Consider the following scenario in an Active Directory domain environment:
Remote Server Administration Tools (RSAT) is installed on a client computer that is running Windows 7 or Windows Server 2008 R2.
A user account is delegated to be able to unlock user accounts in the domain.For more information about how to delegate the Unlock Account right, click the following article number to view the article in the Microsoft Knowledge Base:
You use the user account to log on the domain from the client computer or a Windows Server 2008 R2-based domain controller.
You try to unlock a user account by performing one of the following methods:
Use Active Directory Administrative Center (ADAC).
Use the Unlock-ADAccount cmdlet at a Windows PowerShell prompt.
In this scenario, the account-unlocking operation fails. Additionally, you receive the following error message:
Failed to unlock user account. Insufficient access rights to perform the operation.
Note This issue does not occur when you use the Active Directory Users and Computers (ADUC) Microsoft Management Console (MMC) snap-in to unlock a user account.
This issue occurs because the user account does not have the write access to the UserAccountControl attribute. In ADAC and the Unlock-ADAccount cmdlet, a different method to unlock a user account is implemented. This method requires write access to the UserAccountControl attribute. Therefore, this issue occurs if the user account does not have the necessary write access.
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 Web site:
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.
To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1). Additionally, you must install RSAT on the client computer.
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
To use the hotfix in this package, you do not have to make any changes to the registry.
You do not have to restart the computer after you apply this hotfix. To avoid restarting, close all related ADAC windows or PowerShell prompts.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 7 and Windows Server 2008 R2 file information notes
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:
Windows 7 and Windows Server 2008 R2
GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and 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 x86-based versions of Windows 7
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
To work around this issue, perform one of the following methods:
Use the ADUC MMC snap-in.
Grant the "Read account restrictions" and "Write account restrictions" permissions to the user account. Important Granting the "Read account restrictions" and "Write account restrictions" permissions to the user account will enable the user account to perform account configurations that may affect the security of the account and of the domain.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about ADAC, visit the following Microsoft website:
Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Foundation, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate