Home / server / Questions / 547963
In Process
Mark
Asked: 2013-10-23 20:25:55 +0800 CST

DFS Replication complaining about being disconnected, but there is only one DC

  • 772

I'm seeing this error in my event log on my (only) domain controller:

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 295 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.

In the past (maybe 295 days ago?) there was two domain controllers for a few minutes, while I renamed the domain. This seemed to me the easiest way to accomplish that complex and evidently error-prone task. Now, and for a long time, there has been only one DC in the domain, and that is all there should ever be.

I haven't been able to see how to use the snap-in to remove the server from the replication group, and honestly, I'm not sure I really want to do that, as there is only one server.

What can I do to eliminate this DFSR error?

active-directory

1 Answers

  1. As part of the process of promoting a member server to Domain Controller, that new DC is also included on the DFS replication group in charge of replicate SYSVOL. As your DCs are Windows Server 2012 (I asume both of them have the same versión) this is the standard mechanism for replicating DFS. In Windows Server 2008 the default way to replicate SYSVOL changed from FRS to DFS.

    So, I would recomend you in order to solve the problem, go to DFS Management Console, Edit SYSVOL replication group and Delete the old DC that you promoted and is no longer in use.

    By the way, if you have this issue with the DFS it's highly probable that you may perform some aditional cleaning tasks if you didn't demote the DC using DCPromo.

    Hope this helps!!

    Regards

    • 1