A domain account keeps locking out: how can you find the computer, mobile device, service, or task using an old password?
Repeated lockouts usually come from an endpoint, service, scheduled task, mapped drive, or mobile device that continues to submit stale credentials.

Establish a factual baseline with “lockout events on the PDC” and “Caller Computer in event 4740”, then move to “service and scheduled-task credentials”. Use identity, name resolution, replication and policy as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking lockout events on the PDC, Caller Computer in event 4740 and service and scheduled-task credentials independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · lockout events on the PDC | Checking lockout events on the PDC helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of lockout events on the PDC. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 02 · Caller Computer in event 4740 | Checking Caller Computer in event 4740 helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of Caller Computer in event 4740. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 03 · service and scheduled-task credentials | Checking service and scheduled-task credentials helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of service and scheduled-task credentials. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 04 · mapped drives and Credential Manager | Checking mapped drives and Credential Manager helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of mapped drives and Credential Manager. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 05 · stale passwords on phones, mail clients and Wi-Fi | Checking stale passwords on phones, mail clients and Wi-Fi helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of stale passwords on phones, mail clients and Wi-Fi. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 06 · multi-DC time alignment and log correlation | Checking multi-DC time alignment and log correlation helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of multi-DC time alignment and log correlation. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
Get-WinEvent -FilterHashtable @{LogName="Security";Id=4740} -MaxEvents 20Investigation and change sequence
- Capture a baseline for lockout events on the PDC and Caller Computer in event 4740 and compare it with a known-good system.
- Correlate evidence from service and scheduled-task credentials and mapped drives and Credential Manager to distinguish the direct fault from dependent symptoms.
- Only if evidence points to stale passwords on phones, mail clients and Wi-Fi, plan a controlled change with backups, a change window and rollback triggers.
- Finally check multi-DC time alignment and log correlation and the real business workflow. Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
Validation and rollback evidence
- Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
- Recheck stale passwords on phones, mail clients and Wi-Fi and multi-DC time alignment and log correlation against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming lockout events on the PDC is sufficient while overlooking Caller Computer in event 4740 and dependent checks.
- Changing several settings before preserving the original evidence for service and scheduled-task credentials.
- Do not replace root-cause analysis with destructive directory operations or forced rebuilds.
Common questions and acceptance criteria
What should be checked first?
Begin with lockout events on the PDC and Caller Computer in event 4740. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
