You want to change the interval at which the KCC runs.
220.127.116.11 Using a graphical user interface
18.104.22.168 Using a command-line interface
> reg add HKLM\System\CurrentControlSet\Services\NTDS\Parameters /v "Repl topology[RETURN] update period (secs)" /t REG_DWORD /d <NumSecs>
22.214.171.124 Using VBScript
' This code changes the interval in which the KCC runs. ' ------ SCRIPT CONFIGURATION ------ intNumSecs = <NumSecs> ' Number of seconds between intervals ' 900 is default ' ------ END CONFIGURATION --------- strNetlogonReg = "SYSTEM\CurrentControlSet\Services\NTDS\Parameters" const HKLM = &H80000002 Set objReg = GetObject("winmgmts:root\default:StdRegProv") objReg.SetDWORDValue HKLM, strNetlogonReg, _ "Repl topology update period (secs)", _ intNumSecs WScript.Echo "KCC interval set to " & intNumSecs
By default, the KCC checks its connections ever 15 minutes and makes changes as necessary. You can modify this interval by simply modifying the registry. This was necessary with many Windows 2000 implementations that had large topologies. In that case, the KCC may have taken longer than 15 minutes to run or monopolized the CPU. Changing the KCC to run every hour instead of 15 minutes would help ensure it would complete. With Windows Server 2003, Microsoft made significant improvements to the scalability of the KCC and I recommend running the KCC at the default interval.
There is another related registry setting you should also be aware of. By default, the KCC waits 5 minutes after Active Directory starts up before it runs. You can change this delay by creating a REG_DWORD value called Repl topology update delay (secs) under the HKLM\System\CurrentControlSet\Services\NTDS\Parameters\ key. The data for the value should be the number of seconds to wait after startup before the KCC starts. The default is 300, which is 5 minutes.
11.30.4 See Also
MS KB 271988 (Replication Topology Updates)