Good day,
We need to add a startup option to the WDS {bootmgr} menu that will always be added after a WDS Server service restart or a server reboot. We are a 99% Microsoft shop but we do have a need to load other OS's and use other utilities from time to time and we accomplish this task by using PXELINUX.
I've added a Real-mode startup application to the Boot\x64\default.bcd, Boot\x86\default.bcd, and Boot\x86x64\default.bcd files with bcdedit and I've added the identifier GUID to the displayorder in the {bootmgr} of each default file. When the WDS Server service restarts the bcd files are generated in RemoteInstall\Tmp and the Real-mode Application entry exists in the files but that option is not added to the displayorder option. I can add my entry to the boot menu with bcdedit /set displayorder"{GUID}" /addlast command, however that entry disappears when the service is restarted or the server is rebooted.
Is there a way to always add my entry to the boot menu when the BINLSVC regenerates the .bcd files? I've placed the bcd contents below for reference. We are using WDS on Windows Server 2012 R2 with all current Microsoft Updates.
Thanks for your help.
Cheers,
Andy.
PS C:\temp> bcdedit /enum all /v /store C:\RemoteInstall\Boot\x86x64\default.bcd
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
fontpath \boot\fonts
inherit {4636856e-540f-4170-a130-a84776f4c654}
displayorder {7a9ada24-5d07-11e3-80bc-00155d6b9111}
timeout 30
Real-mode Application (10400009)
--------------------------------
identifier {7a9ada24-5d07-11e3-80bc-00155d6b9111}
device boot
path Boot\linux\pxelinux.0
description Linux Installations and Utilities
pxesoftreboot Yes
Debugger Settings
-----------------
identifier {4636856e-540f-4170-a130-a84776f4c654}
debugtype Serial
debugport 1
baudrate 115200
Device options
--------------
identifier {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdisksdidevice boot
ramdisksdipath \Boot\Boot.SDI
ramdisktftpblocksize 1456
ramdisktftpwindowsize 4
ramdisktftpvarwindow Yes
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
fontpath \boot\fonts
inherit {4636856e-540f-4170-a130-a84776f4c654}
displayorder {289e043e-895c-4a42-9c2f-e840b6532095}
{fa9cf1d8-073b-4963-9247-e8c677140653}
timeout 30
Windows Boot Loader
-------------------
identifier {289e043e-895c-4a42-9c2f-e840b6532095}
device ramdisk=[boot]\Boot\x64\Images\winpe3_x64.wim,{2e641cb4-8afc-4ec3-935e-4cef559a8f33}
description Coreload 64bit (WinPE 3)
osdevice ramdisk=[boot]\Boot\x64\Images\winpe3_x64.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {fa9cf1d8-073b-4963-9247-e8c677140653}
device ramdisk=[boot]\Boot\x64\Images\winpe5_x64.wim,{736d9675-d0c0-4223-a769-a870978db3de}
description Coreload 64bit (WinPE 5)
osdevice ramdisk=[boot]\Boot\x64\Images\winpe5_x64.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Real-mode Application (10400009)
--------------------------------
identifier {7a9ada24-5d07-11e3-80bc-00155d6b9111}
device boot
path Boot\linux\pxelinux.0
description Linux Installations and Utilities
pxesoftreboot Yes
Debugger Settings
-----------------
identifier {4636856e-540f-4170-a130-a84776f4c654}
debugtype Serial
debugport 1
baudrate 115200
Device options
--------------
identifier {2e641cb4-8afc-4ec3-935e-4cef559a8f33}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
Device options
--------------
identifier {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdisksdidevice boot
ramdisksdipath \Boot\Boot.SDI
ramdisktftpblocksize 1456
ramdisktftpwindowsize 4
ramdisktftpvarwindow Yes
Device options
--------------
identifier {736d9675-d0c0-4223-a769-a870978db3de}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes