A common scenario is two domain controllers at different sites. Since the connection between the two site is likely to be slow, you want to keep as much traffic as possible from crossing over those links. If you are at site A and you log on to the network, you would want a domain controller on site A to authenticate you, rather than using the slow (and potentially unreliable) connection between to have the controller in site B authenticate you.
For some reason you decided you need to force Active Directory Replication between Domain controllers follow these steps
Start–>Programs—>Administrative Tools—> Active Directory Sites and Services (For windows 2000 Server)
Start–>Programs—>Administrative Tools—> Active Directory Sites and Services (For windows 2003 Server)
Now expand Sites from left pane –> your site name –> Yourservername–> NTDS Settings –>Now select the <automatically generated> object from right pane
right click on it and select replicate now
This causes the Yourservername to PULL from the DC represented by the connection object
We replicate so that each Domain Controller maintains the same data providing load balancing, fault tolerance and geographic distribution where necessary
Incoming search terms:
- force active directory update (55)
- how to replicate domain controller windows 2003 (54)
- force dns replication between domain controllers (49)
- force dns replication server 2008 (47)
- force dns replication windows 2008 (44)
- yhs-coles_001 (36)
- force ad update (36)
- replicate domain controller 2003 (35)
- force dns replication (30)
- force replication between domain controllers (30)