DFS Replication (DFSR) Fix

Last Updated: February 24th, 2023Published On: January 12th, 2023By

Sample Event Log Entry

Source: DFSR

Date:
2/25/2016 3:14:40 PM

Event ID:
4012

Task Category:
None

Level:
Error

Keywords:
Classic

User:
N/A

Computer:
TTLCloudDC01.ttlcloud.local

Description:
The DFS Replication service stopped replication on the folder with the following local path: C:WindowsSYSVOLdomain. This server has been disconnected from other partners for 107 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.

To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.

FIX

  • Stop the DFS Replication Service: net stop DFSR
  • In the ADSIEDIT.MSC tool, modify the following DN and two attributes on the domain controller you want to make authoritative (preferably the PDC Emulator, which is usually the most up to date for SYSVOL contents):
    • CN=SYSVOL Subscription,CN=Domain System Volume,CN=DFSR-LocalSettings,CN=<the server name>,OU=Domain Controllers,DC=<domain>
      • msDFSR-Enabled=FALSE
      • msDFSR-options=1
    • Here is where you will find that key:
  • Start the DFS Replication service: net start DFSR
  • You will see Event ID 4114 in the DFSR event log indicating SYSVOL is no longer being replicated
  • On the same DN above, set it back to TRUE: msDFSR-Enabled=TRUE
  • Force Active Directory replication throughout the domain and validate its success on all DCs: repadmin /syncall /AdP
  • Run the following command from an elevated command prompt on the same server that you set as authoritative: DFSRDIAG POLLAD
  • You will see Event ID 4602 in the DFSR event log indicating SYSVOL has been initialized. That domain controller has now done a “D4” of SYSVOL.

Notes

The KB article doesn’t say whether you should leave msDFSR-options=1. I didn’t change it back from 1, but it seems it changed itself back to 0 somewhere during the above process. Verify that it eventually goes back to 0.

Categories: Blog, Product SpecificTags: Views: 5515