Microsoft KB Archive/250873
Article ID: 250873
Article Last Modified on 2/28/2007
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Server
This article was previously published under Q250873
When you are using a program to read and reset the user account lockout bit, your program may never report a user as locked out. The code you are using may look like the following sample script (written in the Visual Basic Scripting Edition).
Set oUser = GetObject("LDAP://cn=locked out user,cn=Users,DC=domain,DC=com") if oUser.IsAccountLocked then WScript.Echo "User is locked out" else WScript.Echo "User is not locked out" end if
The userAccountControl property also does not reflect the locked-out status.
The IsAccountLocked property is not accessible by using the Lightweight Directory Access Protocol (LDAP) provider. The lockout flag is not stored in Active Directory, but is created on-the-fly only when you access Active Directory by using the WinNT provider.
To read or reset the lockout bit, use the WinNT provider to gain access to Active Directory. The following sample VBScript demonstrates this method.
Set oUser = GetObject("WinNT://domainname/username") if oUser.IsAccountLocked then WScript.Echo "User is locked out" else WScript.Echo "User is not locked out" end if
The userFlags property has the UF_LOCKOUT bit set as well.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
User lockout uses the user's lockoutTime property. When you access Active Directory by using the LDAP provider, you can use it to determine the lockout status of the user. If it is larger than zero, the user is currently locked out. To undo the lockout, set the value to zero.
LockoutTime is cleared only when the locked-out user attempts to log on. When the lockout time has expired, but the user has not yet tried to log on, lockoutTime may be still set, although the user would be able to successfully log on at that time.
Keywords: kbprb KB250873