AD Account Keeps Getting Locked Out?

There are multiple tools that help determine account lockout source, but most are labor- and time-intensive. If you're looking for how to find what is locking out AD accounts, here are a few options:

1. Microsoft account lockout and management tools

Microsoft offers the LockoutStatus and EventCombMT tools. Though reliable and accurate, using Microsoft’s tools requires multiple individual components to be set up, along with routine manual investigation of every Windows component to figure out how to find what is locking out an AD account in each specific case.

2. PowerShell scripts

The Active Directory PowerShell module allows admins to query and make changes to AD. To search for locked-out accounts, admins can run the following command in the module: Search-AdAccount -LockedOut

However, in addition to admins being aware of the scripting language, using PowerShell scripts requires manual setup of AD security auditing. It includes finding the domain controller that has the primary domain controller emulator role, tracking down Windows Event ID 4740 in security event logs, and analyzing the details of the event found.

3. Account lockout examiners

A third-party solution like ADAudit Plus, that can analyze various Windows components like scheduled tasks, COM objects, OWA, applications, and ActiveSync for signs of outdated credentials and improper mapping goes a long way in determining account lockout source quickly. Resolve AD accounts locking out faster with ADAudit Plus, start your free trial now.

Although it is not possible to prevent all lockouts, implementing these three best practices will help reduce how frequently user accounts get locked out.

1. Enable the “Account lockout duration” policy

The account lockout duration depends on organization-specific information such as the user count or industry type. Setting the duration to zero will keep the account secure by locking the account until an admin unlocks it. However, this also results in excessive requests to the help desk.

The recommended duration is between 30 and 60 minutes

2. Leverage the “Account lockout threshold” policy

If the account lockout threshold is set too low, user accounts will get locked out frequently. This could also make the account vulnerable to denial-of-service attacks since it's easier for the attacker to intentionally enter the wrong passwords to lock the account. On the other hand, if the threshold is set too high, the probability of a successful brute-force attack increases, as the attacker has more opportunities to try and guess the credentials.

The recommended threshold is 15 to 50

3. Configure the “Reset account lockout counter after” policy

While calculating the “reset account lockout counter after” value, organizations need to keep in mind the type and level of security threats they face and balance it with the cost of help desk calls. This value should be less than or equal to the account lockout duration.

The recommended setting is anything less than 30 minutes.