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

[vivekrishna]

When I start the Windows 10 VDI, I am getting the error ""The Group Policy Client service failed the logon. Access is denied."

It is random in some machines and happens often.

Thanks,

Vivek

[ahakimb]

Hello

We are facing the same issue intermittently

it’s seems that when you restart the VM

someone in another thread say :

“

Worked with support, here is the fix that resolved this issue:

Update registry entry: HKLM\SYSTEM\CurrentControlSet\services\svservice\Parameters and change the value of "RebootAfterDetach" to 1.

”

we didn’t test this tips at this time

[vivekrishna]

Does this need to run as a start up script or push in in the Global GPO policy.

[robsisk1972]

So I have users experiencing this intermittently after moving to 1909.   Can anyone confirm that changing this Reg value works?

Thanks

[robsisk1972]

What?   With that setting, the Machine can never be shutdown!

[robsisk1972]

So I finally figured this out in my environment.   The "the group policy Client Service Failed the Logon" sent me down a worm hole so be ware.    It ended up simply being a specific app stack that was assigned to users....That's why it was intermittent.   Removing that specific appstack for the failing users allowed them to logon.   If you see this issue, take heed of whom it is effecting and see if they have a specific appstack in common.  

[TechCheez]

Any idea what in the app stack actually caused it? I'm having the same issue, but the user only has a handful of app stacks and it only happens once and then allows them to login after a reboot of the VM.

[Shreyskar]

Hi TechCheez

This issue is generally caused due to writable volume not appstacks. If it is happening only with appstacks for you, you need to attach one appstack at a time to find the problematic appstack.This was mostly seen for writables created in older version of appvolumes agent (2.16 and earlier).

The workaround is to create 'Rebootafterdetach' reg.

[TechCheez]

We don't have any AppStacks with writable volumes. Every AppStack we have attached was re-created from scratch in 4.x and this seems to only be happening on a persistent full clone machine.