After you re-add a member server to a DFS replication group in Windows Server 2003 R2, initial replication does not occur on the member server, and changes in the replicated folder are replicated unexpectedly to other replication partners

To work around this problem, use one of the following methods.

Method 1: Disable the member server instead of deleting it

When you want to temporarily exclude a member server from a DFS replication group, we highly recommend that you disable the server on the Memberships tab in the DFS Management snap-in. If you want to include the member server in the DFS replication group later, you can just enable the member server without encountering the problem that is described in this article.

Note We recommend that you use Method 1.

Method 2: Wait for more than 60 days to add the member server to the DFS replication configuration

When you delete a member server from a DFS replication group, the member server will be marked by using a 60-day tombstone flag in the DFS replication database. If the member server is added to the DFS replication group within this 60-day period, this tombstone flag will be deleted, and the original server objects for this member server in the DFS replication database will be used. Therefore, the member server will not perform the initial replication, and content in the replicated folder is replicated unexpectedly.

Method 3: Do not change the replicated folder

After you re-add the member server, content in the replicated folder that is newer than the data on other replication partners is replicated unexpectedly. Therefore, verify that the data in the replicated folder is older than the data on other replication partners before you re-add the member server. To achieve this, do not change the replicated folder on the member server that you want to re-add later.