How to fix "Unsuccessful EFI network boot" on Vmware Workstation 12?


I am trying to create our UEFI golden images on VMWare Workstation 12 Pro for deployments. I configured the VM to EFI boot and network boot as first option but when trying to network boot it says it was unsuccessful. Does anyone know of any troubleshooting steps or steps I have missed to configure this to work? My setup is:

K2000 4.0.695
VMWare Workstation 12 Pro

EFI boot selected
Bridged adapter

2 Comments   [ + ] Show comments
  • I am getting the error

    _unseccessful.hell (Unsupported Option)0)
    Sucess downloaded NBP file. - abane 7 years ago
  • What is your dhcp optionss? Option 67 should be set to ipxe.efi for uefi pxe booting. - cserrins 7 years ago
    • Option 66 x86 ef, 67 x64 efi. Both are send ipxe.efi - abane 7 years ago
      • Option 66 should be the ip of your k2. There are 2 boot options in 4.0 and higher, undionly.kpxe for legacy/bios machines and ipxe.efi for uefi. You can configure this automatically with a few servers, search the quest site for configuration information. - cserrins 7 years ago
      • We have:

        if option arch = 00:06 {
        filename "ipxe.efi";
        } else if option arch = 00:07 {
        filename "ipxe.efi";
        } else {
        filename "undionly.kpxe";

        This shouldn't cause the issue we are seeing correct? - abane 7 years ago

Answers (2)

Answer Summary:
Posted by: TheAustinDave 7 years ago
Third Degree Brown Belt

Top Answer

Booting VMWare Workstation to the KBE is usually best completed by creating a special UEFI boot ISO for the VM system that you can point to on the CD drive.

The special KBE can be created by using KBE Manipulator and go to the options section to enable the (UEFI Iso) box. Then create the KBE and have it upload to the KACE Deployment appliance, once done download the ISO file and on the VM have it point to the ISO file (may have to add it to the datastore).

Use the power on to Firmware to boot to the UEFI (BIOS) and select the CD to boot.

  • This fails before we have a chance to load the KBE. iPXE fails to run after the NBP file is downloaded - abane 7 years ago
    • Correct, I would not recommend PXE booting the VM system but use the CD drive of the system pointing to the ISO file of the KBE. - TheAustinDave 7 years ago
      • Can you elaborate on why you wouldn't recommend it? It has not been an issue with BIOS/legacy booting - abane 7 years ago
Posted by: TheAustinDave 7 years ago
Third Degree Brown Belt
The reason that I recommend using the ISO file is that it would not rely on the DHCP services to load the KBE file needed to capture the image or if using to deploy a test image to VM system. Once the system loads the ISO file from the CD to the RamDISK it will be the same as we just changed where the data for the ram-drive is loaded (tftp from appliance vs ISO). Earlier versions before 4.0.695 or if you have Windows DHCP 2008r2 or earlier using the scope polices is an option that is not available.

Using the KBE Manipulator allows the ISO file to be easily created and then download the ISO file to place onto the datastore of the VM.

  • Thank you for the detail. Initial testing looks promising! - abane 7 years ago

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