A user calls for the third time this week: "My account is locked again. I didn't do anything." The service desk unlocks it, the user signs in, and an hour later it is locked again. Unlocking is the easy part. The real ticket is finding what keeps sending the wrong password, because something almost always is: a phone with an old mail password, a mapped drive saved with old credentials, a second laptop, a disconnected RDP session, or, less often, someone actually guessing.
These are my study notes on how I'd work a repeated lockout at the service desk, written as a guide and "what I learned," with each step checked against Microsoft's documentation. I'm not claiming production experience running a domain. Entra ID smart lockout, Netlogon debug logging, and domain controller audit policy are study topics for me, and in a real environment they belong to the identity or server team.
First questions
- When did it start? A password change in the last few days is the most common trigger. The new password works on the PC, and every other device keeps trying the old one.
- How often does it lock? Every few minutes, every hour, or once a morning? A steady rhythm usually means a device or app retrying on a schedule.
- Which devices and apps use this account? Work phone, personal phone with company mail, tablet, second laptop, home PC, VPN, Wi-Fi.
- Where does it fail? On-premises sign-in (Windows logon, file shares, VPN) points to Active Directory. A message like "Your account is temporarily locked to prevent unauthorized use" on a Microsoft 365 sign-in page points to Entra ID smart lockout [3].
- Is anyone else affected? Several accounts locking at once is a security event, not a desk-side fix.
Two different lockouts
This was the first thing I had to get straight. Active Directory has its own lockout policy (threshold, duration, and reset counter), set in Group Policy under Account Policies > Account Lockout Policy [4]. Microsoft Entra ID has smart lockout for cloud sign-ins. By default it locks after 10 failed attempts in public tenants, starts with a one-minute lockout that grows on repeats, and does not count the same wrong password twice because it remembers the last three bad hashes [3]. In a hybrid setup the two can interact, so I'd always write down which sign-in actually failed before touching anything.
Check 1: Confirm the lockout and unlock once
With the RSAT Active Directory module (or Active Directory Users and Computers), I'd confirm the state first [2]:
Get-ADUser jdoe -Properties LockedOut, badPwdCount, lastBadPasswordAttempt, PasswordLastSet
Search-ADAccount -LockedOut
Search-ADAccount -LockedOut lists locked accounts [5]. PasswordLastSet tells me whether a recent password change lines up with the start of the problem. Then, after the user's identity is verified the way the team's procedure says, I'd unlock once [6]:
Unlock-ADAccount -Identity jdoe
Unlocking again and again without finding the source just restarts the clock.
Check 2: Find the source with event 4740
When an account locks, Windows logs event 4740, "A user account was locked out." The field that matters is Caller Computer Name, the computer the bad attempt came from [1]. Lockouts are processed by the domain controller holding the PDC emulator role, so that is the most useful place to look [8]. A Microsoft blog post shows collecting 4740 events for one user from the PDC emulator with Get-WinEvent [8]:
$PDC = Get-ADDomainController -Discover -Service PrimaryDC
Get-WinEvent -ComputerName $PDC -LogName Security -FilterXPath "*[System[EventID=4740] and EventData[Data[@Name='TargetUserName']='jdoe']]"
At many service desks Tier 1 does not have rights to read domain controller security logs. That's fine. The useful Tier 1 move is to ask the identity or server team for the 4740 Caller Computer Name, with the user and the exact lockout times.
Check 3: When Caller Computer Name is blank or a server
If the 4740 field is empty or names a server (Exchange, a RADIUS server for Wi-Fi or VPN, an app server), the bad password came through that system on someone else's behalf. Microsoft's Entra Domain Services lockout guide says the source workstation can be empty when the bad password arrived over a network logon through another device, such as a RADIUS server [7]. Events 4771 (Kerberos pre-authentication failed) and 4776 (NTLM credential validation) can add detail like the client address [9][10]. Netlogon debug logging is the next step, and that is a domain controller change for the server team, not something I'd do from the desk.
Check 4: The usual suspects on the user's side
Microsoft lists the common non-malicious causes plainly: the user retrying an old password after a change, an app or service still holding an old password, and a password change that hasn't synced yet [7]. On the user's side, I'd walk through:
- Phones and tablets. The mail app or Outlook mobile with the old password. Update it, or remove and re-add the account.
- Credential Manager. Saved Windows credentials for file servers, intranet sites, or RDP hosts. Microsoft's support page shows where to view and remove them [11]. I'd remove the stale entry, not every entry.
- Mapped drives saved with "Connect using different credentials."
- A second PC or an old laptop that is still on and signed in.
- A disconnected RDP session on a server, still running under the old password.
- Wi-Fi profiles on laptops or phones that authenticate with the domain password (the RADIUS case above).
- Scheduled tasks or services set to run as the user's account. This is a red flag. A service should not run as a person's account, so I'd escalate it instead of just updating the password.
Check 5: When it might not be the user
If the source is a computer nobody recognizes, the attempts come from outside the network, or several accounts lock together, I'd stop troubleshooting and escalate to security with the timestamps. Repeated failures from an unknown source can be password spraying. For Microsoft 365 sign-ins, an error like AADSTS50053 means Entra ID blocked the sign-in [3], and the sign-in logs belong to the identity team.
What I would not do
- Unlock the account in a loop without finding the source.
- Raise the lockout threshold or turn lockout off for one user. That is a security policy decision.
- Clear every saved credential on the PC "to be safe." It breaks things the user needed and hides evidence.
- Reset the password without verification, or reset it to something the user didn't choose and send it in chat.
- Assume it's the user's fault. In most of the cases I studied, the user did nothing wrong; a device did.
Ticket notes I'd write
- User, verification method, and time of each lockout the user reports
LockedOut,badPwdCount,lastBadPasswordAttempt, andPasswordLastSetvalues- Whether the failure is on-premises (Windows, share, VPN) or a Microsoft 365 sign-in page
- Devices and apps that use the account, and what was updated (phone mail, Credential Manager entry, mapped drive)
- Caller Computer Name from event 4740, if the identity team provided it
- Whether other accounts are locking, and any unknown or external source (security escalation)
What I learned
A lockout ticket is really a "who is still using the old password" ticket. The account policy is doing its job; the work is finding the device. Event 4740 and its Caller Computer Name turn a guessing game into a short list, and a blank caller is a clue in itself, pointing to Exchange, RADIUS, or another server in the middle. I also learned to keep the two systems apart: Active Directory lockout and Entra ID smart lockout have different rules, different messages, and different owners. Next time a user says "I didn't do anything," I'll believe them and go look for their phone.
Sources
- Microsoft Learn, 4740(S) A user account was locked out: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/auditing/event-4740
- Microsoft Learn, Get-ADUser: https://learn.microsoft.com/en-us/powershell/module/activedirectory/get-aduser
- Microsoft Learn, Prevent attacks using smart lockout (Microsoft Entra ID): https://learn.microsoft.com/en-us/entra/identity/authentication/howto-password-smart-lockout
- Microsoft Learn, Account Lockout Policy: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/account-lockout-policy
- Microsoft Learn, Search-ADAccount: https://learn.microsoft.com/en-us/powershell/module/activedirectory/search-adaccount
- Microsoft Learn, Unlock-ADAccount: https://learn.microsoft.com/en-us/powershell/module/activedirectory/unlock-adaccount
- Microsoft Learn, Troubleshoot account lockout in Microsoft Entra Domain Services: https://learn.microsoft.com/en-us/entra/identity/domain-services/troubleshoot-account-lockout
- Microsoft Learn (archived blog), Tracing the source of account lockouts: https://learn.microsoft.com/en-us/archive/blogs/poshchap/tracing-the-source-of-account-lockouts
- Microsoft Learn, 4771(F) Kerberos pre-authentication failed: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/auditing/event-4771
- Microsoft Learn, 4776(S, F) The computer attempted to validate the credentials for an account: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/auditing/event-4776
- Microsoft Support, Credential Manager in Windows: https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0
I'm Rıza Korkusuz, an IT support professional in San Diego. I write these notes to organize what I'm learning about desktop and service desk work. More at rizakorkusuz.com/it-support and github.com/rizakorkusuz.