Immediate Replication Occurs After You Create Inter-Site Connection Objects (294208)

SYMPTOMS

Immediate replication may occur when a new replication link is created for the first time, regardless of the schedule that is defined in the connection object.

Branch-office deployments consist of a hub site that hosts bridgehead servers and many branch offices that are connected to the hub site. These connections are often over slow links. In such scenarios, the creation of inter-site connection objects by Knowledge Consistency Checker (KCC) is sometimes disabled in favor of manual connection objects that you create by using scripts. KCC runs every fifteen minutes and checks the replication topology that is defined with the connection object. This is what you see in the Active Directory Sites snap-in under NTDS Settings. KCC then turns new connection objects into replication links, which are represented by the repsFrom attribute of the naming contexts.

The problem is that immediate replication occurs when a new replication link is created for the first time, regardless of the schedule that is defined in the connection object. This issue occurs only with Remote Procedure Call (RPC) sources, not with Simple Mail Transport Protocol (SMTP) sources.

CAUSE

When a new replication link is created, an initial replication request is queued, which may not be the behavior that you want. The following issues also exist:

Scripts may be used to update connection objects across all domain controllers in the forest simultaneously. If all sites begin to replicate immediately based on connections from new source domain controllers, the outbound bridgehead servers can be overwhelmed by requests and their CPU loads can rise to 100 percent. The staggered schedule that is defined in the new connection objects is not used.
During massive deployments, many domain controllers can be deployed simultaneously. Procedures and scripts are used to build the new domain controllers and to create new inter-site connection objects. If they are all created at the same time, this can cause an overload on the bridgehead servers because they cannot process such a large number of immediate replication requests.

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

242780 How to Disable the Knowledge Consistency Checker From Automatically Creating Replication Topology

244368 How to Optimize Active Directory Replication in a Large Network

245610 How to Disable the Knowledge Consistency Checker Inter-Site Topology Generation for All Sites

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

   Date         Time   Version        Size     File name
   ----------------------------------------------------------------
   21-Jun-2001  03:23  5.0.2195.3737  355,088  Advapi32.dll
   21-Jun-2001  03:23  5.0.2195.3738  142,608  Kdcsvc.dll
   13-Jun-2001  20:43  5.0.2195.3738  209,008  Kerberos.dll
   29-May-2001  12:26  5.0.2195.3739   69,456  Ksecdd.sys
   13-Jun-2001  20:32  5.0.2195.3738  501,520  Lsasrv.dll (128-bit)
   13-Jun-2001  20:32  5.0.2195.3738  501,520  Lsasrv.dll (56-bit)
   13-Jun-2001  08:32  5.0.2195.3738   33,552  Lsass.exe
   21-Jun-2001  03:23  5.0.2195.3758  909,072  Ntdsa.dll
   21-Jun-2001  03:23  5.0.2195.3762  382,224  Samsrv.dll
   29-May-2001  12:53  5.0.2195.3649  128,784  Scecli.dll
   30-May-2001  05:19  5.0.2195.3649  299,792  Scesrv.dll

MORE INFORMATION

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base: