You install the Active Directory Lightweight Directory Services (AD LDS) role on a computer that is running Windows Server 2008 R2.
You enable an account lockout policy on an AD LDS instance.
The policy is triggered when the BadPasswordCount value exceeds the specified threshold. Therefore, the AD LDS user is locked out.
You enter a password to perform an LDAP bind to the locked-out account.
In this scenario, one of the following situations occurs:
If you enter a correct password, you receive an "Account locked out" error.
If you enter an incorrect password, you receive an "Unknown username or bad password" error.
Scenario 2
You install the Active Directory Lightweight Directory Services (AD LDS) role on a computer that is running Windows Server 2008 R2.
You enable an account lockout policy on an AD LDS instance.
You enter a password to perform an LDAP bind to a user account that has an expired password.
In this scenario, one of the following situations occurs:
If you enter an incorrect password, you receive an "Unknown username or bad password" error.
If you enter a correct password, you receive an ERROR_PASSWORD_EXPIRED error. If the User must change password at next logon option is enabled, an ERROR_PASSWORD_MUST_CHANGE error is received instead.
Additionally, the BadPasswordCount property does not increase in “Scenario 2”. Therefore, there is no retry limit.
Important This hotfix has been re-released to address an issue in which the digital signature on files produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory 2749655
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).
For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To use the hotfix, you do not have to change the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.760
0.17xxx
Windows Server 2008 R2
RTM
GDR
6.1.760
0.21xxx
Windows Server 2008 R2
RTM
LDR
6.1.760
1.17xxx
Windows Server 2008 R2
SP1
GDR
6.1.760
1.22xxx
Windows Server 2008 R2
SP1
LDR
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Ntdsa.mof
Not Applicable
227,765
22-Jul-2009
23:08
Not Applicable
Ntdsai.dll
6.1.7600.17053
2,720,768
29-Jun-2012
06:56
x64
Ntdsa.mof
Not Applicable
227,765
10-Jun-2009
20:34
Not Applicable
Ntdsai.dll
6.1.7600.21247
2,726,912
29-Jun-2012
07:01
x64
Ntdsa.mof
Not Applicable
227,765
05-Nov-2010
01:54
Not Applicable
Ntdsai.dll
6.1.7601.17876
2,722,304
29-Jun-2012
06:50
x64
Ntdsa.mof
Not Applicable
227,765
05-Nov-2010
01:54
Not Applicable
Ntdsai.dll
6.1.7601.22034
2,727,424
29-Jun-2012
06:49
x64
Samsrv.dll
6.1.7600.17053
757,760
29-Jun-2012
06:57
x64
Samsrv.mof
Not Applicable
62,541
10-Jun-2009
20:35
Not Applicable
Samsrv.dll
6.1.7600.21247
770,560
29-Jun-2012
07:02
x64
Samsrv.mof
Not Applicable
62,541
10-Jun-2009
20:35
Not Applicable
Samsrv.dll
6.1.7601.17876
758,784
29-Jun-2012
06:50
x64
Samsrv.mof
Not Applicable
62,541
10-Jun-2009
20:35
Not Applicable
Samsrv.dll
6.1.7601.22034
770,560
29-Jun-2012
06:50
x64
Samsrv.mof
Not Applicable
62,541
10-Jun-2009
20:35
Not Applicable
Samlib.dll
6.1.7600.17053
60,928
29-Jun-2012
06:08
x86
Samsrv.mof
Not Applicable
62,541
22-Jul-2009
22:47
Not Applicable
Samlib.dll
6.1.7600.21247
60,928
29-Jun-2012
06:00
x86
Samsrv.mof
Not Applicable
62,541
22-Jul-2009
23:04
Not Applicable
Samlib.dll
6.1.7601.17876
60,928
29-Jun-2012
05:52
x86
Samsrv.mof
Not Applicable
62,541
12-Nov-2010
23:04
Not Applicable
Samlib.dll
6.1.7601.22034
60,928
29-Jun-2012
05:50
x86
Samsrv.mof
Not Applicable
62,541
12-Nov-2010
23:39
Not Applicable
For all supported IA-64-based versions of Windows Server 2008 R2