If DFS (Distributed File System) does not work properly between domain controllers, some important problems may occur.
To summarize these briefly:
- SYSVOL and NETLOGON Replication: SYSVOL and NETLOGON folders cannot be replicated between domain controllers. This may cause group policies (GPO) and login scripts to not work properly.
- Data Inconsistency: Data inconsistencies may occur between domain controllers. For example, changes made in one domain controller cannot be reflected in others.
- User and Group Management Problems: Since changes made to users or groups do not reach other domain controllers, users may experience problems logging in or accessing resources.
- Network Performance and Reliability: If DFS does not work, it may negatively affect file sharing and access speed on the network. In addition, backup and disaster recovery processes may also be at risk.
In such a case, it is important to first check the event logs (Event Viewer) and determine the source of the problem.
What is DFS – Distributed File System?
Distributed File System is a feature offered by Microsoft in Windows Server operating systems. DFS facilitates file sharing and replication, allowing files on the network to be managed more efficiently. It has two main components:
- DFS Namespace (DFS-N): Creates a virtual file system to make it easier for users to access files. This allows users to access files through a single logical structure without needing to know the physical server locations.
- DFS Replication (DFS-R): Allows files to be synchronized between different servers. This reduces network traffic by copying only the changed parts of file changes.
Error Log:
The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\Domain. This server has been disconnected from other partners for 1063 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.
Additional Information:
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: XXXXXXXXXXXXXXXXXXXXXXXX
Replication Group Name: Domain System Volume
Replication Group ID: XXXXXXXXXXXXXXXXXXXXXXXX
Member ID: XXXXXXXXXXXXXXXXXXXXXXXX
Restarting Replication
The log says that it has not been able to replicate for 1063 days. Therefore, we need to enter a higher value. After replication starts, you can change it back to the default day of 60. You need to run the code below as admin.
wmic /namespace:\\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=1100The DFS Replication Diagnostic Tool (dfsrdiag.exe) can be used to examine DFS-related statuses.
Reviewing replication status:
dfsrdiag ReplicationState /member:<ServerName>Checking the status of Backlogs awaiting replication:
dfsrdiag Backlog /rgname:<ReplicationGroupName> /rfname:<ReplicatedFolderName> /mem:<ServerName>Checking health status:
dfsrdiag Health /member:<ServerName>Manually start replication:
dfsrdiag PollADIt may be useful to review the MS Learn page “DFSR SYSVOL fails to migrate or replicate, SYSVOL not shared, Event IDs 8028 or 6016” regarding the subject.
See you in the next article.