Windows server 2019: Troubleshoot missing SYSVOL and Netlogon shares

During a systemcrash, one of my domain controllers stopped showing the SYSVOL and Netlogon shares, I did a lot of debugging, and found out, that the DFS-R that was going on in Win2019 (Not NTFRS anymore :-)) what corrupted.

So the event log, on the failing DC showed me this:

And thus I restarted, waited, and waited som more, it never got passed the inititial point.

Luckily Microsoft have a solution for this, found here:

Troubleshoot missing SYSVOL and Netlogon shares for Distributed File System (DFS) Replication – Windows Server | Microsoft Docs

ad that article lead me to this one:

Force synchronization for Distributed File System Replication (DFSR) replicated sysvol replication – Windows Server | Microsoft Docs

So firstly I debugged with theese commands:

  • Check for the SYSVOL share

    You may manually check whether SYSVOL is shared or you can inspect each domain controller by using the net view command:

    Console

    For /f %i IN ('dsquery server -o rdn') do @echo %i && @(net view \\%i | find "SYSVOL") & echo
    
  • Check DFS Replication state

    To check DFS Replication’s state on domain controllers, you may query WMI. You can query all domain controllers in the domain for the SYSVOL Share replicated folder by using WMI as follows:

    Console

    For /f %i IN ('dsquery server -o rdn') do @echo %i && @wmic /node:"%i" /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo WHERE replicatedfoldername='SYSVOL share' get replicationgroupname,replicatedfoldername,state
    

    The state values can be any of:
    0 = Uninitialized
    1 = Initialized
    2 = Initial Sync
    3 = Auto Recovery
    4 = Normal
    5 = In Error

And mine showed this:

So clearly DC01 has a status of “2”, which means “Initial Sync”, but I never moved across that part :-/

But I simply, (I can use that word now :-D) I followed AL steps in this article, and after that i ran the same command again:

Force synchronization for Distributed File System Replication (DFSR) replicated sysvol replication – Windows Server | Microsoft Docs

Also confirmed in the event log:

Hooray 🙂

To fix older systems running NTFRS (Pre 2016) you can use theese steps to fix the same:

Use BurFlags to reinitialize File Replication Service (FRS) – Windows Server | Microsoft Docs

Leave a Comment

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close