Anyone with SeTakeOwnership privilege can take ownership of an object. By default this is the built-in Administrators group, but you can revoke it from the administrators group and/or give it to other users/groups
Cheers Ken > -----Original Message----- > From: John Hornbuckle [mailto:[EMAIL PROTECTED] > Sent: Saturday, 11 October 2008 4:30 AM > To: NT System Admin Issues > Subject: RE: Who is "CREATOR OWNER"? > > I could be way off-base here, but my understanding is that the Creator is the > person/account who created the file/directory in question. The Creator is the > Owner, by default. However, administrators can take over ownership of the > objects. > > > > > > John Hornbuckle > MIS Department > Taylor County School District > 318 North Clark Street > Perry, FL 32347 > > www.taylor.k12.fl.us > > > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, October 10, 2008 12:43 PM > To: NT System Admin Issues > Subject: Who is "CREATOR OWNER"? > > I've had some exposure/experience with Unix and linux, so this is very > puzzling to me... > > Why is it that, for file/folder permissions in my XP Pro systems, there is > this critter, "CREATOR OWNER", who has no permissions? From what I've > read at TechNet, "C/O" has full permissions for a number of folders, > including "Program Files" and "Documents and Settings" (the complete > sub-path for each of them) as well as some others. > > Anyway, could someone please explain to me Microsoft's conception of > "owner"? > > Either this is something completely different from "owner" in x-nix > systems, or all permissions are unchecked because "C/O" already has full > permsissions and so the boxes need not be checked. (If this is the case, > then, why are they checked for Administrators?) > > Thanks! ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
