How to PXE Boot devices with UEFI

Version 8

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6

    NOTE: UEFI is only supported in Provisioning and not OSD. The industry UEFI standard does not support a menu so you will need to use a scheduled provisioning task instead.  The device must be targeted by a scheduled task in order to network boot.

     

    Provisioning UEFI PXE Boot devices:

     

    Follow these steps to boot the device:

     

    1. Add the client(s) to the Inventory using the Bare Metal Server option:

      A. Expand the Configuration section in the Network view of the LDMS console

      B. Right-click "Bare Metal Server"

      C. Click "Add Devices"

      D. Select a desired identifier type (typically MAC address) and then click "Add"

      E. Enter a name for the computer, and the identifier (such as MAC Address)
          (Note: You can add multiple computers by entering multiple names an identifiers)

      F. Click OK when finished.

    2. Schedule your Provisioning Template (Right click desired template and select "Schedule Template")
    3. Add the client computer(s) to the task, but leave the physical device turned off.
    4. Start the task. It will go to active, and then after a few seconds will go back to a Pending status.
    5. Power on the device(s), and tell it to Network Boot (Usually F12 or Delete).
    6. At this point the PXE Rep should see there is already a task waiting for that machine, and send it straight into WinPE, and automatically begin the Provisioning task.


    In order to import a large list of new devices, the CSVIMPORT utility should be used.   Often hardware vendors are able to provide a list of MAC Addresses and/or other identifiers that can be used to import machine information into the LANDESK Database in order to facilitate provisioning of UEFI Bare Metal (With no operating system installed) devices.


    CSVIMPORT allows the usagse of a .CSV file in order to import Mac Address, Computer name and/or other identifying information.


    For more information about CSVIMPORT, see the following article:


    How to use CSVIMPORT.EXE to import devices