PulseTimeout2

HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

Data type Range Default value
REG_DWORD 60 - 3600 seconds 300 (5 minutes)

Description

Defines how long a primary domain controller (PDC) waits for a backup domain controller (BDC) to complete each step in the replication process. If the value of this entry is exceeded, the PDC regards the BDC as unresponsive and can send a pulse to another BDC in the domain.

PulseTimeout2 applies only to PDCs and is only used when a BDC cannot retrieve all the changes to the SAM/LSA database in a single RPC call.

To be considered responsive, the BDC must respond to a pulse and must continue reporting its progress on the replication. If the interval between progress reports exceeds the value of PulseTimeout2, the BDC is considered to be unresponsive. An unresponsive BDC is not counted against the limit specified by PulseConcurrency, allowing the PDC to send a pulse to another BDC in the domain.

If the value of this entry is set too high, a slow BDC, or one whose replication rate is too slow, consumes one of the PulseConcurrency slots. If the value of this entry is too low, the PDC's workload increases because of the large number of BDCs doing a partial replication.

Note Image Note

For Windows 2000, Net Logon manages replication only when it involves servers running Windows NT 4.0 or earlier. Net Logon for Windows 2000 does not manage replication between two servers running Windows 2000.

Windows 2000 does not add this entry to the registry. You can add it by editing the registry or by using a program that edits the registry.

Related Entries

Page Image

Page Image

Page Image

Page Image

Page Image