Cached passwords for computer accounts are reset when you remove an RODC that is running Windows Server 2008 from Active Directory after you clear the check box that resets cached passwords for computer accounts

Consider the following scenario:

• Some user account passwords and computer account passwords are cached on a read-only domain controller (RODC) that is running Windows Server 2008.
• In the "Active Directory Users and Computers" snap-in window of Microsoft Management Console (MMC), you delete the RODC from the Active Directory directory service. After you click a command button to confirm the deletion of the RODC, you perform the following actions:
  • You click to select the Reset all passwords for user accounts that were cached on this Read-only Domain Controller check box.
  • You click to clear the Reset all passwords for computer accounts that were cached on this Read-only Domain Controller check box.
  • You click to clear the Export the list of accounts that were cached on this Read-only Domain Controller to this file check box.

In this scenario, you have cleared the Reset all passwords for computer accounts that were cached on this Read-only Domain Controller check box. However, all cached passwords for computer accounts are reset after the RODC is removed. Therefore, users cannot log on to the domain from the computers that have reset passwords. Additionally, these computers must rejoin the domain before they can log on to the domain.

This problem occurs because the RODC Delete Wizard cannot differentiate between the user accounts and the computer accounts. Therefore, the RODC Delete Wizard cannot determine which accounts should not be reset.

To fix this problem, install the following hotfix on computers that are running Windows Server 2008 or Windows Vista and that have the "Active Directory Users and Computers" MMC snap-in installed.

Hotfix information

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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, your computer must be running one of the following operating systems:

• Windows Server 2008
• Windows Server 2008 Service Pack 2 (SP2)
• Windows Vista
• Windows Vista Service Pack 2 (SP2)

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x86-based versions of Windows Server 2008 and of Windows Vista SP2

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista SP2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, visit the following Microsoft Web sites: For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista