The referenced account is currently locked out and may not be logged on to

Case



When trying to login to a Windows account, either a local or domain Windows Server account, you incorrectly provide the password multiple times and eventually the account gets locked. You receive the following message.



The referenced account is currently locked out and may not be logged on to.



This article provides an easy way to unlock the user account and thus allow you to login without issues.



Solution



Navigate to the Active Directory server or any management server which has the Remote Server Administration Tools (RSAT) installed and the Powershell Active Directory module imported. If the Powershell Active Directory module is not imported, import it by running the below command.



import-module ActiveDirectory

Run the following command in an elevated Powershell terminal.



Get-AdUser -properties sAMAccountName,Enabled,LockedOut



If the user is locked out you should see the relevant property set to True. Now execute the following command.



Unlock-ADAccount





Your user "lockedout" property should now be unlocked and ready to be used for logon.



An alternative method would be to make use of the Active Directory Users and Computers MMC snapin (dsa.msc) or the Windows Admin Center interface to issue a command to unlock the Active Directory user account object. This can also be done when resetting a user's account password from the DSA.MSC console.


https://stefanos.cloud/kb/the-referenced-account-is-currently-locked-out-and-may-not-be-logged-on-to/

Comments

Post a Comment

Popular posts from this blog

How to resolve Group Policy error codes 8007071a and 800706ba

Image
Case You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below. After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba. This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations. Solution Option 1 Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules : The full configuration is shown below. After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the dom...
Read more

How to resolve Exchange Online 550 5.1.11 error

Image
Case You receive a Non Delivery Report in Exchange Online similar to the following, after sending an email message. Your message to IMCEAEX -_o=_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=d478a21369b24b7dbbcd0eaab8ff6e36-d+2E@.PROD.OUTLOOK.COM couldn't be delivered. Your email program is using outdated address information for this recipient. Reported error: 550 5.1.11 RESOLVER.ADR.ExRecipNotFound; Recipient not found by Exchange Legacy encapsulated email address lookup. Solution To prevent the Outlook client from using outdated address information, you will need to clear the recipient Auto-Complete List in Outlook or Outlook on the web by carrying out the following steps to clear the recipient Auto-Complete List from the Outlook email client. - Identify the recipient who did not receive your email message by looking at the To or CC information located in the Original Message Headers section. Recipients whose names are followed by a set of charact...
Read more

How to perform hardware health checks in Windows

Image
Case You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows. Solution Carry out the steps below. - Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine. - Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console. - Check the health of all your disks , either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-ch...
Read more