SDA KBE Rebuild Issue
Well its time again after a new upgrade the KBE has to be rebuilt, and wouldn't you know we ran into another issue : /
We are getting an error once we log into the SDA preboot screen that "Could not Boot connection timed out http://ipxe.org" xxxxxxxx
The server is the most current release (along with Media Manager, KBE Drivers from portal).
Windows Version: 1809
SDA Version: 7.1.94
Things we have tried:
1.) Completely removed and rebuilt the KBE from the ground up (to also include the additional PXE drivers since this is an 1809 deployment) -no joy
2.) Removed old driver packages from Driver store and added the most current releases -no joy
3.) Tested on other similar hardware (to rule out potential onboard nic failure) (along with switch ports/configs etc) -no joy
4.) Update BIOS on hardware (Latitude 5500 laptops) -no joy
5.) Rebooted SDA after each update performed above (also re-cached drivers) -no joy
6.) Reset BIOS on units to defaults and enabled exact known working settings we have always used prior -no joy
7.) Ruled out Faulty cabling -no joy
8.) Tried various USB dongles -no joy
I am sure there are some things I am forgetting, but what am I missing? It's strange because we can access the share, it can be pinged prior to booting into the environment, from a management side everything is normal. When it comes time to boot a laptop we have always imaged prior (That has had no hardware/mobo revision changes) it acts like it cannot boot fully into the environment to execute a scripted installation... any help or ideas would be much appreciated. We are very close to opening a support ticket but wanted to see if the community had any other ideas or have run across this before.
so the SDA uses an open source protocol called iPXE:
The SDA uses an unmodded version of iPXE, I guess that is the "SDA preboot screen" you're referring to... when iPXE fails, their developers will point you to a URL and an error message, that could determine what is going on.
"Could not Boot connection timed out http://ipxe.org" xxxxxxxx it would be good to know what's the full URL printed on your error message.
Sometimes, the error goes away too fast, that's impossible to catch with naked eye, I would grab a smartphone, record a video, and slow-mo playback until the error happens.
iPXE issues are normally caused by:
-DHCP not properly configured (The DHCP is requesting the wrong tftp boot file and/or forwarding the wrong device IP to the SDA)
-Switches without the portfast enabled setting (Spanning Tree Protocol)
-TFTP Server on the SDA being flooded\spammed by other switches (check the TFTP log, and make sure the IPs there are from actual devices).
-Network issues (traffic shaping rules, network saturation)
-The BIOS+NIC are not compatible with iPXE. (Not all devices are iPXE compatible out of the box).
Things to try:
-If you were to spin up a Virtual Machine, on the same subnet as the KACE SDA, is this Virtual Machine able to iPXE boot just fine? (VMs like VMware, Hyper-V , are 100% iPXE compatible, and being on the same subnet as the SDA, could rule out network issues).