PulseTimeout2
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
| Data type | Range | Default value |
|---|---|---|
REG_DWORD |
60–3,600 (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, then the PDC regards the BDC as unresponsive and can send a pulse to another BDC in the domain.
This entry applies only to PDCs, and it is used only if a BDC cannot retrieve all the changes to the Security Accounts Manager (SAM) or Local Security Authority (LSA) databases in a single remote procedure call (RPC).
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 this entry, then the BDC is considered to be unresponsive. An unresponsive BDC is not counted against the limit specified by the PulseConcurrency entry, allowing the PDC to send a pulse to another BDC in the domain.
If the value of this entry is set too high, then a slow BDC, or one whose replication rate is too slow, consumes one of the PulseConcurrency slots. But if the value of this entry is too low, then the PDC's workload increases because of the large number of BDCs doing a partial replication.
This entry does not exist in the registry by default. You can add it by using the registry editor Regedit.exe.
Note
- In Windows Server 2003, the Net Logon service manages replication only if the replication involves servers running Windows NT 4.0 or earlier. Net Logon for Windows Server 2003 does not manage replication between two servers running Windows Server 2003.