After promoting an additional WS2012 Domain Controller (i.e. utilises DFS-R for SYSVOL replication), one or more of the following symptoms may present: 

• No content is synchronised to the SYSVOL folder
• NetLogon and SYSVOL folders are not shared
• dcdiag /test:advertising produces the following error:

  Warning: DsGetDcName returned information for \\DC1 when we were trying to reach <DC2>. SERVER IS NOT RESPONDING or IS NOT SUITABLE

• Event 4604 indicating successful SYSVOL initialisation is not logged
• The DFS-R debug logs indicate SYSVOL failure
• However replication appears to be operating correctly when checking event logs and repadmin.

Resolution

Once any network issues are resolved, we need to persuade SYSVOL to replicate to allow the server to complete the Domain Controller promotion process and advertise services. 

• Ensure the Manage auditing and security log user rights assignment includes the Administrators built-in group as per article DFSR SYSVOL Fails to Migrate or Replicate, SYSVOL not shared, Event IDs 8028 or 6016.
• Attempt a non-authoritative synchronisation of SYSVOL as per article How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS).
• If the above steps don't bring any joy, go for Performing an authoritative synchronization of DFSR-replicated SYSVOL. This is the DFS-R equivalent of the old FRS restore. During this process the msDFSR-Options attribute of a functioning DC (preferably the PDCE) is set to 1:

  

Validation

Once the situation resolves, you will see all the normal signs of a happy DC:

• Content is synchronised to SYSVOL
• NetLogon and SYSVOL folders are shared
• Event 4604 DFSR is logged:

  The DFS Replication service successfully initialized the SYSVOL replicated folder at local path <path>\SYSVOL\domain. This member has completed initial synchronization of SYSVOL with partner <DC>.

• The DC passes dcdiag advertising test.

Till next time

Viszontlátásra