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.

1. Conclusion and scope

Prepare the client and server versions, domain membership, DNS and gateway settings, network location, full error text, event timestamps, and recent changes. The reserved example domain corp.example is used throughout; no customer domain, IP address, account, or device identifier is included.

This issue falls under Active Directory and Group Policy. Logs and configuration can often be collected remotely first. Bulk permission changes, switch-path work, production cutovers, and recovery drills should use a controlled implementation window.

2. Symptoms and environment

• Capture the complete error text, event-log timestamp, and failed action rather than relying on a verbal description.
• Record the affected scope, first occurrence, reproducibility, and whether the result changes on another subnet.
• Domain members and computers being joined must use internal DNS; public resolvers do not provide the AD SRV records required for discovery.

3. Troubleshooting sequence

1. Review Security event 4740 on a domain controller to identify the locked account, caller computer, and exact time instead of stopping after a manual unlock.
2. Check old mobile mail profiles, saved Remote Desktop credentials, mapped drives, scheduled tasks, Windows services, and scripts for an outdated password.
3. When a service account is locked, identify every Windows service, IIS application pool, SQL Agent job, backup task, and third-party application that uses it before rotating the password.
4. If lockouts continue after a password change, investigate offline laptops, mobile devices, old VPN clients, and endpoints that have not restarted or signed out for a long time.
5. Remove incorrect cached credentials and stale SMB sessions, then confirm that the client is using the intended domain or local account.
6. Change one variable at a time and export the current configuration before making changes.

Get-WinEvent -FilterHashtable @{LogName="Security";Id=4740} -MaxEvents 20 | Format-List TimeCreated,Message
cmdkey /list

4. Safe remediation and rollout

Start with read-only queries, configuration exports, and one-system validation. Once the root cause is confirmed, define the target scope, change window, and rollback method. For multiple computers, use a test OU and a small pilot group, export policy results, and roll out in stages only after side effects are excluded.

• If lockouts continue after a password change, investigate offline laptops, mobile devices, old VPN clients, and endpoints that have not restarted or signed out for a long time.
• Remove incorrect cached credentials and stale SMB sessions, then confirm that the client is using the intended domain or local account.
• Change one variable at a time and export the current configuration before making changes.

5. Validation, rollback and common mistakes

Do not stop when the service works once. Revalidate with the user workflow, logs, a restart or fresh sign-in, another network location where relevant, and the next policy or backup cycle.

Validation and rollback checks

• Change one variable at a time and export the current configuration before making changes.
• Verify consistent time zones and time sources across clients, domain controllers, and hypervisors to prevent Kerberos failures.
• Confirm AD and SYSVOL replication between domain controllers and verify that the contacted controller has the expected policy version.

Common mistakes to avoid

• Using public DNS or permanent hosts-file entries for domain controllers.
• Removing a computer from the domain before confirming local administrator access.
• Linking a new GPO to the entire domain without a pilot group.