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\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!
MPATechTeamAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.

Will.
0
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.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/

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

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

Also check any sysvol replication issues in the domain controller.

http://theitbros.com/the-processing-of-group-policy-failed-windows-attempted-to-read-the-file/

http://blog.practicaltech.ca/2011/02/sysvol-replication-issues.html
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.