none
GPO Replication Bad RRS feed

  • Question

  • I have (2) new 2016 domain controllers.  One has DNS and one does not.
    I have an existing 2012 domain controller.
    GPO is not replicating from the 2012 to 2016 servers.

    gpupdate /force works fine on the 2012 server but I am getting the following errors on the 2016 servers.

    The processing of Group Policy failed. Windows attempted to read the file \\xxxxx.prv\SysVol\xxxxxxxx\Policies\{97650F49-8D70-4E2B-B335-1AFAC7C59F87}\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:
    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.

    I have verified that I can ping the server names from each other.
    I have also checked out a Health Report in DFS and not gotten any replication errors.

    I see this Policy on the 2012 server but not in \\domainname\sysvol.

    Can I just copy and paste it into the \\domainname\sysvol folder?

    Thanks in advance for your help.



    • Edited by SEBERCAW Monday, May 20, 2019 6:48 PM
    Monday, May 20, 2019 6:45 PM

Answers

  • Hi

    Does your ad replication work well ?

    If yes, it seems like a just NETLOGON folder replication issue. 

    Recommend resolve this issue by modify registry entry on your problematic dc.

    HKLM --> System --> CurrentControlSet --> Services --> ntfrs --> Parameters --> Backup/Restore --> Process at Startup --> BurFlags --> changed value as "D2" (Non-Authrotive Restore).

    Best Regards,

    Fan



    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    • Marked as answer by SEBERCAW Tuesday, May 21, 2019 7:10 PM
    Tuesday, May 21, 2019 3:33 AM