/build/static/layout/Breadcrumb_cap_w.png
06/14/2019 276 views

Since the new BIOS doesn't support legacy ROM's the PXE boot option won't work. Documentation for the K2K says their DHCP should see that these computers need UEFI and boot to that environment but everything I have found online about this says you have to create a USB thumb drive to boot to UEFI and connect to the K2K before the computers can be imaged. Is there some way to network boot these to UEFI like we could to PXE?

0 Comments   [ + ] Show comments

Comments


All Answers

1

You can configure your dhcp for UEFI only and switch all machines over to uefi from now on


Or if you are using MSDHCP you can set up for either bios tyoe

Answered 06/14/2019 by: SMal.tmcc
Red Belt

  • Quest says the K2000 DHCP already supports UEFI by default. The computers are being assigned IP's by the K2K but will not boot to the KBE over the network as they would with legacy.
    • Check bios for settings. Secure boot disabled, network stack uefi enabled and boot set to uefi only no legacy. Have you updated the KBE driver store with the proper WIN PE drivers for booting this model nic. Make sure the newer kbe is set to default for pxe booting in settings, Increase the UEFI KBE Boot delay in settings
      • It appears to have been an issue with the boot delay. Letting the computer go into PXE boot automatically when starting up will fail, but if I go into boot options and manually choose the same option it will work. Thanks for the help on this.