Skip to main content

Troubleshooting account lockout.

It's been a couple of days searching for answers on how to resolve "frequent account lockout in Active Directory (AD)". If you missed the my previous posts, here's the links:
1st post -
2nd post -

Today I will try this post on how to Troubleshoot Account Lockout courtesy by Microsoft Technet.

I started my Active Directory Users and Computer, right click on my AD domain (for ex., then Properties. Click the Group Policy tab, select the Default Domain Policy, click Properties.

In Group Policy Object Editor, collapse Windows Settings, Security Settings, Account Policies, then click on Account Lockout, and change Account Lockout threshold from 3 to 50. You need to come back here and change it to 3 after your troubleshooting.

Save the policy.

In AD server command prompt, run "net accounts" to see if the changes you made is saved.

I applied the net user /persistent:no. Here's the explanation why not to use persistent.
" Persistent drives may have been established with credentials that subsequently expired. If the user types explicit credentials when they try to connect to a share, the credential is not persistent unless it is explicitly saved by Stored User Names and Passwords. Every time that the user logs off the network, logs on to the network, or restarts the computer, the authentication attempt fails when Windows attempts to restore the connection because there are no stored credentials. To avoid this behavior, configure net use so that is does not make persistent connections. To do this, at a command prompt, type net use /persistent:no. Alternately, to ensure current credentials are used for persistent drives, disconnect and reconnect the persistent drive." (2011, Microsoft Technet)

I use the LockoutStatus.exe tool to monitor the "account", on how it quickly lockout the user. I've noticed right away the Bad Pwd Count is 4.

After few hours ... the Bad Pwd Count is still at 4.

I updated the Account Lockout threshold from 50 to 10, since the lockout status only reported 4 max for the last two hours. Check using "net accounts" to see if the changes you made is applied. Some network, AD updates takes a while between 5 to 15 minutes.

After few hours ... the Bad Pwd Count is still at 4. If my test account will not lockout with the setting of Account Lockout threshold of 10 for the next 24 hours. I will consider this issue resolve. Thanks God, it's time to celebrate.


Popular posts from this blog

Alternative Social Networks

If you are planning to create your social network e.g. similar to Facebook. Here's a short list of alternative software's:

Open Source and Free​ - Wordpress (Open Source and Free) - (Open Source and Free)Commercial Social Networks software ($299 Stand Alone, $29/mo Cloud) (run with Joomla, need to know CMS) (very expensive, $399 for Standard) (from free to Commercial, I left my networks and they are selling it (I used this before, it's hard to maintain. I moved to NING but left too after it was sold to another company) (I don't recommend using this service, it's hard to export your data when it's time to move)Something to check when selecting your next soc…

Example of Out of Office Reply for Terminated Employee

This is a sample message that I used for terminated employees, unless HR staff specified a different message.
=== Example for KING.NET Employee === John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2008 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at
Please call our main office 703-345-6789 if you have other concerns.
Thank you.
=== end of message ===

Frequent Account Lockout in Active Directory

I have a user in Windows Pro 7, and Windows Server 2003 environment that is frequently account locked out. I tried many different scenarios to resolve this account lockout issue, from resetting his password, changing a new password, remove and re-join the domain, rebooting the workstation and active directory servers.

I tried to use the command prompt utility to run "rundll32.exe keymgrdll, KRShowKeyMgr" (case sensitive) to delete the account in Windows 7 password cache, and still no luck.

Still searching for answer ... Let me know if you encounter a similar issue in Windows Pro 7 and Windows Server 2003.

Continue reading updated post here: