Advertisement
This seems to be a common thing but I can’t find an answer that works for me. Every time I create a new GPO I get:<\/p>\n
The processing of Group Policy failed. Windows attempted to read the file \\DOMAIN.local\\SysVol\\DOMAIN.local\\Policies{04AB5BD4-8E44-4167-B707-8A3FF99721AF}\\gpt.ini from a domain controller and was not successful. Group Policy settings 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:
\na) Name Resolution/Network Connectivity to the current domain controller.
\nb) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
\nc) The Distributed File System (DFS) client has been disabled.<\/p>\n
A. They can see eachother by nane
\nB. This is the truth but even after days it doesn’t replicate
\nC. This is Enabled on both DCs.<\/p>\n
Any thoughts?<\/p>\n
Thanks<\/p>","upvoteCount":1,"answerCount":4,"datePublished":"2018-06-07T12:50:42.000Z","author":{"@type":"Person","name":"benspain","url":"https://community.spiceworks.com/u/benspain"},"suggestedAnswer":[{"@type":"Answer","text":"
This seems to be a common thing but I can’t find an answer that works for me. Every time I create a new GPO I get:<\/p>\n
The processing of Group Policy failed. Windows attempted to read the file \\DOMAIN.local\\SysVol\\DOMAIN.local\\Policies{04AB5BD4-8E44-4167-B707-8A3FF99721AF}\\gpt.ini from a domain controller and was not successful. Group Policy settings 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:
\na) Name Resolution/Network Connectivity to the current domain controller.
\nb) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
\nc) The Distributed File System (DFS) client has been disabled.<\/p>\n
A. They can see eachother by nane
\nB. This is the truth but even after days it doesn’t replicate
\nC. This is Enabled on both DCs.<\/p>\n
Any thoughts?<\/p>\n
Thanks<\/p>","upvoteCount":1,"datePublished":"2018-06-07T12:50:42.000Z","url":"https://community.spiceworks.com/t/sysvol-not-replicating-between-2-2012-dcs/655821/1","author":{"@type":"Person","name":"benspain","url":"https://community.spiceworks.com/u/benspain"}},{"@type":"Answer","text":"
I would try the command line tool repadmin.<\/p>\n
On the server that hasn’t been correctly sync’d, run repadmin /syncall<\/p>\n
If it doesn’t work, it should reveal why, or at least a clue.<\/p>","upvoteCount":0,"datePublished":"2018-06-07T13:00:18.000Z","url":"https://community.spiceworks.com/t/sysvol-not-replicating-between-2-2012-dcs/655821/2","author":{"@type":"Person","name":"mikedinit","url":"https://community.spiceworks.com/u/mikedinit"}},{"@type":"Answer","text":"
Make sure each DC is pointing to the other DC for DNS as its primary and itself for secondary.<\/p>\n
Run DCDIAG from an elevated command prompt on both DC’s. If there are problems it should give you insight on what the problems are.<\/p>","upvoteCount":0,"datePublished":"2018-06-07T13:03:11.000Z","url":"https://community.spiceworks.com/t/sysvol-not-replicating-between-2-2012-dcs/655821/3","author":{"@type":"Person","name":"da-schmoo","url":"https://community.spiceworks.com/u/da-schmoo"}},{"@type":"Answer","text":"