Security & identity

Find the Source of AD Account Lockouts with ManageEngine ADAudit Plus

Trace which device, service, scheduled task or mapped drive keeps locking an Active Directory account: event 4740 first, then the ADAudit Plus Account Lockout Analyzer, plus fixes.

By EpiFive Editorial TeamReviewed/updated 11 min readHow we check our guides
On this page

To find what keeps locking an Active Directory account, read event ID 4740 on the domain controller to get the Caller Computer Name, then check that machine for the service, scheduled task, mapped drive or app still using the old password. ManageEngine ADAudit Plus automates the second half with its Account Lockout Analyzer, which lists possible causes per lockout. This guide covers both routes and how to fix the cause, using the vendors' own documentation as of 2026-11-20.

Who this is for and what you will have at the end

This is for help desk leads and Windows administrators who keep unlocking the same user and want the lockouts to stop. At the end you will know how to confirm auditing is on, how to read a lockout event, where to find the analyzer in ADAudit Plus, what its output means, and how to clear the usual causes. It also explains the cases where the native event misleads you, so you do not chase the wrong machine.

The guide assumes an on-premises Active Directory domain with an account lockout policy already set. It does not cover Entra ID Smart Lockout, which is a separate cloud mechanism.

How an AD lockout happens

A lockout is not a single failure. A client or service sends a wrong password repeatedly until the count reaches the account lockout threshold in your policy, and the domain controller then locks the account. The usual culprit is not the person typing: it is a saved credential that went stale after a password change.

ManageEngine's lockout guides name the same places to look: services running under the account, scheduled tasks, mapped drives, applications that cache credentials, and the account's previous logon attempts. Phones and mail clients using Exchange ActiveSync or Outlook Web App are also on the analyzer's component list.

Two facts shape the investigation:

  • The 4740 event is written on the domain controller that processed the lockout and also on the PDC emulator. Microsoft's Premier Field Engineering blog says that if you collect events with scripts, forwarding or a SIEM, you can target the PDC emulator of the user's domain.
  • Event 4740 is documented by Microsoft as generated on domain controllers, member servers and workstations for user accounts, every time an account is locked out.

Prerequisites

Before either method works, auditing must be on.

Turn on the audit policy

ManageEngine's manual guide enables auditing through a Group Policy Object. In GPMC (gpmc.msc), create or edit a GPO linked to the domain controllers, then open Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Audit Policies > Account Management. Double-click Audit User Account Management and enable Success and Failure. Then run a Group Policy update on the domain or OU.

ManageEngine's troubleshooting article for the analyzer gives the same setting as its first prerequisite: Category "Account Management", Subcategory "Audit User Account Management", Audit Events "Success and Failure".

You can check the setting on a domain controller with auditpol. Microsoft's blog shows this command and the documented output:

C:\>auditpol /get /subcategory:"User Account Management"
System audit policy
Category/Subcategory                      Setting
Account Management
  User Account Management                 Success

Your own output may say "Success and Failure" if you enabled both, as ManageEngine recommends.

Privileges for ADAudit Plus

Two requirements come from ManageEngine's knowledge base:

  • The ADAudit Plus service account must be a local administrator on the product server, which the "Privileges required for ADAudit Plus auditing" article says is required for the Account Lockout Analyzer module.
  • The "No data available in Account Lockout Analyzer report" article says the service account must have Domain Admin privileges to query the top components remotely.

If you use the Exchange-related checks, the same article says IIS must be enabled on the ADAudit Plus server and IIS logging must be configured on the Exchange server that has the Client Access Server role.

Method 1: Find the source with native events

This route needs no extra software and is the right first check even if you own ADAudit Plus.

Step 1: Read event 4740 on the domain controller

  1. Open Event Viewer on the domain controller (or the PDC emulator).
  2. Go to Windows Logs > Security and click Filter Current Log.
  3. Enter 4740 in the field and click OK.
  4. Open the event for the locked account.

Microsoft's event reference describes the fields you need. Under Account That Was Locked Out you see the account name. Under Additional Information, Caller Computer Name is "the name of computer account from which logon attempt was received and after which target account was locked out", for example WIN81 in Microsoft's sample.

Step 2: Look at the caller machine

Sign in to the machine named in the Caller Computer Name and look for the process using the old password. ManageEngine suggests reviewing events around the lockout time and checking the account's services, applications, scheduled tasks and mapped drives. To name the process, filter the Security log on that machine for event 4625 and search for the locked-out user name. In the failed logon event, the Caller Process Name identifies the program; ManageEngine's example shows java.exe.

Event IDMeaningWhere it is logged (ManageEngine)
4740Account locked out, shows source computerDomain controllers
4625Failed logon attemptClients and servers
4771Kerberos pre-authentication failurePDC emulator
4768 / 4776Kerberos and NTLM authentication failuresDomain controllers

When Caller Computer Name is wrong or blank

Microsoft is direct about this limit: the field "is not necessarily accurate" and works on a best-effort basis. It is reliable when authentication comes from Windows machines, but with third-party devices it can be empty or contain an arbitrary value.

The most common surprise is a domain controller as the caller. Microsoft explains that when an application uses an LDAP simple bind, the LDAP server, which is also your domain controller, starts the authentication, so the Caller Computer Name shows the local DC. To find the real client:

  1. On the DC that received the authentication, look at the failed logon event 4625. Its Network Information section shows the Source Network Address of the actual LDAP client. In Microsoft's example, 10.0.0.7 is the client, not the DC.
  2. This requires auditing the Logon subcategory for failures. Microsoft's blog shows the documented setting as "Success and Failure".
  3. The event 4625 appears only on the local DC, not on the PDC emulator. The PDC emulator logs event 4776 if the Credential Validation subcategory audits failures.

Failure auditing is noisy. Microsoft's alternative is the Account Lockout subcategory under Logon/Logoff, which the blog says must be set to Failure despite what the documentation stated at the time. It produces a 4625 event with the task category Account Lockout, but only when someone tries to authenticate against an already locked account (the lockout threshold plus one attempt). That event also carries the client's real IP address and is far quieter than auditing all logon failures.

Method 2: Use the ADAudit Plus Account Lockout Analyzer

ADAudit Plus gathers the same events and then queries the suspected machines for the stored credentials that could be responsible.

Open the analyzer

In the ADAudit Plus console, go to Active Directory > User Management > Account Lockout Analyzer. ManageEngine's summary lists the same location as Reports > Active Directory > User Management > Account Lockout Analyzer; the menu layout can differ between builds, so look for the report name.

Read the report

The report is sorted by time. Each lockout row shows the lockout details, and ManageEngine's page lists these elements: the locked-out user, the domain controller and caller computer, the time of the lockout, and previous logon attempts. Click Details in the Analyzer Details column to see possible causes for that lockout, such as cached credentials used by services, scheduled tasks or other components.

ManageEngine's product page states the analyzer examines "scheduled tasks, COM objects, OWA, applications, and ActiveSync for signs of outdated credentials and improper mapping", and lists expired cached credentials for Windows services and improper shared drive mappings. Treat that as the vendor's description and confirm it against your own environment in a trial, since the page is promotional. The page does not mention Outlook specifically, so do not assume Outlook coverage.

Alerts

The same page says you can receive account lockout notifications by email and SMS, set thresholds, and run scripts such as unlocking an account automatically. A sensible rule is an alert for privileged accounts and for any burst of lockouts, which matches Microsoft's own monitoring advice for event 4740 on high-value accounts.

If the report is empty

ManageEngine's "No data available in Account Lockout Analyzer report" article lists four causes, and the fixes below follow its steps:

  1. 4740 not in the DC's Security log. Open Event Viewer on the DC, go to Windows Logs > Security and search for 4740. If it is missing, fix the Audit User Account Management policy.
  2. Audit settings misconfigured, so ADAudit Plus never collected the event. Re-apply the settings from the prerequisites section.
  3. Service account lacks Domain Admin privileges. In ADAudit Plus open Domain Settings, select the domain, click Modify Credentials and enter an account with Domain Admin rights.
  4. Exchange IIS logging not configured. On the Exchange server with the Client Access Server role, open IIS Manager, expand Server > Sites > Default Web Site, double-click Logging and set Log File Format to W3C, and configure the W3C logging fields. If your time zone is not GMT, ensure "Use the local time for file naming and rollover" is unchecked.

If the caller machine name is blank, Microsoft's caveat above applies: use the 4625 route to find the client address.

Fix the cause

Finding the source is half the work. Match what you found to the fix:

Source foundTypical fix
Windows service running as the userUpdate the password the service runs under, or stop it using the user's credentials
Scheduled taskRe-enter the credentials in the task, or run it under a dedicated service account
Mapped drive or saved Windows credentialRemove the old saved credential and reconnect the drive with the new password
Phone or tablet mail clientUpdate the password in the mail app on the device, or remove the profile
Application using LDAP simple bindUpdate the application's bind password; locate the client from the 4625 source address
Stale password on a replicated DCManageEngine's manual guide says to update the password and force replication

After the fix, unlock the account once, watch for a new 4740, and confirm the Caller Computer Name no longer appears.

Verification and checklist

  • The Audit User Account Management policy is set to Success and Failure on domain controllers.
  • Event 4740 appears in the Security log of the DC (and the PDC emulator) for a test lockout.
  • The Account Lockout Analyzer lists the lockout and the Details link shows possible causes.
  • The Caller Computer Name has been confirmed against event 4625 and the machine's own logs.
  • The stale credential is updated at the source, and no new lockout appears after the next password sync.
  • Alerts are set for privileged accounts and lockout bursts.

What we checked

  • Opened ManageEngine's "How to find the source of an account lockout" guide and the ADAudit Plus lockout how-to on 2026-11-20 and recorded the GPMC path to Audit User Account Management, the event IDs 4740 and 4625 and the Caller Process Name step.
  • Opened Microsoft's event 4740 reference on learn.microsoft.com on 2026-11-20 and confirmed that the Caller Computer Name field is described as the computer from which the logon attempt was received, and that the event is logged on domain controllers, member servers and workstations.
  • Cross-checked ManageEngine's audit-policy setting (Account Management, Audit User Account Management) against its troubleshooting article and Microsoft's auditpol output; the documented output shown above is from Microsoft's blog.
  • Compared the analyzer menu path across two ManageEngine pages: "Active Directory > User Management > Account Lockout Analyzer" and "Reports > Active Directory > User Management > Account Lockout Analyzer". Both are quoted above.
  • Opened ManageEngine's "Privileges required" and "No data available" knowledge base articles on 2026-11-20 and matched the local administrator and Domain Admin requirements.
  • Not tested on a live domain or a live ADAudit Plus install; the steps follow vendor documentation as of 2026-11-20, and edition and pricing details were left out because they were not confirmed.

Last tested: 2026-11-20

References

Questions people ask

How do I find which computer is locking out an AD account?

On a domain controller, open Event Viewer, go to Windows Logs > Security and filter for event ID 4740. The Caller Computer Name field under Additional Information names the machine from which the logon attempt was received. Microsoft notes the field is best effort, so confirm it with the failed logon events on that machine.

Where is the Account Lockout Analyzer in ADAudit Plus?

ManageEngine documents the path as Active Directory > User Management > Account Lockout Analyzer. Its summary gives the same report as Reports > Active Directory > User Management > Account Lockout Analyzer. Click Details in the Analyzer Details column of a lockout to see possible causes.

Why does event 4740 show a domain controller as the caller computer?

Microsoft explains that when an application authenticates through an LDAP simple bind, the authentication starts on the domain controller, so the Caller Computer Name shows the local DC. The actual client address can be found in the failed logon event 4625 on that DC.

Why does the Account Lockout Analyzer show no data?

ManageEngine lists the usual causes: the 4740 event was not logged on the DC, audit settings are misconfigured, the service account lacks Domain Admin privileges to query machines remotely, or IIS logging is not configured on the Exchange Client Access server. Check each in that order.

ManageEngine ADAudit PlusActive DirectoryAccount LockoutEvent ID 4740Windows Security Log