KACE Product Support Question

KACE SDA : KBE not always loading since 6.0.425 update

09/12/2018 1255 views
Hi all,

I updated to KACE SDA 6.0.425 recently and I changed my DHCP config file to undionly.kpxe because the PXELINUX doesn't work anymore.

Since that moment I noted that my KBE don't always load when I try to boot on the network despite the fact I configured a deployment in my SDA. I have to reboot my client many times (between 2-8) on the network and it ends up loading the KBE while I didn't change anything on my SDA deployment.

Did someone note the same issue?



I have the following screen when it doesn't work:

5 Comments   [ + ] Show comments


  • When you manually boot the machine, does it receive a PXE response when booting from the NIC?
  • Please specify where exactly is getting stuck, any error messages or codes?
  • Can also try restarting the startnet.cmd if it stops with a cmd window and error 53.
  • You can see the message on the picture I uploaded in my initial post... I edited the question
    • What is the brand and model for this computer?

      Also I would try making sure it has the latest BIOS version.

      Also: http://ipxe.org/err/040ee1

      "If connected to a Cisco switch make sure 'spanning-tree portfast' is enabled on the switch. Otherwise iPXE will fail establishing network connection."

      If you are using CISCO switches, make sure that option is enabled, and try to replicate the issue.
      • We have only Dell computers and we face to this issue on several computer models (still Dell). They don't all have the latest BIOS version but we never had problem with PXELINUX.
        It seems to me portfast is configued on all our switches but I have to confirm with our network team
    • PXELINUX is not iPXE... not all PXELINUX devices are compatible with iPXE, manufacturers tend to add compatibility with iPXE with a new BIOS version


      It doesn't matter if it's DELL or not, there are some DELL machines not compatible with iPXE, see:

  • Did you follow the instructions in this knowledge base article?

    We had this issue and it ended up being an issue with improper scoping. We had a mix of computers with DHCP reservations and those without on one VLAN and the DHCP scope didn't get the correct DHCP options, so those machines couldn't PXE boot.
    • On the DHCP we configure only the filename undionly.kpxe. But when my client computer boot on the network card it obtains an IP address so it should also have informations to boot on SDA.
      Furthermore on the same PC if it doesn't boot the first time I retry 2-3 times and then it works (without any change)
      • To narrow it down, try to mimic:


        If your SDA (k2), is a VM, you will need separate VSwitch for the SDA and a dummy VM for iPXE using the SDA's DHCP.

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ