This article has been archived. It is offered "as is" and will no longer be updated.
You start an Itanium-based client computer and then try to connect to a Windows Deployment Services (WDS) server that is running Microsoft Windows Server 2003. After you do this, you may be unable to see the OSChooser menu. Additionally, the client may not receive any response from the WDS server.
This issue occurs because the Itanium-based version of the Windows Preinstallation Environment (Windows PE) 2.0 boot image has not been released. When the WDS server is in mixed mode, the default boot programs that are specified on the WDS server are extracted from the Windows PE 2.0 boot image. This step occurs when the boot image is first uploaded to the WDS server. Because the Itanium-based version of the boot image is unavailable, the Default Boot Program setting for Itanium-based clients points to a network boot program that does not yet exist on the server. Therefore, Itanium-based clients cannot download the OSChooser menu that provides legacy Remote Installation Services (RIS) functionality.
To resolve this issue, use one of the following methods:
In the WDS management console, change the Default Boot Program setting for Itanium-based clients to oschooser\IA64\oschoice.efi in the Boot tab of the Properties dialog box.
Pre-stage all the Itanium-based clients by running one of the following commands. These commands configure the clients to download the oschooser\IA64\oschoice.efi legacy RIS network boot program:
If a device does not already exist in the Active Directory directory service as a pre-staged computer object, use the following command to add the device and to set the correct value for the boot program parameter: