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:
ad that article lead me to this one:
So firstly I debugged with theese commands:
- Check for the
SYSVOLshareYou may manually check whether
SYSVOLis shared or you can inspect each domain controller by using the net view command:ConsoleFor /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
SYSVOLShare replicated folder by using WMI as follows:ConsoleFor /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,stateThe
statevalues 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:
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