Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Windows » Configure Local Administrators Account lockout

Configure Local Administrators Account lockout

Posted on 17/10/202215/06/2023 Christian By Christian No Comments on Configure Local Administrators Account lockout
acctlockout-1

Account lockout helps keep user accounts secure by preventing unauthorized users etc., from guessing the username and password. When your account is locked, you will have to wait for a specified amount of time before being able to log into your account again. Therefore, the account lockout policy “locks” the user’s account after a defined number of failed password attempts. In this article, you will learn how to configure Local Administrators Account lockout. Kindly refer to these related guides: How to Change User Account Type in Windows 10, Is my AD user account or service account password correct? How to run an App as a different User and switch Users in Windows, User account and process management in Linux, and how to find disabled Active Directory User accounts.

In the past, it was recommended to disable the local Administrator account due to several known vulnerabilities such as the built-in administrator account cannot be locked out no matter how many failed login attempts, making it a prime target for brute-force attacks that attempt to guess passwords. This is no longer true as beginning October 11, 2022, or later Windows cumulative updates, a local policy will be available to enable local administrator account lockouts. 

Please here are some related articles: How to deploy MBAM for Bitlocker Administration, How to increase Windows PIN complexity, how to fix The logon attempt failed for the remote desktop connection, how to fix “The following error occurred attempting to rename the computer Account already exists“, and how to Change Account Lockout Threshold for Local Accounts in Windows: The reference account is locked.

Why Enable Local Administrator Account Lockout?

Brute force attacks are one of the prevalent ways Windows devices are attacked today. Previously, Windows devices did not allow local administrators to be locked out. This leads to scenarios where without the proper network segmentation. Or the presence of an intrusion detection service, the local administrator account can be subjected to unlimited brute force attacks to attempt to determine the password.

This can be done using RDP over the network. If the passwords are not long or complex, the time it would take to perform such an attack is becoming trivial with modern CPUs/GPUs. Here are some related guides. What is Pass the Hash Attack and how to mitigate the attack, and Windows 11 Hardware and Software Requirements: How to upgrade to Windows 11. Also, see how to enable or disable Windows Defender Credential Guard.

Enable account lockouts for Administrator accounts

In an effort to prevent further brute force attacks/attempts. Microsoft is implementing account lockouts for Administrator accounts beginning with October 11, 2022. Or later Windows cumulative updates, a local policy will be available to enable local administrator account lockouts. This policy can be found under.

Local Computer Policy\Computer Configuration\Windows Settings\Security Settings\Account Policies\Account Lockout Policies. 
accountlockout

For existing machines, setting this value to Enabled using a local or domain GPO will enable the lockout for the Administrator accounts. Such environments should also consider setting the other three policies under Account Lockout Policies. Our baseline recommendation is to set them to 10/10/10.

This means an account would be locked out after 10 failed attempts within 10 minutes. And the lockout would last for 10 minutes, after which the account would be unlocked automatically. Kindly refer to this interesting guide: What is Pass the Hash Attack and how to mitigate the attack.

For new devices running Windows 11, v22H2, or any new device that will include October 11, 2022. Windows cumulative updates before the initial setup, these settings will be set by default at system setup. This occurs when the SAM database is first instantiated on a new machine. So, if a new machine was set up and then had the October updates installed later. It will not be secure by default and will require the policy settings above. 

If you do not want these policies to apply to your new computer. You can set the local policy above or create a group policy to apply the Disabled setting for “Allow Administrator account lockout.”

Password Complexity

Securing your environment requires that strong passwords be employed. This helps eliminate the threat of a malicious user guessing a weak password. Whether through manual methods or by using tools, to acquire the credentials of a compromised user account. This is especially true for administrative accounts. When you change a complex password regularly, it reduces the likelihood of a successful password attack.

Password policy settings control the complexity and lifetime of passwords. Password policies affect Windows passwords, not necessarily feature passwords.

Now, password complexity is now enforced on new devices having the local administrator account enabled. The password must have at least three of the four basic character types (lower case, upper case, numbers, and symbols). This will help further protect these accounts from being compromised because of a brute force attack. However, if you want to use a less complex password, you can still set the appropriate password policies in the location below.

Local Computer Policy\Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy
Passowrdcomplexity

I hope you found this blog post helpful on how to configure Local Administrators’ Account lockout. Please let me know in the comment session if you have any questions.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows, Windows Server Tags:Microsoft Windows, User Account, Windows 10, Windows Server 2016

Post navigation

Previous Post: How and where to find your BitLocker recovery key on Windows
Next Post: WHFB Hybrid Cloud Kerberos Trust Model is now available

Related Posts

  • Best Disk Partition Manager for Mac
    How to extend System Drive Partition on Windows Windows
  • DC Name
    Install and configure Active Directory Domain Services on Windows Server Windows
  • mdtxxxxx
    Failed to run the action install Operating System: Lifetouch deployment failed, Return Code = -2147467259 0x80004005 when installing Windows image via MDT Windows
  • Screenshot 2021 03 16 at 21.14.05
    Unable to locate the account: Fix call to DsGetDcNameWithAccount failed with return value 0x0000054B Windows Server
  • How to Fix 0xc000007b Error banner
    Fix 0xc000007b Error on Windows 11 While Launching a Game Windows
  • cookies9
    How to remove third-party cookies from Microsoft Edge Windows

More Related Articles

Best Disk Partition Manager for Mac How to extend System Drive Partition on Windows Windows
DC Name Install and configure Active Directory Domain Services on Windows Server Windows
mdtxxxxx Failed to run the action install Operating System: Lifetouch deployment failed, Return Code = -2147467259 0x80004005 when installing Windows image via MDT Windows
Screenshot 2021 03 16 at 21.14.05 Unable to locate the account: Fix call to DsGetDcNameWithAccount failed with return value 0x0000054B Windows Server
How to Fix 0xc000007b Error banner Fix 0xc000007b Error on Windows 11 While Launching a Game Windows
cookies9 How to remove third-party cookies from Microsoft Edge Windows

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • Screenshot 2020 07 25 at 13.09.08
    Fix the following error occurred when DNS was queried for the service location Windows Server
  • oauth2final
    How to implement Interactive Authentication using MSAL dotNET AWS/Azure/OpenShift
  • Check Virtualization
    Enable Virtualization in BIOS: Determine if the Intel VT-x or AMD-V Virtualization Technology is enabled in BIOS Virtualization
  • dfeef
    How to automatically resolve errors associated with failed dependencies Linux
  • Slide2 1
    How to deploy WordPress on Azure App Service AWS/Azure/OpenShift
  • what is saml e1690630549650
    What is SAML – Security Assertion Markup Language Windows Server
  • remote desktop connection tabs   rdp tabs
    Guide to Remote Desktop Connection Properties for Secure Access Windows
  • Hyper V VM creation
    How to Create a Windows Server VM on HyperV Windows Server

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,821 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.