New
#11
Regardless of the technicalities (which most users couldn't care less about) an XP Administrator could accomplish tasks with significantly less clicks, than a W7 Administrator.
I am aware of the "twin security token" system.
There is some confusion here (probably due to my bad phrasing):
- Domain Administrators need to have access to all network resources to be able to manage the network
- Local Administrators do not
That does not explain why users can fix problems using the built-in Administrator, when they can't fix problems despite:
- Owning a resource
- Having Full permissions
- Having child objects set to inherit those permissions
There have been multiple threads on SevenForums where this has happened.
I find it unlikely that:
- Every reported instance of this occurring has been PEBKAC
- Users have set the additional specific permission restrictions on themselves.
My bad.
Five years ago I couldn't find any useful information about this.
After spending considerably more time than a clean install would take, I gave up and performed a clean install.
Thanks for this tip. :)
I'm not quite sure what you are trying to say.
The user account created during install, is part of the Administrators group (in W7 at least).
Obviously simply changing an account to Administrator doesn't magically endow someone with knowledge they didn't previously possess.
Nonetheless it seems you have never come across this issue:
- X owns a folder
- X has Full permissions
- X's permissions are applied to child objects
- Windows will not allow X to access the folder
I see it once or twice a year.
The other variation is when you attempt to take ownership and Windows refuses to apply the changes.
The most recent example of this happening to me was a few weeks ago in W10 (during my search for the Lock Screen wallpapers).
W10 refused to apply the new ownership to a least one child object and displayed the "security enumeration failure" warning.
I was unable to open the folder to view its contents.
I rebooted it and tried again.
Again I received the "security enumeration failure" warning, however despite this I was able to open the folder and view its contents.
Linux ignores NTFS permissions.
However despite what Linux "Fan Boys" claim, it is not bulletproof either.
There are files in my Home directory that are owned by "root".
Given they are config files for certain applications, it appears those application have been incorrectly written.
When I upgraded from LM17 to LM17.1, I tried using the Home directory backup/migration tool.
After installing LM17.1, I used the tool to restore my Home directory.
The permissions were randomly screwed up.
I ended up performing another clean install and manually copying my files to my new Home directory.
When I mentioned this on the LM forums, other members reported the same experience.