A client cannot automatically join a domain that contains RODCs when a Windows Server 2008-based WDS server is used

Consider the following scenario:

• You use a Windows Deployment Services server that is running Windows Server 2008 to deploy operating system images in a domain. This domain contains both read/write domain controllers and read-only domain controllers (RODCs).
• You deploy an operating system, and you try to use an answer file to join a Windows Deployment Services client to the domain automatically.

In this scenario, the Windows Deployment Services client cannot join the domain. Additionally, the Mini-Setup Wizard prompts you to enter a correct domain name and the credentials of a user account.

This issue occurs because the Windows Deployment Services client incorrectly contacts a read-only domain controller to join the domain. However, the Windows Deployment Services client is expected to contact a read/write domain controller to perform the operation.

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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 Service Pack 2 (SP2) on the computer. Additionally, the computer must have the Windows Deployment Services role installed.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Installation instructions

To install this hotfix, follow these steps:

1. The hotfix that is mentioned in this article contains a .cab package. Extract the Wdsclient.dll file from the .cab package to a temporary folder. To do this, double-click the .cab package.
2. Install Windows Automated Installation Kit (Windows AIK) or Windows OEM Preinstall Kit (Windows OPK).
3. Disable the boot image on the Windows Deployment Services server to make the boot image unavailable for downloading. For example, you can run the following command at a command prompt:
   wdsutil.exe /set-image /image:<ImageName> /imagetype:boot /architecture:<Platform> /enabled:no
   Note The <ImageName> placeholder represents the name of the boot image. Replace the <Platform> placeholder with x86, with x64, or with ia64, as appropriate for your situation.
4. Export the boot image from the Windows Deployment Services server. For example, you can run the following command at the command prompt:
   wdsutil.exe /export-image /image:<ImageName> /imagetype:boot /architecture:<Platform> /destinationimage /filepath:<PathToBootWIM>
   Note The <PathToBootWIM> placeholder represents the path of the Windows Imaging Format (WIM) file to which you want to export the boot image.
5. Mount the boot image that you exported in step 4. When you do this, specify an index of 2, and specify read access and write access. For example, you can run the following command at the command prompt:
   imagex.exe /mountrw <PathToBootWIM> 2 <MountLocation>
   Note The <MountLocation> placeholder represents the location where you want to mount the boot image. For more information about this operation, see the documentation that is provided in the Windows OPK.
6. Locate the Wdsclient.dll file that you extracted in step 1. Copy the Wdsclient.dll file to the Sources folder in the mount location that you specified in step 5, and replace the existing file.
7. Unmount the WIM file that you specified in step 5 by committing all changes. For example, you can run the following command at the command prompt:
   imagex.exe /commit /unmount <MountLocation>
8. Add the WIM file back to the WDS server. For example, you can run the following command at the command prompt:
   wdsutil.exe /replace-image /image:<ImageName> /imagetype:boot /architecture:<Platform> /replacementimage /imagefile:<PathToBootWIM>
9. Delete all temporary folders.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You do not have to 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 file information notes

• 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" section. MUM files 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 Server 2008

For all supported x64-based versions of Windows Server 2008

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

For more information about Windows Deployment Services, visit the following Microsoft Web sites: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: