Article ID: 321153 - View products that this article applies to.
This article was previously published under Q321153
In Microsoft Windows 2000, you may have to disable replication on a particular domain controller to isolate that server for testing or to run restore processes. With this functionality, you can fully test changes on a destination domain controller before you implement them in your organization. It is a good idea to do this kind of testing when you implement security changes, Group Policy changes, and authoritative restore procedures. In order to test schema changes, you should not disable replication on the schema master. Instead, follow the process in http://technet.microsoft.com/en-us/library/testing-for-active-directory-schema-extension-conflicts(WS.10).aspx
Repadmin.exe is a command-line tool from the Microsoft Windows 2000 Resource Kit that is included in the Support\Tools folder on the Windows 2000 Server CD-ROM.
To enable or disable replication for a destination computer, follow these steps:
Warning These flags do not prevent replication when replication is forced by using other repadmin commands or by using other applications that use the Replication Management APIs. The /replicate, /sync, and /syncall repadmin commands do not replicate when the Active Directory connection has been disabled and when the Knowledge Consistency Checker (KCC) has already run and has removed the replication link. (This link is visible as the output of the repadmin /showrepl command). At this point, you are safe from unwanted replication by delegated administrators who cannot change the Active Directory topology because the repadmin /add command does not support the /force option.
Article ID: 321153 - Last Review: February 23, 2011 - Revision: 3.1