The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe. SUMMARYThere may be situations where you want to determine why backup domain controllers (BDCs) request full synchronizations. MORE INFORMATIONFull synchronizations can be caused by several things:
To log enough information to determine if the change log was wrapped, set the following parameter in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\ParametersThe following lines show that a full synchronization was caused by wrapping the change log: The first line represents a particular BDC requesting all new changes. In this example, the BDC had changes up to 0 7c7d, or the first 31,869 changes to the Security Accounts Manager (SAM). The second line shows that the requested delta is no longer in the change log. The primary domain controller (PDC) ignores the partial request and tells that BDC to request a full synchronization. You can change the size of the change log from 64 KB to 4.19 MB. Each change averages 32 bytes, so the change log can store approximately 2,000-130,000 changes. To change the size of the change log:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters Value Name: ChangeLogSize Additional query words: synchronization 5713
Keywords : |
Last Reviewed: November 11, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |