Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You experience issues with DFS replication in a Windows Server 2003 R2-based AD environment
Article ID: 967507 - View products that this article applies to.
RAPID PUBLISHINGRAPID PUBLISHING ARTICLES PROVIDE INFORMATION IN RESPONSE TO EMERGING OR UNIQUE TOPICS, AND MAY BE UPDATED AS NEW INFORMATION BECOMES AVAILABLE.
Consider the following scenario:
DFSR keeps track of the root folder FID and processes a mechanism that is called tombstoning. When the server and the replicated folder are removed from the replica set data that is kept in Active Directory, the content set is kept in a tombstoned state.
The same folder is added back to the replica set, which is the same folder and therefore is the same FID, DFSR will not perform the sync again.
This problem occurs because the removal of the server and folder from the replication group is the result of any unintentional change or Active Directory replication latency.
To work around this issue, use one of the following methods.
Method 1Delete the original folder and then create another folder that has the same name.
Method 2Disable the replicated folder, delete the content, and then re-enable the folder.
MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE FOR ANY PURPOSE. THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED HEREIN AT ANY TIME.
Article ID: 967507 - Last Review: March 2, 2009 - Revision: 1.0