Windows Deployment Services - client will not boot into new OS Loader

[benjieevski]

Hi,
I was wondering if anyone can help with a problem that has been bugging me for the last few days!
I have a new server built with Windows 2003 R2 with SP2 on it. It was running RIS before upgrading to SP2 and now is running Windows Deployment Services in Mixed Mode.

My Problem is as follows, when I boot from a client (Dell Optiplex GX270 in this case) using the netboot (PXE) and press F12 I am only greeted with the "Os Chooser 5.2 Menu". This only displays the old RIS functionality and the old Legacy Images.
What I am expecting is to get the new Windows Boot Manager with the options of Vista Setup, and RIS.

The Server is setup as follows.
I have some old RIS images installed within Legacy Images.
I have some new images converted from Legacy Images to the new WIM File and added within Install Images.
I have added a new Install Image using the "install.wim" file from the Vista DVD for Vista Business.
I have added a new Boot Image using the "boot.wim" file from the Vista DVD for Vista Business.
I have added a new Boot Image using the "winpe.wim" file from the WIAK Kit.
I have then selected either the boot.wim or winpe.wim as the "default boot image" under the servers properties and restarted it's services.
Then I boot the client and I still go back into the WDS Legacy mode/RIS.

If anyone could help why this is happening I would be very grateful?
Many thanks
Ben

 

[Zelandakh]

If you run WDS from the console you can add new images which is more thorough than doing it remotely. Doing it that way worked for me.