Q: So I have this Windows 2000-based computer used to be a member of a domain, but then I brought it home on a personal computer, and I took him off the field. Im a new user I created as a member of the Administrators group. Everything worked fine until I tried to address some of the files on the computer of the user I used to use to log in to remove the domain. They said I was not authorized to do so. So I looked at the permissions on the files, and Windows aware that I had read only access permissions, and I was not able to change them. So I logged on as local administrator, and had the same problem. I have not heard of anything like this before, does the system do not have full access to certain files. Any thoughts? By the way, the files of the program and the domain user UWin was also in the Administrators group. Thanks for any help you guys and girls can give me.
Re:<< so if I take ownership and give you full access again you'll never notice. >>
The ability of anyone (inculding the admin) to take ownership of files/folders can disabled via Group Policy.
If Im making the call on policy, and not the only admin in the domain, its a must for me.
I also audit ownership changes, so it's unlikely that no one is going to notice.
That said, most admin's don't give a hoot about stuff like that. As I've said a couple of times before , it's not the OS's inability to provide the tools, it's the admin's lack of knowledge/ability/desire to actually implement them.
Re:Still, I suppose what we have now is a start in the right direction…
What direction? All that does is make things more complicated for the admin.
Re:<< This is expected behavior. It means that even admins can't poke around your My Documents folder without taking ownership of the files. Which is, all in all, a Good Thing in my opinion.
How often do you check the owner of your files? I'm willing to bet, even if you are the exception, that noone pays attention to that so if I take ownership and give you full access again you'll never notice. Also someone's already written a chown program for Win2K so I could give ownership back if I wanted to. >>
You are right. These are very valid points, and MS has not addressed them.
Still, I suppose what we have now is a start in the right direction…
Re:Thanks guys, that cleared it right up. Guess I'm used to Linux and the almighty root.
Re:This is expected behavior. It means that even admins can't poke around your My Documents folder without taking ownership of the files. Which is, all in all, a Good Thing in my opinion.
How often do you check the owner of your files? I'm willing to bet, even if you are the exception, that noone pays attention to that so if I take ownership and give you full access again you'll never notice. Also someone's already written a chown program for Win2K so I could give ownership back if I wanted to.
Re:You need to take ownership of the files before you can give yourself permissions to the files.
This is expected behavior. It means that even admins can't poke around your My Documents folder without taking ownership of the files. Which is, all in all, a Good Thing in my opinion.
-Noggin
0 Comments.