An ACPI APIC UP HAL operating system image cannot be deployed if a Windows 7 boot image or a Windows Server 2008 R2 boot image is used in the deployment process

Symptoms

Consider the following scenario:

You install the Windows Deployment Services (WDS) server role on a computer that is running Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003.
In the local area network (LAN), you use a Windows 7 boot image or a Windows Server 2008 R2 boot image to deploy one or more operating system images in Windows Deployment Services.
You try to deploy an image that is based on an ACPI Uniprocessor (ACPI APIC UP) Hardware Abstraction Layer (HAL) to a client that uses an ACPI APIC UP HAL or an ACPI Multiprocessor (ACPI APIC MP) HAL.

In this scenario, the image is not displayed in the menu for the available operating system images during the deployment process. Therefore, you cannot deploy the image to the client.Note This problem also occurs in Windows Vista boot images and in Windows Server 2008 boot images. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

935772 An ACPI APIC UP HAL operating system image cannot be deployed if a Windows Vista boot image or a Windows Server 2008 boot image is used in the deployment process

Cause

The issue occurs because the Wdsclient.dll module incorrectly excludes images that are based on an ACPI APIC UP HAL when the Wdsclient.dll module displays the menu of the available operating system images.

Resolution

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:

http://support.microsoft.com/contactus/?ws=supportNote 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 one of the following operating systems:

Windows Server 2003 Service Pack 2 (SP2)
Windows Server 2008
Windows Server 2008 Service Pack 2 (SP2)
Windows Server 2008 R2
Windows 7
Windows Vista Service Pack 1 (SP1)

Note These are the operating systems on which you can install the Windows Automated Installation Kit (Windows AIK) for Windows 7. You use Windows AIK for Windows 7 to apply the hotfix to the Windows 7 boot image or to the Windows Server 2008 R2 boot image.

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 7 and 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.

For the x86-based Windows 7 boot image

File name	File version	File size	Date	Time	Platform
Wdsclient.dll	6.1.7600.20650	532,480	21-Feb-2010	15:55	x86

For the x64-based Windows 7 boot image and for the x64-based Windows Server 2008 R2 boot image

File name	File version	File size	Date	Time	Platform
Wdsclient.dll	6.1.7600.20650	624,128	21-Feb-2010	16:09	x64

For the IA-64-based Windows Server 2008 R2 boot image

File name	File version	File size	Date	Time	Platform
Wdsclient.dll	6.1.7600.20650	1,351,680	21-Feb-2010	15:03	IA-64

Status

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

More Information

You must apply this hotfix to the second image of the Windows 7 or Windows Server 2008 R2 boot image file. To do this, follow these steps.Note The second image is the Windows Preinstallation Environment (Windows PE) image.

On the Windows Deployment Services server, install the Windows Automated Installation Kit (AIK) for Windows 7.To obtain the Windows AIK for Windows 7, visit the following Microsoft website:http://www.microsoft.com/download/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=enNote You can also install Windows AIK for Windows 7 on a separate computer that is running an operating system that is supported by Windows AIK for Windows 7.
Click Start , click All Programs, click Microsoft Windows AIK, right-click the Deployment Tools Command Prompt, and then select Run as administrator.If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.
Extract the Windows6.1-KB980711-Platform.cab file from the hotfix package to a temporary folder. To do this, follow these steps:
1. Click Start , click Run, type cmd, and then click OK.
2. At the command prompt, type the following command, and then press ENTER:
  
  Expand.exe CabFilePath -R -F:* TempFolderPathNotes
  - The CabFilePath placeholder represents the path of the CAB file.
  - The TempFolderPath placeholder represents the path of the temporary folder.
Disable the problematic boot image to make it unavailable for download in the update process. To do this, open the Windows Deployment Services Microsoft Management Console (MMC) snap-in, right-click the boot image that you want to update, and then select Disable.
Export the problematic boot image from the Windows Deployment Services server to BootWimPath. To do this, right-click the boot image, and then select Export Image. Export the boot image to BootWimPath.Notes
- The BootWimPath placeholder represents the local directory where the Boot.wim file is exported.
- If you install the Windows AIK on a separate computer, you must copy the Boot.wim file to a directory on that computer. Then, perform step 6 through step 8 on that computer.
Mount the boot image for read access and for write access. To do this, type the following command at the command prompt, and then press ENTER:

dism /mount-wim /wimfile:BootWimPath /index:2 /mountdir:MountLocationNote
- The MountLocation placeholder represents the location to mount the image.
- Make sure that you mount the image whose boot index number is 2.
Copy the Wdsclient.dll file from the TempFolderPath folder to the following folders:
- MountLocation\Windows\Winsxs\Platform_microsoft-windows-imagebasedsetup-media_ID
- MountLocation\sources
Note An example value for the ID placeholder is 31bf3856ad364e35_6.1.7600.16385_none_6fe42cf3e82ff497
Unmount the Boot.wim file, and then commit all changes. To do this, type the following command at the command prompt, and then press ENTER:

Dism.exe /unmount-wim /mountdir:MountLocation /commit
Add the updated Boot.wim file back to the Windows Deployment Services server. To do this, open the Windows Deployment Services MMC snap-in, right-click Boot Images, select Add Boot Image, and then specify the path to the updated Boot.wim file
In the Windows Deployment Services MMC snap-in, right-click the boot image that you added to make sure that it is enabled.Note You have to disable or delete the problematic boot image.

For more information about Windows Deployment Services, visit the following Microsoft Tech websites:

General information about Windows Deployment Services

General information about Windows Deployment Services for Windows Server 2008 R2For more information, click the following article number to view the article in the Microsoft Knowledge Base:

935772 After you upgrade to WDS, an ACPI Multiprocessor image does not appear in the menu of operating system images when you start a PXE client that uses an ACPI Uniprocessor computer HAL For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates