The Group Policy Client service failed the sign-in The universal unique identifier (UUID) type is not supported

Hi guys,
we created a custom WIM Image (Windows 8 Enterprise) with MDT 2012.
Sysprept the Image, Deployed via SCCM 2012 SP1.
Computers are Domainjoined. Error with standard Domain User.
On some computers (not every computer) and not with every user on the first logon following error message arises:
The Group Policy Client service failed the sign-in The universal unique identifier (UUID) type is not supported
It works, when you log in a second time but this error isn't very nice.
Is there a solution for that?
Kind Regards
Martin

Hi,
The service is responsible for applying settings configured by administrators for the computer and users through the Group Policy component. This issue can be caused by various reasons based on the computer environment.
Can you find any information in event log about this issue?
Here is the related blog in which the steps can solve most of such issues if the issue continuously happen.
http://blogs.msdn.com/b/moiqubal/archive/2012/03/04/how-to-fix-quot-the-group-policy-client-service-failed-the-logon-access-denied-quot-error.aspx
Also, you can refer to the similar thread about this issue:
http://social.technet.microsoft.com/Forums/en-US/4a644219-50ee-494d-b965-e64a8555109e/the-group-policy-client-service-failed-the-signin-the-universal-unique-identifier-uuid-type-is
Since this issue can be related to SCCM, to better help you, please submit a new thread for further help:
https://social.technet.microsoft.com/Forums/en-US/home?category=systemcenter2012configurationmanager
Hope these could be helpful.
Kate Li
TechNet Community Support

Similar Messages

Error Message when logging on "The Group Policy Client service failed the logon. Access is denied"

Since the move to Windows 7 we have started getting this error above when people login at random times and on random machines, at first we thought it was only a select few users, but now it seems to have occurred to about 20 different Staff members working
at the school. Also of those 20 odd users it has happened to them on a few occasions.
What we know
We know this problem is only occurring to staff with Roaming Profiles, it seems like somehow the profile is not Synchronizing with the Servers File Share that houses the profiles, which causes the NTUSER.DAT file to become corrupt and go from being around
2 – 3 MBs to 256KB (In all cases where a user has had this issue there NTUSER.DAT file has been 256KB)
Current Resolution to the problem
When a staff member contact us with this problem, we fortunately have Previous Versions working on the profiles folder on the server, so we are able to restore their NTUSER.DAT file from 1 to 2 days before it became corrupt, which then seems to allow them
to log on fine
What we have tried so far & suggested so far
After some research on Google, we found the following thread on EduGeek
http://www.edugeek.net/forums/windows-7/78733-windows-7-user-profile-failed-error-again.html#post700415
Which suggested that the problem may lay within registry, so we implemented the Script that was posted on the website, however this has not seemed to make any difference
In the early stages when only 5 – 10 staff seemed to be having the problem, we believed the issue could be with just certain AD accounts. It had not seemed to happen to any recently created AD accounts so we thought it could be a corrupt attribute on
the user so we delete one of the staff AD accounts that had the problem and creating a brand new one, however within about 2 – 3 weeks that staff member had the issue occur again
Leading on from point two, we also thought the problem could be with people using multiple computers, logging on in 2 places and not logging off properly, but unfortunately the staff member referred to in point 2 only uses the one computer in reception.
Another potential cause that we figured might be the route of the problem, was it could be specific computers that are not communicating properly with the server, which could be causing this problem to occur, but we have no real way of testing this,
as the staff generally log onto 3 – 4 different computers throughout the day and in different location
We log a call with EE and they just pointed us to various websites that we had already checked and wasn’t much help.
In Summary
This error has now occurred with about 20 members of staff, we currently only use Windows 7 at our Senior School & Moving to Windows 7 at our Prep School in the Summer
holidays, we would like to find out the route of this problem ideally before then, as we could potentially be doubling the amount of staff with the problem after the move. Has anyone else seen this problem or have a brain wave on how to solve it?
Regards
Andy

Hi Dudleya,
First of all ,I would suggest to check the permissions of the NTUSER.DAT registry hive .Here is a link for reference :
The Group Policy Client service failed the logon. Access is denied(Juke Chou`s answer)
https://social.technet.microsoft.com/Forums/windows/en-US/8c0054a3-35be-4fc4-839c-e2176613eb23/the-group-policy-client-service-failed-the-logon-access-is-denied?forum=w7itpronetworking
Please refer to this link and add the registry keys to have a check .Please backup the registry keys before you made modifications to them.
The Group Policy Client Service Failed The Logon In Windows 8(It should also work on windows 7 )
http://www.thewindowsclub.com/fix-group-policy-client-service-failed-logon-windows-8
If the issue persists ,we can refer to this link to troubleshoot this issue .
Troubleshoot User Profiles with Events(It should also be applied to windows 7 )
https://technet.microsoft.com/en-us/library/jj649075.aspx
NOTE: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites.
Best regards

The Group Policy Client Service Failed The Logon

Hello,
When our students login to our Windows 7 machines they are getting this error:
The Group Policy Client Service Failed The Logon
Access is denied.
We are attempting to use both volatile and roaming profiles. The profiles are being stored on their H drives. I seem to only see the issue when the Windows NT 6.1 Workstation Profile.V2 folder already exists on their H drive. If the profile is not there then everything works fine.
Loading the user's ntuser.dat hive located in their H drive and changing the permissions manually to allow System, Administrators, and Users Full Control fixes the issue. How can I do this across all my user's H drives? Should I just delete them all and manually create the folder myself?
Last time I found one, the permissions for the hive had an "Unknown" user in the permissions list. There was no "Users" group. Removing the "Unknown" and adding "Users" fixed the problem. Are the permissions getting corrupted somehow?
Thanks for any assistance.
I've used the following link for reference:
Support | Windows 7 Roaming Profiles fail - user is assigned a temporary profile or fails to log on
Novell Doc: ZENworks 10 Configuration Management Policy Management Reference - Assigning a Roaming Profile Policy that has the User Profile Stored on a Home Directory

Originally Posted by coreyhansen
So it appears that I am experiencing the temporary profile detailed in my link I referenced above. I have status bubbles disabled by policy and didn't notice the notification. I'm going to try pre-populating my user H drives with the Windows NT 6.1 Workstation Profile.V2 folder containing an ntuser.dat file I've already edited the hive permissions of. This worked in small scale testing, so we will see.
I've been referencing this thread: http://forums.novell.com/novell-prod....html#poststop
So I have tried this with students that are experiencing the problem, and gotten limited success. It feels like it works at random, with around 50% of attempts working.
Has anyone out there had success with roaming profiles? Do I just need to go back to folder redirection? Will anyone please respond?
This is what the student's ntuser.dat hive permissions look like when things are not working:

The group policy client service failed the logon access is denied.

This one is starting to get on my nerves now. We've had 2 users suffering this problem on our Remote Desktop server.
We are running two Windows Server 2008 SP2 domain controllers, with two Windows 2008 R2 servers running RD Gateway and Remote Desktop Server.
The first user I had to recreate because of following instructions I googled because it caused the user to always logon with a temporary profile on the server and I could not resolve this.
This user I have managed to cleanly delete the local logon profile.
BOTH of these users are on roaming profiles, as are most of the users that are logging in to this server (for reasons that they move around the office). On the server, the user is listed twice one with a .v2 extension (XP machines at desks)
The user we are having a problem with at the moment was working perfectly fine a couple of weeks ago when they last logged into the server.
Could this be down to me setting an over ride on the settings that force people to logout completely after an hour of idle time, resulting in an unclean logoff?
Some of the messages that are in the event log for when that user attempts to login:
Event id: 1542
Windows cannot load classes registry file.
DETAIL - The system cannot find the file specified.
Event ID: 6001
The winlogon notification subscriber <Sens> failed a notification event.
Event ID: 6004
The winlogon notification subscriber <GPClient> failed a critical notification event.
I'm also getting a constant batch of
Event ID: 510
Folder redirection policy application has been delayed until the next logon because the group policy logon optimization is in effect
Any ideas why this should happen? I need a solution as soon as possible please as these users are running our sales department from home, and this user is due to be on the rota to do it this week! :)

Andy, I have been struggling with this issue on a new 2008R2 server. Can
you explain the commands you used to load ntuser.dat and usrclass.dat
into the registry? This is a truly maddening issue.
Thank you.
On 1/10/2011 11:01 AM, Andy Murphy wrote:
> Seems I have managed to over come this.
>
> After deleting the profile from within the Advanced System Settings >
> User Profiles on the RD server I still couldn't logon (as said above
> about clean deletion of the local profile)
>
> So I manually loaded the UsrClass.dat and NTUser.dat into the registry
> as they were not there. To do this I did the following:
>
> Loaded NTUser.dat from the profile on the server as a hive under
> HKEY_USERS to S-1-5-21-2055973500-2782184047-1828406536-1165
>
> Loaded UsrClass.dat from the profile.v2 on the server as a hive under
> HKEY_USERS to S-1-5-21-2055973500-2782184047-1828406536-1165_Classes
>
> Then logged in as the user, and it works perfectly again (it did hang on
> waiting for the session manager). To be sure I then copied the Default
> user to that newly created profile on the RD server and logged in again,
> no hangs. Perfect.
>
> Maybe this will solve a few other peoples problems with these related
> errors.
>

Group Policy Client service failed the sign-in

After doing an OSD with a Windows 8.1 reference image, I get the "The Group Policy Client service failed the sign-in. The Universal unique identifier (UUID) type is not supported." message. It only shows up on the first very first log in, right
after the OSD process has completed, and never shows up again. I'm using basic OSD task sequences right now, but I'm not sure where to pinpoint the cause of this message.

Hi,
This is only happening when we use the original RTM ISO en_windows_8_1_enterprise_x64_dvd_2791088.iso
(without any software update), if we instead use the en_windows_8_1_enterprise_x64_dvd_2971902.iso the error is gone.
Apparently this ISO is updated with the
Windows 8.1 and Windows Server 2012 R2 General Availability Update Rollup
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Group Policy Client service failed! Help!

A few days ago I was booted out of my account, while watching a DVD. My system restarted itself, but not before flashing some sort of blue screen. Unfortunately I was unable to read the content of it. After restarting, I was presented with a light blue login screen, instead of my normal screen. However, my name and profile picture remained the same. I was able to login with my password, only to be informed that I had been set up with a temporary account. I was unable to access my files, and had no idea how to access my regular account. After logging out, and restarting in hopes that it would go back to normal... my system went into recovery mode, and afterwards presented me with the same temporary account login screen. Only this time, I was unable to login. Instead I received "The Group Policy Client service failed the logon. Access denied" message. I'm the only user (administrative), and my computer has no internet connection. So, I'm not sure if this is a simple error; a result from my low capacity battery needing to be replaced, or a virus. I've checked previous forums, but I've had no luck. I can't login to my computer at all, and it's very frustrating. I've also backed up my files, just in case my system has to be restored to its factory settings (I hope not). Could any one tell me how to resolve this? Please!
- Frustrated (Pavilion dv6-1350us) User

Hello @chigi93 ,
Welcome to the HP Forums!
I understand you were booted from your account and can now only log in with a temporary account.
Windows does this when the main account is unavailable. The account most likely needs to be repaired.
Please follow this document to fix a corrupted profile: Fix a corrupted user profile.
If that doesn't work please go through this document: You receive a "The User Profile Service failed the logon” error message.
Let me know if that works.
Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
The Great Deku Tree
I work on behalf of HP.

After restarting i get a message saying that Windows could not connect to the Group policy client service

The message i get is the following:
Windows could not connect to the Group policy client service. This problem prevents limited users from logging on to the system As and administrative user you can review the system event log for details why the service didn't respond.
This happens after restarting my laptop. It takes longer than usual and once it has booted up and loaded Windows Vista, I get the message on the right bottom corner as a window popping up.
I can still use my computer but a lot of my user account settings are not there.
I fixed it temporarily by rebooting using the option: boot up using my last successful configuration. Bu once I restart again the same thing happens.
How can i fix it?
Thanks.

Hi,
Please try the solutions on the following threads:
http://social.answers.microsoft.com/Forums/en/vistasecurity/thread/bbfe3246-0ceb-4899-bfba-7a98e642c009
http://social.technet.microsoft.com/Forums/en/winserverGP/thread/5de9f483-ff69-4fac-ac3f-601a62cc78d1
If the problem continues, please let us know if the computer is in a domain environment.
Regards,
Bruce

Failed to Connect "Group Policy Client Service" Windows 7 x64

This error pops up everytime boot / start-up. I've tried everything, for the last month. including
http://support.microsoft.com/kb/2421599 In the "Resolution Section" did step by step, But did not work for me...
Also
http://blogs.technet.com/b/mempson/archive/2010/01/10/userenvlog-for-windows-vista-2008-win7.aspx Didn't work either. :(
Is this a Winlogin problem? Or does have to do with other computers in my homegroup?
But in Safe Mode & Safe Mode with Networking, this issue does Not appear / pop-up at start up. "Group Policy Client Service"
""HP Premium Remote Services"" tells me that in order to fix, I have to Re-Install Windows. And have been in contact today with Hp Premium Remote Services for over 7 hours with NO Resolution!!
Hate to make a Recovery Partition on a New PC, in order to Re-Install Windows...
This is a Brand New HP Pavilion HPE H8-1234 AMD Processor that I installed on 7/23/2012. Running windows 7 64-bit home premium, OS: Internet Explorer 9.
Have a copy of Windows 7 Ultimate using Anytime Upgrade, My question is would that rectify the "Group Policy Client Service" error?
Always run MalwareBytes Anti-Malware and Hitman Pro, in addition with Norton, on a regular basis. So that I know my system is clean...
Any MS Engineers or Tech's have any ideas, suggestions OR help, How to Fix this issue,With-Out having to use: System Recovery/Restore. To factory condition...
Would be Very Greatly Appreciated! HELP Me Pleeeze !!!!
***Because this issue Baogles my Mind! After all I'am only dealing with half a Brain, LOL- Due to Brain Tumor Surgery...

I FOUND SOLUTION TO THIS PROBLEM!
I had this issue on my laptop since November, and it really bugged me. I sifted through the event log and found the pattern of events that preceded the issue, and, probably, caused it.
In short, the pattern is as follows: Windows updates run automatically as scheduled, and when reboot is initiated after the updates are finished, the computer crashes (probably during reboot sequence). When it boots up, it reports that the last shutdown
was unexpected, and the issue begins to occur.
I spent 2 days trying to dig out a solution from the Internet, to no avail, until I came across
this page. It doesn't say anything about this particular problem, but it gives more information about SVCHOST process that starts many services, including Group Policy Client. It looks like during reboot a vital registry settings were lost during
crash and Group Policy Client "doesn't know" how to start. Let me explain:
There are two places to look in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services this path should contain
gpsvc key (a folder), which is responsible for service parameters and configuration. I found that the key was intact, so, you do not touch anything here - just check that the key exists.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SVCHOST This is the most important path you should look into, as it must contain the keys and values referred in the key #1. Below are descriptions what must be present
there.
There must be Multi-String value called GPSvcGroup. My laptop was missing it. So, you should create multi-string value named
GPSvcGroup and assign it value GPSvc.
Next, you must create a key (a folder) and name it GPSvcGroup - this key normally should be there, but, again, it was missin on my laptop.
Then open newly-created GPSvcGroup folder and create 2 DWORD values:
First called AuthenticationCapabilities and you must give it a value of 0x00003020 (or 12320 in decimal)
Second is called CoInitializeSecurityParam and it must have value of 1.
Once you complete all steps above, reboot the computer and the problem will be fixed.
I am so relieved I was able to fix it, and hope this will help others with the similar issue.
Here is the link to the video walkthrough if you have any troubles understanding what has to be done: http://youtu.be/4m5KEmckWK4
I did try the above, but it did not fix my issue with the ""group policy client service failed the logon".
This problem was happening on 5 different RDS Nodes. All I did was rename the Roaming Profile, then delete the locally stored profile on each RDS Server: right click COMPUTER > PROPERTIES > ADVANCED SYSTEM SETTINGS > USER PROFILES > delete the
offending User(s).
Hope that helps.
Life is dangerous, no one has ever survived. So enjoy!

Group Policy Client service does not start

Hi,
As soon as I (administrator on my PC) logon to Windows 7, I get a message saying that the Group Policy Client service failed to start. I'm not sure why I'm getting this error even though the dependencies are very much up and running..
Below is the error message I get in the notification area as soon as I logon
Failed to connect to a windows service
Windows could not connect to the Group Policy Client service. This problem prevents stndard users from logging on to the system.
As an administrative user, you can review the System Event Log for details about why the service didn't respond.

I FOUND SOLUTION TO THIS PROBLEM!
The crash of your computer caused that - you are absolutely right!
I had this issue on my laptop since November, and it really bugged me. I sifted through the event log and found the pattern of events that preceded the issue, and, probably, caused it.
In short, the pattern is as follows: Windows updates run automatically as scheduled, and when reboot is initiated after the updates are finished, the computer crashes (probably during reboot sequence). When it boots up, it reports that the last shutdown
was unexpected, and the issue begins to occur.
I spent 2 days trying to dig out a solution from the Internet, to no avail, until I came across
this page. It doesn't say anything about this particular problem, but it gives more information about SVCHOST process that starts many services, including Group Policy Client. It looks like during reboot a vital registry settings were lost during
crash and Group Policy Client "don't know" how to start. Let me explain:
There are two places to look in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services this path should contain
gpsvc key (a folder), which is responsible for service parameters and configuration. I found that the key was intact, so, you do not touch anything here - just check that the key exists.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SVCHOST This is the most important path you should look into, as it must contain the keys and values referred in the key #1. Below are descriptions what must be present
there.
There must be Multi-String value called GPSvcGroup. My laptop was missing it. So, you should create multi-string value named
GPSvcGroup and assign it value GPSvc.
Next, you must create a key (a folder) and name it GPSvcGroup - this key normally should be there, but, again, it was missin on my laptop.
Then open newly-created GPSvcGroup folder and create 2 DWORD values:
First called AuthenticationCapabilities and you must give it a value of 0x00003020 (or 12320 in decimal)
Second is called CoInitializeSecurityParam and it must have value of 1.
Once you complete all steps above, reboot the computer and the problem will be fixed.
Video walkthrough for those who are not very technical is here: http://youtu.be/4m5KEmckWK4
I am so relieved I was able to fix it, and hope this will help others with the similar issue.

Windows 8.1 cannot connect to group policy client service

Windows 8.1 laptop under administrator account has this "cannot connect to group policy client service" error.Found the following instructions on internet but I don't see this "Replace owner on subcontainers and objects" box on Permissions/Advanced
popup windows ???
Could anyone help ?
Change the permissions on the relevant keys configuring the Group Policy Client service to allow Full Control to Administrators
Open regedit (Start > type regedit in the search box) and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\gpsvc
Right-click the registry key and choose Permissions.
Click Advanced, then click Owner.
Choose Administrators and check the Replace owner on subcontainers and objects box.
Exit the permissions dialog and then open it again.
Click Advanced, then choose Administrators and click
Edit…
Check Replace all child object permissions with inheritable permissions from this object.
Click OK and confirm; exit.
Thank you,

Hello CarLover,
Based on my test, the option Replace owner on subcontainers and objects exists in Windows 7, but doesn’t exist in Windows 8.1.
Please take a look at the screenshot about the option in Windows 7.
Please take a look at the following thread similar to this issue.
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/why-wont-windows-connect-to-the-group-policy/b73107f8-8447-4599-87a5-65ecc6a63aa0
Best regards,
Fangzhou CHEN
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Group Policy client Service Error - Access is denied

I am
at domain admin working on windows 7 roaming profiles, testing with a
staff user. I am in a domain environment. I have changed the
profile path for a user to the folder I created for new windows 7 roaming
profiles. gave it all the permissions noted here and followed these steps
at Microsoft's deploying roaming profiles page for win 7.<o:p></o:p>
once I logged in the user,
it created their profile.v2 but I still couldn't access it. getting
access denied. so I went back and changed the staff roaming profile back
to the original profile path. didn't make any group policy changes.
but now she gets group policy client service failed to logon. access is
denied. I have deleted the .v2 profile that win 7 creates in her old
profile path, moved her profile path back to what is was before testing,
retested her xp profile which does work and she can login and work.
but the win 7 machines no matter where she logs in, will not work. they
all give the same error about group policy client service failed. no
other users are having this problem

Hi,
Regarding the issue here, have you checked the below thread?
Group
Policy Client Service Failed the logon - Access Denied: Windows 7 Ultimate/Server 2008 R2
Please take a try with the steps mentioned by Nina Liu.
QUOTE here:
At this time, let’s refer to the following steps for troubleshooting:
1. Open registry editor on the problematic Windows 7 machine (please log in as domain admin)
2. Highlight HKEY_USERS, choose File -> Load Hive, browse to the location of one failing roaming profile and open NTUSER.DAT file, click open
3. Under Key Name, enter any name you like, but remember what you have entered, such as enter "test"
4. Expand, HKEY_USERS, you should see new registry hive called "test" or any name you entered earlier
5. Right click on that "test" hive and choose permissions. Confirm that the following users have permissions:
- Administrators: Full Control
- SYSTEM: Full Control
- User (or group) that owns this profile: Full Control
6. If the permissions were wrong, correct them, then click on Advanced tab, on Advanced tab and enable "Replace permission entries on all child objects with entries
shown here that apply to child objects" and click Apply.
7. Highlight "test" registry hive, then click on File -> Unload Hive to release handle on NTUSER.DAT file.
8. Log off and log on with the failing roaming profile you have just modified.
Any process, please feel free to contact us.
Best regards
Michael Shao
TechNet Community Support

The Group Policy client-side extension Scripts failed ...

This is an error I've been seeing forever and it was always the impression that upgrading would resolve it, but it never has even in 10.3. 100% of our users get these errors in the Event Viewer:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1085
Date: 10/21/2010
Time: 8:04:52 AM
User: NT AUTHORITY\SYSTEM
Computer: XXXXXX
Description:
The Group Policy client-side extension Scripts failed to execute. Please look for any errors reported earlier by that extension.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
We also seem to have flakey policy issues where once in awhile a user will not be able to logon to Windows with Workstation Only while getting the " not allowed to logon interactively" message, other times the users report not being able to access the Windows Date and Time Properties and further sometimes they are unable to make system changes.
We have troubleshooted this and the only resolutions we've found are to run zac cc, zac ref, zac pl and sometimes it seems like deleting c:\windows\system32\grouppolicy will help.
In regards to the Event Viewer entry I posted, on any given machine I can issue the command gpupdate and it will put another entry into the Event Viewer (sometimes multiple ones). I've learned through research that if I "clean up" c:\windows\system32\grouppolicy\gpt.ini the errors go away, but once the policy is refreshed they come right back.
This is the version ZenWorks gives the users:
[General]
gPCFunctionalityVersion=2
gPCFunctionalityVersion=2
gPCMachineExtensionNames=[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957D-509E-11D1-A7CC-0000F87571E3}][{3610EDA5-77EF-11D2-8DC5-00C04FA31A66}{0F6B957D-509E-11D1-A7CC-0000F87571E3}][{42B5FAAE-6536-11D2-AE5A-0000F87571E3}{40B6664F-4972-11D1-A7CA-0000F87571E3}][{4CFB60C1-FAA6-47F1-89AA-0B18730C9FD3}{0F6B957D-509E-11D1-A7CC-0000F87571E3}][{827D319E-6EAC-11D2-A4EA-00C04F79F83A}{803E14A0-B4FB-11D0-A0D0-00A0C90F574B}]
Version=6488106
gPCUserExtensionNames=[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{42B5FAAE-6536-11D2-AE5A-0000F87571E3}{40B66650-4972-11D1-A7CA-0000F87571E3}][{4CFB60C1-FAA6-47F1-89AA-0B18730C9FD3}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{A2E30F80-D7DE-11D2-BBDE-00C04F86AE3B}{FC715823-C5FB-11D1-9EEF-00A0C90347FF}]
This is the version I cleaned up:
[General]
gPCFunctionalityVersion=2
gPCUserExtensionNames=[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{4CFB60C1-FAA6-47F1-89AA-0B18730C9FD3}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{A2E30F80-D7DE-11D2-BBDE-00C04F86AE3B}{FC715823-C5FB-11D1-9EEF-00A0C90347FF}]
gPCUserExtensionNames=[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{A2E30F80-D7DE-11D2-BBDE-00C04F86AE3B}{FC715823-C5FB-11D1-9EEF-00A0C90347FF}]
I'm not sure how to get Zenworks to use the cleaned up version nor and I too sure what those extra extensions are and how they got in there. I may need to contact Novell in regards to this, but since I'm already working on an SR with them I figured I'd go ahead and post here first.
Any help or advice would be greatly appreciated.

Here are the groups I'm using. NOTE: These have been in affect throughout the issues experienced. Users will work perfectly fine then suddenly the problem will start happening without any policy change on our side.
-Member of-
Network Configuration Operators+
Remote Desktop Users+
Users+
-Assigned Rights under a group I called "Other Rights"-
Access this computer from network
Change the system time
Log on locally
Shut down the system
The only condition I have is that these issues happen when logging in Workstation Only and I'm not able to recreate the problem on demand with tests.
Originally Posted by craig_wilson
The "Interactive Logon" is a Windows Security Permission.
It is generally assigned to certain local groups such as "User".
Which groups are assigned this right can be changed manually and
controlled by local security policies.
When user's get this error, it generally means their account is not in a
local group that has been assigned that right.
If using "DLU", make sure the user accounts are a member of "Users".
And If anyone was messing with security policies, make sure they did not
take away "Interactive Logons" from anyone.
On 10/29/2010 7:06 AM, jcsmith1 wrote:
>
> Thanks for replying craig.
>
> My policy woes have only grown since my first post. We are currently
> testing the removal of administrative rights and now we're having
> teleworkers (who login Workstation Only) getting the message "policy
> does not allow interactive login". What -seems- to fix it is a zac cc,
> zac ref and zac pl, however we just started getting call backs from
> users.
>
> I seem to have no further leads and Novell's ZenWorks tech supports
> seems to be going through some kind of painful-to-the-customer
> transition as one of my thoughts on resolving the issue is to go to 10.3
> or 10.3.1, but my Satellites appear to be upgrading but in reality do
> not upgrade (but the primary servers upgraded) (See SR 10655976331).
>
> Does anyone knows how to troubleshoot policy issues when the users
> aren't loggin into ZCM?
>
> craig_wilson;2036646 Wrote:
>> See: 'Group Policy Error: The Group Policy client-side extension Script
>> failed to execute.'
>> (Group Policy Error: The Group Policy client-side extension Script failed to execute.)
>>
>> This would never be fixed in any patch, since it would be the job of
>> GPEDIT to properly maintain the GPT.INI.
>>
>> Most of the Time these errors are cosmetic and caused by stray script
>> extensions.
>>
>> You may want to create an Enhancement Request to allow the creation of
>> "Filters" so certain errors are discarded and not sent to the DB/ZCC.
>> This way an Admin could choose to filter out various error messages
>> that
>> they deem are not actually of concern.
>>
>> On 10/21/2010 9:36 AM, jcsmith1 wrote:
>>>
>>> This is an error I've been seeing forever and it was always the
>>> impression that upgrading would resolve it, but it never has even in
>>> 10.3. 100% of our users get these errors in the Event Viewer:
>>>
>>> -Event Type: Error
>>> Event Source: Userenv
>>> Event Category: None
>>> Event ID: 1085
>>> Date: 10/21/2010
>>> Time: 8:04:52 AM
>>> User: NT AUTHORITY\SYSTEM
>>> Computer: XXXXXX
>>> Description:
>>> The Group Policy client-side extension Scripts failed to execute.
>>> Please look for any errors reported earlier by that extension.
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> -
>>> We also seem to have flakey policy issues where once in awhile a
>> user
>>> will not be able to logon to Windows with Workstation Only while
>> getting
>>> the " not allowed to logon interactively" message, other times the
>> users
>>> report not being able to access the Windows Date and Time Properties
>> and
>>> further sometimes they are unable to make system changes.
>>>
>>> We have troubleshooted this and the only resolutions we've found are
>> to
>>> run zac cc, zac ref, zac pl and sometimes it seems like deleting
>>> c:\windows\system32\grouppolicy will help.
>>>
>>> In regards to the Event Viewer entry I posted, on any given machine
>> I
>>> can issue the command gpupdate and it will put another entry into
>> the
>>> Event Viewer (sometimes multiple ones). I've learned through
>> research
>>> that if I "clean up" c:\windows\system32\grouppolicy\gpt.ini the
>> errors
>>> go away, but once the policy is refreshed they come right back.
>>>
>>> This is the version ZenWorks gives the users:
>>>> [General]
>>>> gPCFunctionalityVersion=2
>>>> gPCFunctionalityVersion=2
>>>>
>> gPCMachineExtensionNames=[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957D-509E-11D1-A7CC-0000F87571E3}][{3610EDA5-77EF-11D2-8DC5-00C04FA31A66}{0F6B957D-509E-11D1-A7CC-0000F87571E3}][{42B5FAAE-6536-11D2-AE5A-0000F87571E3}{40B6664F-4972-11D1-A7CA-0000F87571E3}][{4CFB60C1-FAA6-47F1-89AA-0B18730C9FD3}{0F6B957D-509E-11D1-A7CC-0000F87571E3}][{827D319E-6EAC-11D2-A4EA-00C04F79F83A}{803E14A0-B4FB-11D0-A0D0-00A0C90F574B}]
>>>> Version=6488106
>>>>
>> gPCUserExtensionNames=[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{42B5FAAE-6536-11D2-AE5A-0000F87571E3}{40B66650-4972-11D1-A7CA-0000F87571E3}][{4CFB60C1-FAA6-47F1-89AA-0B18730C9FD3}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{A2E30F80-D7DE-11D2-BBDE-00C04F86AE3B}{FC715823-C5FB-11D1-9EEF-00A0C90347FF}]
>>>>
>>>>
>>>
>>> This is the version I cleaned up:
>>>> [General]
>>>> gPCFunctionalityVersion=2
>>>>
>> gPCUserExtensionNames=[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{4CFB60C1-FAA6-47F1-89AA-0B18730C9FD3}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{A2E30F80-D7DE-11D2-BBDE-00C04F86AE3B}{FC715823-C5FB-11D1-9EEF-00A0C90347FF}]
>>>>
>> gPCUserExtensionNames=[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}][{A2E30F80-D7DE-11D2-BBDE-00C04F86AE3B}{FC715823-C5FB-11D1-9EEF-00A0C90347FF}]
>>>>
>>>>
>>>
>>> I'm not sure how to get Zenworks to use the cleaned up version nor
>> and
>>> I too sure what those extra extensions are and how they got in there.
>> I
>>> may need to contact Novell in regards to this, but since I'm already
>>> working on an SR with them I figured I'd go ahead and post here
>> first.
>>>
>>> Any help or advice would be greatly appreciated.
>>>
>>>
>>
>>
>> --
>> Craig Wilson - MCNE, MCSE, CCNA
>> Novell Knowledge Partner
>>
>> Novell does not officially monitor these forums.
>>
>> Suggestions/Opinions/Statements made by me are solely my own.
>> These thoughts may not be shared by either Novell or any rational
>> human.
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

The Group Policy Client Side Extension Group Policy Shortcuts may have caused th e Group Policy Service to terminate unexpectedly.

Hi all,
Having an issue with the shortcuts Group Policy extension applying to our Windows 7 machines. It was working until last Wednesday and since then users get a Group Policy Client service error when logging in.
We have narrowed it down to the shortcuts extension, if the extension is disabled then a user can log in, if enabled and empty then the following error comes up. With all the investigation we have done so far it seems as though something on the client is
making this happen.
We have –
Copied the original policy
Exported and imported the policy
Deleted all the shortcuts
Deleted all the shortcuts and created a brand new shortcut
And the same thing happens. Only if you right click on the Shortcut Extension and select disable then the user can log in
When running Gpupdate /force we get the following error
The Group Policy Client Side Extension Group Policy Shortcuts may have caused the Group Policy Service to terminate unexpectedly. To prevent further failures inthe
Group Policy Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension may no
longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue recurs.
The Group Policy Client Side Extension Group Policy Internet Settings may have caused the Group Polcy Service to terminate unexpectedly. To prevent further failures
in the Group Policy Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension
may no longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue recurs.
Has anyone come across this before?
Thanks

Hi Dejul,
How is the issue going? Does this issue happen to all Windows 7 clients? I am not sure this can be helpful but we can give it a try to install the following hotfix.
Some Group Policy preferences are not applied successfully on computers that are running Windows Vista, Windows Server 2008, Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/kb/979731
Besides, please make sure that our clients are patched or updated to the latest.
An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2775511
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Best regards,
Frank Shen

Please wait for the group policy client - shutting down issues

Hi
I have issues with shutting down machines. When machine is connected to company's LAN everything works fine. However, if machine is connected to VPN - Juniper NC - 1 hour or more it always hangs when it is shutting down. When I shut down the machine
(verbose mode on), first stage is:
Please wait for the system Event Notification service.
This ends exactly
after 3 minutes. Next stage:
Please wait for the group policy client windows 7
...is never timed out (even after few hours). Machine never shuts down.
In Application logs there are always these 4 events when machine is unsuccessfully shutting down:
6005: The winlogon notification subscriber <Sens> is taking long time to handle the notification event (Logoff).
4627: The COM+ Event System timed out attempting to fire the Logoff method on event class {D5978650-5B9F-11D1-8DD2-00AA004ABD5E} for publisher and subscriber . The subscriber failed to respond within 180 seconds.
The display name of the subscription is "ISensLogon2". The HRESULT was 80010002.
6006: The winlogon notification subscriber <Sens> took 180 second(s) to handle the notification event (Logoff).
6005: The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (Logoff).
Sens is timed out after 3 minutes while there is no 6006 event for GPClient and machine is stuck there for ages (Please wait for the group policy client
stage). I noticed in System logs that machine always hangs if there is this error
5783: The session setup to the Windows NT or Windows 2000 Domain Controller \\server for the domain X is not responsive. The current RPC call from Netlogon on \\machine to \\server has been cancelled.
I made a group policy log and below you can see part of GPSVC log when machine is unsuccessfully shutting down:
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xe58
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Canceling pending calls
GPSVC(2d4.1cfc) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x71a
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Cancelled pending calls
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
GPSVC(438.1a04) 21:31:24:327 Waiting for user group policy thread to terminate.
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xe10
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Canceling pending calls
GPSVC(218.c88) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x525
GPSVC(2d4.1cfc) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x71a
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Cancelled pending calls
GPSVC(2d4.9c8) 21:31:24:327 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xdcc
GPSVC(218.1054) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0x20cc
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.9c8) 21:31:24:327 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xd90
GPSVC(218.1054) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.1cfc) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
GPSVC(218.d48) 21:31:24:342 Client_CompleteNotificationCall: failed with 0x525
GPSVC(218.d48) 21:31:24:342 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
GPSVC(218.1c04) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x525
GPSVC(218.1c04) 21:31:24:342 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Entering with event 0x2100
GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Entering with event 0x1264
GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
I tried with signing out from VPN before shutting down machine, I even switched off WiFi but machine still hung. If i tried to get GP results before shutting down machine it takes ages and it is stuck in "Getting the user name" stage.
Gpupdate /force never updates policy (It stops at Updating Policy...). I tired with installing different hotfixes which did not resolve the issue. I never have any
issues with logging in, no GP scripts are applied when user is logging off or on, no roaming profiles. The only issue is when machine needs to be shut down.
I excluded 1 machine from GP and left it on VPN for a few hours, several times. It always shuts down successfully. I applied GP back one by one and the one which is presumably causing an issue is Avecto which adds admin rights when VPN application
starts (event 100):
Process started with admin rights added to token.
Command Line: "C:\Users\User\AppData\Roaming\Juniper Networks\Setup Client\JuniperSetupClient.exe"
Process Id: 5540
Parent Process Id: 2252
Policy: EA-PrivilegeGuardSettings.UK Policy
Application Group: EA-PrivilegeGuardSettings.Applications Granted Admin Rights
Reason: <None>
File Name: c:\users\User\appdata\roaming\juniper networks\setup client\junipersetupclient.exe
Hash: 27D8463A913A802E555AEEF45717B122249AA993
Certificate: Juniper Networks, Inc.
Description: Juniper Setup Client
Application Type: exe
Product Name: Juniper Setup Client
Product Code: <None>
Upgrade Code: <None>
Product Version: 8.0.6.48695
I guess there is a DNS issues when machine is on VPN which leads that GP cannot be applied / updated. Not sure if or why Avecto would have an impact on this. When machine is trying to shut down it still somehow thinks it is connected to DC. What
I also noticed are several explorer crashes while machine is on VPN.
Does anyone have same issues? All machines are Dell with Juniper NC (VPN).
Thanks,

Hi,
According to event log, Winlogon process takes a long time to handle logoff event. That's to say winlogon process is waiting for response to logoff.
According to your description after, this problem is most probably caused by Avecto. You can try to disable or uninstall it temporarily for test.
To make further troubleshoot with this problem, you can try to use WPT (Windows Performance Tool) to make troubleshoot.
http://blogs.technet.com/b/askpfeplat/archive/2013/03/22/troubleshooting-windows-performance-issues-using-the-windows-performance-recorder.aspx
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Having problem with svchost.exe/ntdll.dll errors causing GPSVC (Group Policy Client) to crash preventing users from logging into the server.

Recently (within the past 2 weeks) I have noticed a few of our servers will have problems with the svchost.exe application causing the GPSVC (Group Policy Client) to crash. The only fix at that point is to reboot the server since the GPSVC service is tied
to svchost.exe and therefore is protected from being manually restarted.
I noticed the following errors when this occurs:
Log Name: Application
Source: Application Error
Date: 7/23/2013 4:35:26 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Server1.xxx.xxx.net
Description:
Faulting application name: svchost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000024
Fault offset: 0x00000000000cd7d8
Faulting process id: 0x46c
Faulting application start time: 0x01ce877f9476ac07
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d252d26d-f372-11e2-8ad4-005056ac00e8
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-07-23T08:35:26.000000000Z" />
<EventRecordID>158950</EventRecordID>
<Channel>Application</Channel>
<Computer>AAW19XM2.agency.nwie.net</Computer>
<Security />
</System>
<EventData>
<Data>svchost.exe</Data>
<Data>6.1.7600.16385</Data>
<Data>4a5bc3c1</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec4aa8e</Data>
<Data>c0000024</Data>
<Data>00000000000cd7d8</Data>
<Data>46c</Data>
<Data>01ce877f9476ac07</Data>
<Data>C:\Windows\system32\svchost.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>d252d26d-f372-11e2-8ad4-005056ac00e8</Data>
</EventData>
</Event>
All of our servers are running Server 2008 R2 Enterprise where we use Citrix to deliver desktop sessions to our users, but some are virtual and some are physical. This seemingly impacts our virtual machines more, and our VMs are hosted through VMWare, however,
about 5 months ago a similar error fired on a non-virtual machine:
Log Name: Application
Source: Application Error
Date: 2/27/2013 6:57:58 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: AAW29033
Description:
Faulting application name: svchost.exe_gpsvc, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000024
Fault offset: 0x00000000000cd7d8
Faulting process id: 0x6c0
Faulting application start time: 0x01ce14e1af313fd9
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: ed3d01c4-80d4-11e2-9128-b499baa9e5e8
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-02-27T11:57:58.000000000Z" />
<EventRecordID>286291</EventRecordID>
<Channel>Application</Channel>
<Computer>AAW29033</Computer>
<Security />
</System>
<EventData>
<Data>svchost.exe_gpsvc</Data>
<Data>6.1.7600.16385</Data>
<Data>4a5bc3c1</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec4aa8e</Data>
<Data>c0000024</Data>
<Data>00000000000cd7d8</Data>
<Data>6c0</Data>
<Data>01ce14e1af313fd9</Data>
<Data>C:\Windows\system32\svchost.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>ed3d01c4-80d4-11e2-9128-b499baa9e5e8</Data>
</EventData>
</Event>
I've searched and cannot seem to find any information as to what may be causing this, or even really where to start. Would someone be able to help me identify what might be causing this event, specific with the Exception code: 0xc0000024, which causes
the Group Policy Client service to stop?

You still out there looking at things? If so I have an update. The issue hasn't stopped, even though it did seemingly die down for awhile, however, it is now back with a vengeance.
I am able to force it to happen by killing the svchost process that is hosting GPSVC. If I run gpupdate /force, then logout/login it does get GPSVC running again. Furthermore, if I simply start svchost again via the Task Manager GPSVC starts running again.
When I access the server remotely with KVM it acts just like it does as if I'm logging into it via Citrix/RDP which for Admin IDs gives an error saying "Failed to connect to a windows service. Windows could not connect to the Group Policy Client service...",
however, normal user accounts just get a message when logging into the server "The Group Policy Client Service Failed the Logon. Access is denied."
I haven't opened a case with Microsoft yet, but we about ready to because of the increase in these errors.
If you have any further suggestions that would be great, otherwise I'll provide an update once I get word back from Microsoft.
**EDIT -- apparently I mistook the the server's SCM's actions as my own. I was able to successfully crash the GPSVC service by killing the hosting svchost process, however, after I crashed it and let it sit crashed for awhile when I attempted
to restart either by starting a svchost task, or running gpupdate /force it failed. Either that, or there is a timing issue where if we don't restart the svchost process, or run gpupdate /force quickly enough it won't be able to recover without a reboot.

The Group Policy Client service failed the sign-in The universal unique identifier (UUID) type is not supported

Similar Messages

Maybe you are looking for