MPATechTeam
asked on
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
ered:
The processing of Group Policy failed. Windows attempted to read the file \\domainname.local\SysVol\
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!
Updating Policy...
User policy could not be updated successfully. The following errors were encount
ered:
The processing of Group Policy failed. Windows attempted to read the file \\domainname.local\SysVol\
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!
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.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
Post the dcdiag and repadmin as suggested.
Ensure correct dnd setting on DC and client as this
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
Post the dcdiag and repadmin as suggested.
ASKER
Very helpful feedback. Thank you both!
Will be in touch with more info shortly!
Will be in touch with more info shortly!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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!
It was indeed a replication issue between domain controllers.
I appreciate your advice and assistance on this!
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.
Will.