When you start an Itanium-based client computer and then try to connect to a WDS server that is running Windows Server 2003, you may be unable to see the OSChooser menu

Article translations Article translations
Article ID: 927167 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

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.

CAUSE

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.

RESOLUTION

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:
      WDSUTIL /Add-device /Device:Name_of_device ID:GUID_or_media_access_control_address /BootProgram:oschooser\IA64\oschoice.efi
    • If a device already exists in Active Directory as a pre-staged computer object and if the boot program parameter is not set, use the following command to set the boot program parameter:
      WDSUTIL /Set-Device /Device:Name_of_device /BootProgram:oschooser\IA64\oschoice.efi

STATUS

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

MORE INFORMATION

Steps to reproduce the problem

  1. Install RIS on a server that is running Windows Server 2003.
  2. Add an Itanium-based Windows Server 2003 boot image in the RIS management console.
  3. Confirm that you can connect to the RIS server from an Itanium-based client and that you can see the OSChooser menu.
  4. Install WDS on the server.
  5. Confirm that you can connect to the WDS server from the Itanium-based client and that you can see the OSChooser menu.
  6. Configure the WDS server to run in mixed mode.
  7. Restart the Itanium-based client. You can no longer see the OSChooser menu from the client.

Properties

Article ID: 927167 - Last Review: October 11, 2007 - Revision: 1.3
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, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
Keywords: 
kbtshoot kbprb KB927167

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com