No x64-based images appear in the list of images when you connect to a Windows Server 2003-based computer that is running Windows Deployment Services

You use the Pre-Boot Execution Environment (PXE) to start an x64-based client computer. Then, you connect to a Microsoft Windows Server 2003-based computer that is running Windows Deployment Services (WDS). However, no x64-based images appear in the list of images, even when the images are present.

This issue occurs if the client computer incorrectly reports its architecture to the Windows Deployment Services server.

To resolve this issue, use the Wdsutil.exe command-line tool to enable architecture detection. To do this, type the following command at a command prompt on the server, and then press ENTER:

The PXE specification states that each network-booting client computer must indicate its architecture by setting Dynamic Host Configuration Protocol (DHCP) option 93 to the appropriate value. However, on many x64-based client computers, the value may not be set. Or, the value may be set incorrectly. For example, the architecture may be specified as x86 even though the client computer is x64-capable. The following table lists the architecture values.When architecture detection is enabled, the client computer downloads a network boot program (Wdsnbp.com) from the server. Then, the network boot program reports the architecture of the client computer to the server. This operation occurs before the client computer downloads the default boot program for its architecture. Examples of the default boot program include Pxeboot.com and Pxeboot.n12.

Architecture detection may add time to the boot process, increase network traffic, and increase the load on the server. By default, architecture detection is turned off.

To review the server's architecture detection setting, type the following command at a command prompt, and then press ENTER:For more information about WDS and the Wdsutil.exe command-line tool, visit the following Microsoft Web site: For more information about a similar issue, click the following article number to view the article in the Microsoft Knowledge Base: