Microsoft KB Archive/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 =

Article ID: 935772

Article Last Modified on 8/29/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition

-



SYMPTOMS
You upgrade a Remote Installation Service (RIS) server to use Windows Deployment Services (WDS). However, images that are based on an ACPI Uniprocessor (ACPI APIC UP) Hardware Abstraction Layer (HAL) are not available. These images are not available when you start a Pre-Boot execution (PXE) client WDS boot image on an ACPI Multiprocessor (ACPI APIC MP) computer.

This problem occurs when the multiprocessor computer is running Windows Server 2003, Windows XP, or Microsoft Windows 2000.



CAUSE
Windows Imaging format (WIM) images are displayed to the user based on the HAL type of the client computer. Therefore, only WIM images that exactly match the HAL type of the client computer are displayed in the menu of operating system images. In RIS, ACPI Multiprocessor (ACPI APIC MP) images appear when you start a PXE client that uses an ACPI Uniprocessor (ACPI APIC UP) computer HAL. However, in WDS, the behavior differs from the behavior in RIS.



RESOLUTION
To resolve this problem, apply hotfix 937333 to the startup image on the WDS server. For more information about this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

937333 WDS cannot generate more than 255 client names when you use WDS to deploy Windows Vista



WORKAROUND
To work around this problem, create an operating system image for each computer HAL type that is present in your environment. Or, apply a specific Wdsclientunattend.xml file to each client computer.

Each Wdsclientunattend.xml file must specify the image to apply to each client computer. You can create the Wdsclientunattend.xml file by using the Windows System Image Manager (WSIM) tool. WSIM is included in the Windows Automated Installation Kit (AIK). For more information, download the &quot;Deploying and Managing the Windows Deployment Services Update on Windows Server 2003&quot; guide. To do this, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkId=81031



MORE INFORMATION
After you apply hotfix 937333, update a Setup binary file in image 2 of the Boot.wim file. To do this, follow these steps.

Note Image 2 is a Setup Windows Preinstallation Environment (Windows PE) image.  On the WDS server, install the Windows OEM Preinstallation Kit (OPK) tool set or the Windows Automated Installation Kit (AIK) tool set. Extract the CAB file (Windows6.0-KB -arch.cab) to a temporary folder. To do this, follow these steps:  Click Start, click Run, type cmd, and then click OK. At the command prompt, type the following command, and then press ENTER:

Expand.exe  -F:*

Note represents the path of the CAB file. represents the path of the temporary folder.

If you receive an error message when you run this command, use the Expand.exe tool to extract the files. This tool is included in the Windows OPK and in the Windows AIK.  Disable the startup image to make it unavailable for download. To do this, type the following command at the command prompt, and then press ENTER:

wdsutil.exe /set-image /image: /imagetype:boot /architecture:{x86|x64|ia64} /enabled:no

Note represents the name of the startup image.</li> Export the startup image from the WDS server. To do this, type the following command at the command prompt, and then press ENTER:

wdsutil.exe /export-image /image: /imagetype:boot /architecture:{x86|x64|ia64} /destinationimage /filepath:

Note represents the path of the Boot.wim file.</li> Mount the &quot;Microsoft Windows Longhorn Setup (x86)&quot; image or the &quot;Microsoft Windows Longhorn Setup (x64)&quot; image (index 2) of the Boot.wim file for read access and for write access. To do this, type the following command at the command prompt, and then press ENTER:

imagex.exe /mountrw  2

Note represents the location where you want to mount the index 2 image. For more information about how to mount an image and about how to use the ImageX.exe tool, see the documentation in the Windows Vista OPK.</li> Copy the Wdsclient.dll file from the temporary folder that was specified in step 2 to the source folder in the location at which you mounted the index 2 image.</li> 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:

imagex.exe /commit /unmount

</li> Add the Boot.wim file back to the WDS server. To do this, type the following command at the command prompt, and then press ENTER:

wdsutil.exe /replace-image /image: /imagetype:boot /architecture:{x86|x64|ia64} /replacementimage /imagefile:

</li> Delete any folders that were created in step 2 and in step 5.</li></ol>

Keywords: kbexpertiseadvanced kbtshoot KB935772

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.