VMware Horizon Community
WheatonCollege
Contributor
Contributor

"The Group Policy Client service failed the logon. Access is denied." error on windows 7 Linked Clone desktops with Persona Management

Hi All,

Here is our setup

- Windows 7 pool of Linked Clone floating desktops (62 desktops in the pool)

- View 5.2

- Esxi 5 hosts

- Using Persona Management for user profiles and also redirecting desktop and my documents folders into profile folder (lives on a NetApp CIFs share)

- Using ThinPrint GPO's to assign a default printer

- Using several other GPO settings that are consolidated into just a handful of objects for performance reasons

We received notice that 2 end users (out of 1,263) received the following warning when trying to log into the pool

"The Group Policy Client service failed the logon. Access is denied."

We ended up making sure they were not logged in and we just renamed their profile folder on the NetApp CIFs share so their next login would re-create it... but something like this throws up the red flag for me. Any ideas as to why this may have happened?

Reply
0 Kudos
2 Replies
satishchirala
Enthusiast
Enthusiast

http://support.microsoft.com/kb/947215 To fix the user account profile, follow these steps: Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows How to back up and restore the registry in Windows1.Click Start, type regedit in the Search box, and then press ENTER. 2.In Registry Editor, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList 3.In the navigation pane, locate the folder that begins with S-1-5 (SID key) followed by a long number. 4.Click each S-1-5 folder, locate the ProfileImagePath entry in the details pane, and then double-click to make sure that this is the user account profile that has the error. 2705065 ◦If you have two folders starting with S-1-5 followed by some long numbers and one of them ended with .bak, you have to rename the .bak folder. To do this, follow these steps: a.Right-click the folder without .bak, and then click Rename. Type .ba, and then press ENTER. 2493038 b.Right-click the folder that is named .bak, and then click Rename. Remove .bak at the end of the folder name, and then press ENTER. 2493039 c.Right-click the folder that is named .ba, and then click Rename. Change the .ba to .bak at the end of the folder name, and then press ENTER. 2493040 ◦If you have only one folder starting with S-1-5 that is followed by long numbers and ends with .bak. Right-click the folder, and then click Rename. Remove .bak at the end of the folder name, and then press ENTER. ◦If you have two folders starting with S-1-5 followed by some long numbers and one of them ended with .bak, you have to rename the .bak folder. To do this, follow these steps: a.Right-click the folder without .bak, and then click Rename. Type .ba, and then press ENTER. 2493038 b.Right-click the folder that is named .bak, and then click Rename. Remove .bak at the end of the folder name, and then press ENTER. 2493039 c.Right-click the folder that is named .ba, and then click Rename. Change the .ba to .bak at the end of the folder name, and then press ENTER. 2493040 ◦If you have only one folder starting with S-1-5 that is followed by long numbers and ends with .bak. Right-click the folder, and then click Rename. Remove .bak at the end of the folder name, and then press ENTER. 5.Double-click the folder without .bak in the details pane, double-click RefCount, type 0, and then click OK. 2493045 6.Click the folder without .bak, in the details pane, double-click State, type 0, and then click OK. 2493046 7.Close Registry Editor. 8.Restart the computer. 9.Log on again with your account.

Reply
0 Kudos
charvoworld
Enthusiast
Enthusiast

I ran into an interesting problem last week when I was told that one of the users in a VMware View deployment. The majority of the desktops in the environment were linked-clones with a dedicated 40GB disk assigned to every user so that their profiles could get redirected to a persistent disk and thus retained their customized Windows and Office settings every time I refreshed the desktops with an updated image.  Seeing how no one else had issues with their desktops, I was curious as to why the user was experiencing this problem so I went ahead and logged onto her desktop to find that her profile was redirected to the persistent D drive but same user profile was also available in c drive.

I initially thought that the problem would be solved if I simply deleted the profile from within the master image but quickly noticed that it was a bit more demanding than that so after hacking away at the problem and finally fixing it,  I took the time to document the steps.

pls follow this link

charvoworld.blogspot.in

click here

Believe,


Charvo Benjamin

Reply
0 Kudos