Dell Latitude 5400 BIOS no longer supports legacy ROM's. Can these boot to the K2000 KBE without having to use a USB thumb drive?
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?
Answers (2)
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
Comments:
-
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. - ScottAday 5 years ago
-
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 - SMal.tmcc 5 years ago
-
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. - ScottAday 5 years ago
-
I can't boot into k2000 from UEFI devices, only legacy BIOS. Did anyone figure this out yet? - moddo 5 years ago
-
it was resolved read above, but this was for a single model not uefi in general - SMal.tmcc 5 years ago
DHCP Configuration for BIOS and UEFI PXE.
There is a link at the bottom on how to configure MS DHCP. When I downloaded the link the file came down with no extension, if that happens just rename the file with a .pdf extension
We have cut over to UEFI and when we need to boot a legacy we either boot stick it for single machine or change the 67 DHCP entry for that subnet temporarily to legacy, boot, then change it back when we have a group.
Increase the UEFI KBE Boot delay in settings - to what value? (i made it 40 sec) didn't work.
And - boot set to uefi only no legacy - I dont see this setting anywhere in the bios.
It was resolved read above, but this was for a single model not uefi in general - no it wasn't, i have a 5401 - redwingnut35 5 years ago
What DHCP are you using? SDA's or other?
The boot also needs drivers as well as post
Did you download the WinPE drivers (https://www.dell.com/support/home/us/en/04/product-support/product/latitude-14-5401-laptop/drivers - Dell Command | Deploy Driver Pack) and add those to the PE driver store on the SDA, compile a new KBE that includes those and also on the SDA settings make that default?
BTW
My current delay is 10sec - SMal.tmcc 5 years ago
Thank You for your help. - redwingnut35 5 years ago