So that I don’t lose this later, and so it will help others out who run into this…
When you are developing non-admin, you will probabky end up using something like Aaron Margosis’ MakeMeAdmin tool to elevate your privileges when you need to do admin-like things.
The problem comes when you are doing something in an admin context that creates files. In Windows XP, when you created a file as a member of the Administrators group, the file was owned by you. In Server 2003, it is owned by the Administrators group. Apparently this was to make it easier for multiple system adminstrators to work on a system. Each of them, by just being a member of the right group, gets ownership of all the files created by other admins. Makes sense.
But when you are developing, you may not want this behavior. Suppose for example that you perform a build of your application from a MakeMeAdmin boosted context. When the compiler is doing its dirty work, all those files in obj/ and bin/ will be owned by the Administrators group. If you later try to do a compile of the same project as a non-admin, it may fail because you may not have the rights to delete an administrator’s file. Oops. Keith Brown talks about this in Item 41 in his book.
Now for the fix (similar to the one described _place_holder;at the end of _place_holder;MSKB 318825):
- Use MakeMeAdmin or logon as the local machine administrator
- Launch gpedit.msc, the group policy editor.
- Navigate to Computer Configuration/Windows Settings/Security Settings/Local Policies/Security Options in the tree
- Double click on System objects: Default owner for objects created by members of the Administrators group.
- Change the value to Object creator.
Reboot and you’re golden.
Note: You may have to use MakeMeAdmin to fix any files that were previously created.