Forcing Replication with repadmin
repadmin has a few primary commands you can use to force replication as shown in the following table.
Tip
If you are having problems with replication and
cannot force replication, check DNS. One important check is to ensure
that DNS has created SRV records. You can stop and restart the netlogon service to re-create SRV records with the net stop netlogon and net start netlogon commands.
| repadmin Replication Commands | Comments |
|---|
Synchronize a DC with all partners.
| Synchronizes
a specified DC with all replication partners.
This should generate callback messages indicating replication is in
progress, replication has completed, and that syncall finished. |
Force replicate with a specific DC.
repadmin /replicate target-DC
source-DC domain-DN
C:\> repadmin /replicate dc2
dc1 dc=pearson,dc=pub
| Triggers immediate replication of the specified directory partition to the destination DC from the source DC.
This performs the same actions as selecting Replicate Now, as shown in Figure 2. You can access this by clicking Start, Administrative Tools, AD Sites and Services. Additionally, it works the same way if the DCs are in different sites, as shown in Figure 3. |
Recalculate replication topology.
repadmin /kcc target-DC
C:\> repadmin /kcc dc1
| Forces
the knowledge consistency checker (KCC) to recalculate the replication
topology and re-create replication connections if needed. The KCC runs
every 15 minutes by default. The example forces the KCC to run on the
domain controller dc1.
Note
You can run this for each DC in your domain from a single DC. It doesn’t need to be run locally.
|
Tip
repadmin has a
rich set of commands that you can use to monitor and troubleshoot
replication. This chapter doesn’t attempt to show them all. However, if
you want to dig deeper, check out the TechNet web page: http://technet.microsoft.com/library/cc770963.aspx.
