Group Policy Client Error When Logging In
Warning: This post deals with editing the registry. If you don’t know what that is stop right here & ask someone else to help you. Using the registry editor incorrectly can cause serious problems that may require you to reinstall Windows. Use the registry editor at your own risk.
Everytime a user tried to log into any of the Terminal Servers she got an error that said, “The Group Policy Client service failed the logon. Access is denied.”
No one else was having the issue on any of the Terminal Servers.
Long story short, her roaming profile was bad. What you can do to verify is open Regedit & mount (e.g. Load Hive) the user’s ntuser.dat file to a temporary key name. Look at the permissions of that node.
Yeah, that’s all messed up. It should look more like this.
So in my case I renamed her roaming profile on the file server from username to username.bak & had her try to log in again. It created a new profile & all was good. Had to reconfigure a few things once she was logged in but redirected folders took care of most of the things that would have gone missing.