Boot images are not enumerated by Windows Deployment Services server after you create new derivatives of an existing Windows PE boot image on a Windows "Longhorn" Server Beta 2-based computer (912046)

MORE INFORMATION

When you create new derivatives of an existing Windows PE boot image, WDS creates an image file in the Microsoft Windows Imaging Format (WIM) image format.

You can store this image file at the location of your choice. However, WDS does not automatically add the image file to the list of available boot images. You must manually add the image to the WDS server by using one of the WDS management tools. You cannot just copy the image file to the Images folder.

To add the new boot images to the WDS server by using the WDS management tools, follow these steps:

1. Create a new derivative image of an existing Windows PE boot image by using one of the WDS management tools. For example, create a new capture image or a new discover image by using the WDSUTIL tool or by using the WDS MMC snap-in.
2. Save the images that you create at the location of your choice.
3. Add the images that you saved in step 2 to the \RemoteInstall\Boot\Arch\Images folder in WDS server. This is the folder where Windows PE boot images are stored. You can useeither the WDS MMC or the WDS command-line utility, Wdsutil.exe, to store the images.
   
   Note In this folder, Arch represents the architecture of the boot image. For example, WDS server stores x64-based images in the \RemoteInstall\Boot\x64\Images folder.

When you add the images to the WDS server, a control signal is sent to the WDS service. This control signal helps to create a BCD store entry. Then, the BCD store entry enumerates the boot images on the Boot menu.