SYSVOL on newly promoted DC is not synchronising, but replication looks ok?

I came across this scenario recently following some network issues in an environment I'm working in.

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. 

  
 

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