In our environment, localboot is done by not hitting F12 to PXEBOOT - so there was no need. That, and we boot to PXELINUX first - that provides a localboot option.
The working BOOTMGR I have is version 6.0.6000.16386. The non-working BOOTMGR is version 6.0.6001.18000. The solution was found in this thread: http://www.msfn.org/board/index.php?showtopic=114711&hl=
When I do this, every menu item that shows in the Windows Boot Manager is named "Ramdisk options". Thoughts? Problem solved. Found in another thread here - the BOOTMGR.EXE from the latest WAIK is the culprit. Using the BOOTMGR.EXE from the older WAIK displays the menu items correctly. The working BOOTMGR I have is version 6.0.6000.16386. The non-working BOOTMGR is version 6.0.6001.18000.
Thank the Lord I found this thread - was beating my head against the wall trying to figure out this issue. The working BOOTMGR I have is version 6.0.6000.16386. The non-working BOOTMGR is version 6.0.6001.18000.
Has anyone gone any further with this? I'm experiencing the same issue - every menu entry in the Windows Boot Manager that is created in the BCD reads "Ramdisk options" - using the "BCDedit /store *path*\TFTPRoot\Boot\BCD /set {guid} description "WinPe1"" command changes nothing. The enum shows this description has been changed for the GUID entry, but that description never shows. The booting of the different WIMs works fine - but a user doesn't know what WIM he is selecting since each name is the same. Using EasyBCD or VistaBootPro doesn't seem to offer a way to change it either - it's not a matter of "not knowing the syntax."
In our shop, we've modified the script to run a CMD file that includes the specific switch for that image, rather then reference the image itself. Yes, it's an extra step to create that CMD for each image, but we require that degree of control.