How to configure PXE to Deliver NetBoot Services in LANDESK 2016.3

Version 5

    Verified Product Versions

    LANDESK Management Suite 2016.x

    Introduction

    LANDESK 2016.3 introduced Self-Electing Subnet Services. This changes the way NetBoot Services are configured. Self-Electing Subnet Services will need to be enabled alongside PXE Services in the Client Connectivity Agent Settings for managed devices:

    Agent Settings 1.png Agent Settings 2.png

     

    For more information on the full configuration, please visit How To: Configure PXE services in LDMS 2016.3.

     

    Changes in Internet Information Services (IIS)

    NetBoot Installers includes files that have zero-value extensions. IIS is not configured by default to account for these file types, so the IIS MIME Types need to be updated.

     

    Open Internet Information Services (IIS) Manager on the Core Server and browse to the Default Web Site. From there, select MIME Types:

    IIS Manager.png

    In the MIME Types Action Window, select Add... Configure the new "." MIME Type as follows:

    MIME Type.png

    Click OK. It is not necessary to run an IISReset.

    This change will also need to be made on any Preferred Servers planned to be used for NetBoot Services.

     

    Configuring the NetBoot Install Files Repository

    By default, the NetBoot Image location on the core will be http://corename/landesk/vboot/Netboot.

     

    This location can be configured in the Operating System Provisioning tool in the LANDESK Management Console.

     

    Go to Tools > Provisioning > OS Provisioning. Select Preboot and click Manage NetBoot Image Mappings:

    Preboot.png Manage Netboot IMage Mappings.png

    Click OK once the desired Configurations have been made.

     

    At this point, the Self-Elected PXE Representatives will need to check in with the Core Server to Acknowledge the updated Repository Settings. This can be done in two ways:

    • Manually restarting the LANDESK PXE Service on the Elected Representative.
    • Waiting for the Elected Representative to check in via the Polling Frequency (Configured in the Self-Electing Subnet Services Tool).

     

    When this is done, the pxesvc.log located on the Representative under C:\ProgramData\LANDesk\Log will log something similar to the following:

     

    Thu, 16 Feb 2017 12:32:35 Redirecting and resolving paths for Default.
    Thu, 16 Feb 2017 12:32:35 Original path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/, redirected path: http://ldcore20163.ADAY.local/ldlogon/mac/NBIs/Stamped.nbi/ 
    Thu, 16 Feb 2017 12:32:35 Redirected path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/, resolved path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/ 
    Thu, 16 Feb 2017 12:32:35 Redirecting and resolving paths for VMware7,1.
    Thu, 16 Feb 2017 12:32:35 Original path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/, redirected path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/ 
    Thu, 16 Feb 2017 12:32:35 Redirected path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/, resolved path: http://ldcore20163/ldlogon/mac/NBIs/Stamped.nbi/ 
    Thu, 16 Feb 2017 12:32:35 ******* Leaving GetNetbootFiles *******
    

     

    Space Requirements on the Elected Representative

    The Space Requirements on the Elected Representatives is very little. Elected PXE Representatives will redirect the NetBooted Macs to the Core/Preferred Server in order to pull down the full NBI.

     

    A typical size for a LANDESK Stamped NBI will be around 550MB. The NBI files copied down the PXE Representatives will be around 20-30MB in size. On the Representative, they are located under C:\Program Files (x86)\LANDesk\PXE\System\images\mac.

    The NBI's will also get copied to the SDMCache on the Representative before being copied to the default location. They will appear twice on the Representative for some time before being remove by the SDMCache.