Hi Fredrik,
Intra-site replication is based on a notify pull process. 5 minutes (.by
default in Windows 2000 - it's 15 seconds in Windows Server 2003) after a
change is made a domain controller starts notifying its replication partners
in the same site that it has updates. There is also a delay of 30 seconds
(.by default in Windows 2000 - it's 3 seconds in Windows Server 2003)
between notifying subsequent replication partners so the domain controller
does not get overwhelmed. This article contains details on how these values
can be changed (just don't set them lower than 15/3 or else you will have
excessive replication traffic):
How to Modify the Default Intra-Site Domain Controller Replication Interval
http://support.microsoft.com/?id=214678
There are some operations, however, that don't use the above delays -
replication happens immediately within a site. This is known as urgent
replication and you can find a list of triggers here:
Urgent Replication Triggers in Windows 2000
http://support.microsoft.com/?id=232690
In contrast, inter-site replication is based on a schedule and does not use
a notify pull process by default (this also means urgent replication does
*not* cross the site boundary by default). To set the replication interval
on inter-site connections it depends if the connections were created
manually or automatically by the KCC (however, 15 minutes is the minimum
scheduled interval).
If you have automatically generated connections (the default) you need to
edit the replication interval on the site links:
HOW TO: Configure Site Link Replication in Windows 2000
http://support.microsoft.com/?id=321253
(under "Configure the Site Link Replication Frequency")
If you have manually generated connections you need to edit the replication
interval on the connections:
Manually created inter-site Connection Objects Do Not Inherit Replication
Schedule from Site Link
http://support.microsoft.com/?id=305179
You can also enabled the notify pull process that is used for intra-site
replication on a site link (i.e. so intra-site replication also uses the
notification process), but it's not recommended. While enabling notification
across site links will allow urgent replication to happen immediately,
normal non-urgent replication will also trigger replication.
Password replication is like non-urgent replication but with an aditional
twist. When a password is changed it is preferentially replicated to the PDC
emulator for the domain (even if the DC the password was changed on and the
PDC emulator are not in the same site by default). Have a look at this KB
article for more details:
New Password Change and Conflict Resolution Functionality in Windows
http://support.microsoft.com/?id=225511
Mike
------------------------------------------------------------------
Mike Aubert
MCSE, MCSD, MCDBA
(e-mail address removed)
Note the "news2" in my email address is temporary and may be changed in the
future, remove it to email me at my Permanente address.
This posting is provided "AS IS" with no warranties, and confers no rights.
