Missing CN=DFSR-LocalSettings on a Domain Controller?

Question

Hi Experts,

This new DC has replication issues with the PDC and its not replicating Sysvol and Netlogon shares. Then we found this article on how we could fix it by performing an Authoritative DFSR Sync. However, as we follow the guide, we bump into this issue. This DC is missing the CN=DFSR-LocalSettings in ADSI Edit? How do we fix this so that we could attempt the Authoritative DFSR Sync to fix the original issue of Sysvol and Netlogon shares? Please advise.

Thank you so much!

Logbi

Answer 1

Not a lot to go on. What operating systems are being used? Was health confirmed 100% before adding the new one? May still be using FRS? In which case this one may be more applicable.
https://support.microsoft.com/en-us/help/257338/troubleshooting-missing-sysvol-and-netlogon-shares-on-windows-domain-c

--please don't forget to Accept as answer if the reply is helpful--

Answer 2

HI DSPatrick,

The existing DC is on Windows 2012 R2 Standard and CN=DFSR-LocalSettings can be seen in here. For the the new DC with missing CN=DFSR-LocalSettings, its on Windows 2016 Standard. Dcdiag /q shows this result by the way.

Thank You!

Logbi

Answer 3

Still a bit vague. Might try demote, reboot, and promo it again. Should work seamlessly assuming existing health was 100%

--please don't forget to Accept as answer if the reply is helpful--

Answer 4

If you're using older FRS you can follow along here.
https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi
or for DFSR follow along here.
https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

If you find 48 then using DFSR, if null or 0, 16, 32 then FRS or some state of migration from FRS

Answer 5

Hi,
 
Just want to confirm the current situations.
 
Please feel free to let us know if you need further assistance.
 
Best Regards,
Vicky