Systems Deployment Question
Installing KBE Boot Media to WinRE volume.
One of the PSO techs at UserKon mentioned that there is a process for using the WinRE volume to push the KBE media to a system and then flagging the systems to boot to it on next startup.
Would anyone happen to have a link to instructions for this process?
Our current DHCP server cannot simultaneously support Legacy and UEFI PXE booting. We are primarily using legacy on systems but gradually switching over to UEFI. I'm currently having to manually boot UEFI systems to the KBE via a USB drive which is rather time consuming.
If there is already a documented process for this it'll save me a bit of time and trial/error.
Answer Chosen by the Author
This is something I haven't seen in years.. but the steps were like:
• Store KBE on the local workstation, eliminating PXE
• Copy KBE as a midlevel task (or copy to workstation
as a k1 script), naming it winre.wim
• Run ReagentCcommands to boot to the KBE.
– reagentc /disable
– reagentc /setreimage /path %systemdrive%\kace_recovery
(path points to the directory containing winre.wim)
– reagentc /enable
– reagentc /boottore
– shutdown /r
start /wait xcopy winre.wim c:\KACE\Recovery
ReAgentC.exe SetReImage /Path c:\kace\recovery /Target c:\windows
I understand your might be using Windows Server 2008.... just so you know, the KACE SDA has it's own DHCP that supports UEFI and Legacy, the problem is this only works for customers who have a separate network for imaging.
Also, free solutions such as the Linux ISC DHCP, have this ability and it's free.
If you are using Infoblox, (which is a Linux DHCP), that's possible via console, contact your vendor about it.
Anyways, I remember seeing a DELL KCE from 2014, it was a PDF with those instructions very detailed, it was popular back then, when DHCP couldn't UEFI PXE Boot