Orphan ACLs remain on files/dirs after account removal
After screwing up one of my accounts I created a fresh profile and imported my settings from the old one, and then removed the account from the computer managment console, and deleted the directory from the 'documents and settings' dir.
After screwing up one of my accounts I created a fresh profile and imported my settings from the old one, and then removed the account from the computer managment console, and deleted the directory from the 'documents and settings' dir.
However on checking the security tabs on folders/files that were created using the old account (and thats most of them because it was an adminstrator profile). A orphan permission remains eg S-1-5-21... etc.
Does this leftover permission pose a security risk or affect Windows performance in any way? If so is there any way to easily remove all the old entrys from the disk / registry without a re-install of the OS?
However on checking the security tabs on folders/files that were created using the old account (and thats most of them because it was an adminstrator profile). A orphan permission remains eg S-1-5-21... etc.
Does this leftover permission pose a security risk or affect Windows performance in any way? If so is there any way to easily remove all the old entrys from the disk / registry without a re-install of the OS?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Thx thats put my mind at rest at least...
But is there any way of searching out and removing the old entries on disk or in the registry in one go? (either from within Windows, or using a 3rd party util).
But is there any way of searching out and removing the old entries on disk or in the registry in one go? (either from within Windows, or using a 3rd party util).
