Remove/Rebuild User Profile on Remote Desktop Server 2016
I've inherited a remote desktop server to administer and a little out of my depth and trying to figure out a problem isolated to one user.
I believe this user has a corrupt profile which is causing some odd permissions problems. She was created along with all the other users on the remote desktop server with identical permissions when new several months ago.
In order to resolve this problem, I thought it would be sufficient to remove the user from the remote desktop server and I assumed that on next login her profile would be rebuilt. I renamed her folder under c:\users and tried logging in again as that user. But after getting to the user's desktop I got the error: "We can't sign into your account..." with the additional info about creating a temporary profile etc.
I've seen this error on desktops before and know it means that the user's profile cant be accessed, but not sure where to go with this on a Remote Desktop Server.
Am I on the right track to remove and rebuild this user's profile on the Remote Desktop Server or is there a better way to attack this problem?
If I am on the right track, perhaps there's a better way to do give this user a fresh profile on the Remote Desktop Server?
As always, any help is appreciated.
Ken C.
Additional Info:
Windows Server 2016 Remote Desktop
On a domain with the controller local to this location
Remote Desktop Server and domain controller both running as Hyper-V machines on the same hardware.
I believe this user has a corrupt profile which is causing some odd permissions problems. She was created along with all the other users on the remote desktop server with identical permissions when new several months ago.
In order to resolve this problem, I thought it would be sufficient to remove the user from the remote desktop server and I assumed that on next login her profile would be rebuilt. I renamed her folder under c:\users and tried logging in again as that user. But after getting to the user's desktop I got the error: "We can't sign into your account..." with the additional info about creating a temporary profile etc.
I've seen this error on desktops before and know it means that the user's profile cant be accessed, but not sure where to go with this on a Remote Desktop Server.
Am I on the right track to remove and rebuild this user's profile on the Remote Desktop Server or is there a better way to attack this problem?
If I am on the right track, perhaps there's a better way to do give this user a fresh profile on the Remote Desktop Server?
As always, any help is appreciated.
Ken C.
Additional Info:
Windows Server 2016 Remote Desktop
On a domain with the controller local to this location
Remote Desktop Server and domain controller both running as Hyper-V machines on the same hardware.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
when you delete the profile you also have to remove it from the registry.
Click Start, and then click Run.
Type regedit , and then click OK.
In the Registry Editor, navigate to the following registry key: HKEY_LOCAL_MACHINE\Software\Microsof t\Windows NT\CurrentVersion\ProfileL ist.
Locate your user profile folder and delete it and the username
David...
Thanks for the tip... I will have to wait until this weekend to try that, but will update as soon as I do.
Thanks,
Ken C.
Thanks for the tip... I will have to wait until this weekend to try that, but will update as soon as I do.
Thanks,
Ken C.
David...
That did the trick. After backing up and deleting the registry key, I renamed the c:\users\*userdata* file and then logged her into a fresh profile on the Remote Desktop server.
And best of all, the newly created profile was free of the odd permission that were the cause of this whole exercise.
Thanks for the help!
Ken C.
That did the trick. After backing up and deleting the registry key, I renamed the c:\users\*userdata* file and then logged her into a fresh profile on the Remote Desktop server.
And best of all, the newly created profile was free of the odd permission that were the cause of this whole exercise.
Thanks for the help!
Ken C.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial