mario00
asked on
Administrator cannot save to local C:\ drive, nor access own user folders (i.e., Videos, Pictures, Documents, etc.). Access Denied
I have a workstation connected to my domain whose user is set up as an Administrator. This user was created through a wizard:
Control Panel->User Accounts->Manage User Accounts->Add...
The user was selected from my AD and added as an Administrator. This is the same process I have used on numerous workstations without any difficulties. In this particular instance, however, the user is unable to save to the local C:\ drive, nor can this user access own private folders (i.e., Videos, Pictures, Documents, etc.).
Steps I have tried:
Control Panel->User Accounts->Manage User Accounts->Add...
The user was selected from my AD and added as an Administrator. This is the same process I have used on numerous workstations without any difficulties. In this particular instance, however, the user is unable to save to the local C:\ drive, nor can this user access own private folders (i.e., Videos, Pictures, Documents, etc.).
Steps I have tried:
Having user sign out, and back in
Changing user account to Standard, saving changes, and back to Administrator
Verified information in the "Back up files and directories" within secpol.msc
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So basically my solution led you to the solution. I need at least some credit for leading you to the solution.
Thanks
Zac
Thanks
Zac
ASKER
Accepted answer: 0 points for mario00's comment #a41215886
Assisted answer: 500 points for itguy012006's comment #a41215280
for the following reason:
I had the user sign out, I signed in, changed the name of the user directory folder, and had the user sign back in. After that, I had the user sign out once again, I signed back in, changed the folder name once again to what it was before, and had the user sign in. This fully resolved the issue.