none
FRS not replicating SysVol

    Question

  • Hi,

    I have 3 domain controllers running windows server 2008 R2 which is still using FRS for sysvol replication. On my 1st domain controller which holds all the FSMO roles, I have errors 13552 and 13555 in FRS event viewer while the 2nd and 3rd DChave 13508. When I create a GPO in any Domain controllers, the files appears in the 1st DC sysvol but it is not replicating to the 2nd and 3rd. 

    I have read some resolution below but cannot decide which of my DCs is having a good copy. My 1st DC do not have the event "Event ID - 13516. "The File Replication Service is no longer preventing the computer <computer name> from becoming a domain controller. ... An event number 13516 in the File Replication Service event log indicates that replication is complete and is working properly." for years and I suspect it cannot be used for client authentication. Which server should I force FRS replication by applying registry burflag D2 key to resolve this?

    https://community.spiceworks.com/topic/555565-ntfrs-issues
    http://kpytko.pl/active-directory-domain-services/non-authoritative-sysvol-restore-frs/


    https://community.spiceworks.com/topic/555565-ntfrs-issues

    http://kpytko.pl/active-directory-domain-services/non-authoritative-sysvol-restore-frs/

    regards,

    Chiew Sheng

    Thursday, December 6, 2018 5:30 PM

Answers

All replies

  • From what you described it sounds like you should do an authoritative restore using "1st DC" as source. More info here to look at.

    https://blogs.technet.microsoft.com/janelewis/2006/09/18/d2-and-d4-what-is-it-for/

    https://support.microsoft.com/en-us/help/315457/how-to-rebuild-the-sysvol-tree-and-its-content-in-a-domain

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Thursday, December 6, 2018 5:47 PM
  • Hi,

    You can use the solution provided by Dave. 

    If you still have the replication , you can demote and promote impacted DC. 

    Once you problem fixed, I recommend you to migrate FRS to DFS for SYSVOL replication.  

    FRS is a legacy replication system and will be unsupported by Windows 2019.


    Please don't forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/

    • Marked as answer by ironmanwannabe Saturday, December 8, 2018 1:59 AM
    Thursday, December 6, 2018 7:38 PM
  • Thanks for the feedback. I will try the solution by Dave. 

    >If you still have the replication , you can demote and promote impacted DC. 

    You mean to demote and promote the 2nd and 3rd DC if issue still persist?

    Friday, December 7, 2018 1:08 AM
  • Thanks for the feedback. I will try the solution by Dave. 

    >If you still have the replication , you can demote and promote impacted DC. 

    You mean to demote and promote the 2nd and 3rd DC if issue still persist?

    Yes.


    Please don't forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/

    Friday, December 7, 2018 10:03 AM