• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 642
  • Last Modified:

Group Policy Error

We are receiving the following Group Policy error on clients connected to SBS 2011.

Updating Policy...

User policy could not be updated successfully. The following errors were encount

The processing of Group Policy failed. Windows attempted to read the file \\domainname.local\SysVol\domainname.local\Policies\{2370F62D-14FD-400F-B8C7-F6DDE7AC3
A58}\gpt.ini from a domain controller and was not successful. Group Policy setti
ngs may not be applied until this event is resolved. This issue may be transient
 and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller
 has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
Computer Policy update has completed successfully.

To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
rom the command line to access information about Group Policy results.


A) There is not a DNS communication issue with the server.
C) DFS is running on the server.

What is your recommendation for tracking down this issue?

Thanks for your help!
1 Solution
Will SzymkowskiSenior Solution ArchitectCommented:
Have you tried the following steps to ensure that replicaiton is operating accordingly...

Repadmin /replsum
Repadmin /showrepl

DCDiag /v

Ensure that the out-put of all of those commands come back successful.

Also are you able to read that group policy form the users workstation? Domain users should have read access over this.

SandeshdubeySenior Server EngineerCommented:
You need to first trace which policy is not applied.On the DC open cmd and run gpotool you will get the GPO name and policy quid.Check is this GPO required or its orphan GPO still present in AD.If gpotool command is not working you need to download resource kit tool for the same to work.

Ensure correct dnd setting on DC and client as this
Best practices for DNS client settings on DC and domain members.

Post the dcdiag and repadmin as suggested.
MPATechTeamAuthor Commented:
Very helpful feedback. Thank you both!

Will be in touch with more info shortly!
Check any Netlogon errors in the clients. It could be connectivity. Network issue.

Also check any sysvol replication issues in the domain controller.


MPATechTeamAuthor Commented:
Sorry for my delay in awarding these points.

It was indeed a replication issue between domain controllers.

I appreciate your advice and assistance on this!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now