DFRS and SYSVOL Replication Issues

August 15, 2017

tags: , ,
no comments

Introdcution

Due Active Directory replication consistency issue, the DFSR may not work as expected. The issue may include, but not limited to, dcdiag errors on a missing attributes values such as msDFSR-ComputerReference.

Resolution

a. Review the following Active Directory attributes values

msDS-AdditionalDnsHostName

Value: Usually should be empty

image

msDFSR-MemberReference

Value: CN=TESTDC1,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=testdom,DC=local

image

msDFSR-ComputerReference

Value: CN=NTDS Settings,CN=TESTDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=testdom,DC=local

image

ServerReference 

Value: CN=NTDS Settings,CN=TESTDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=testdom,DC=local

image

B. Replicate the DFRS SYSVOL from a good standing Domain Controller.

In a case of a single Domain Controller in the Forest without a backup, you may need to update the attributes values manually and reboot the Domain Controller. However, its highly recommended to create a full backup to the Domain Controller before applying any change.

For furtner information please review:

How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like “D4/D2” for FRS)

Troubleshooting File Replication Service

Rename a domain controller

Add comment
facebook linkedin twitter email