Internet Access Required

In contrast to a typical PXE environment, the installation of IGEL OS 12 requires Internet access because the endpoint devices must be able to reach the IGEL App Portal.


  • Your devices meet the requirements for IGEL OS 12. For further information, see Devices Supported by IGEL OS 12.
  • Your devices are able to boot via the network
  • Your devices are in a network with Internet access
  • A DHCP Server is available in your network

Retrieving the Required Files from the OSC ZIP File

  1. Open a web browser, go to, and select the folder OS 12 BASE SYSTEM IMAGE FOR PXE.

  2. Download the ZIP file (e.g. and extract it.
    We will distribute the required files to their appropriate locations later on.

Setting up the DHCP Server

When the devices are powered on, they need to be directed to the TFTP server that provides the low-level files required for booting. This is done by the DHCP server. In our example, we use a Microsoft Windows DHCP server; other DHCP can be used as well.

In the following, we will create three vendor classes, two for UEFI and one for BIOS. 

  1. On your Windows server, go to DHCP and right-click on IPv4.

  2. Define each vendor class as follows:
    1. In the DHCP Vendor Classes dialog, click Add.
    2. Enter the data according to the vendor class you are creating:
      1. Vendor class for UEFI on an x86 architecture:
        • Display name: PXEClient (UEFI x86)
        • Description: PXEClient:Arch:00006
      2. Vendor class for UEFI on an x64 architecture:
        • Display name: PXEClient (UEFI x64)
        • Description: PXEClient:Arch:00007
      3. Vendor class for BIOS on x86 and x64 architectures:
        • Display name: PXEClient (BIOS x86 & x64)
        • Description: PXEClient:Arch:00000

  3. Perform the following steps for each vendor class you have created:
    1. Right-click Scope ([IP address]) DHCP range > Policies and select New Policy from the context menu.
    2. At Policy Name, enter the name exactly as you did for the vendor classes, i.e, once PXEClient (UEFI x86), once, PXEClient (UEFI x64), and once PXEClient (x86 & x64).
    3. Click Next.
    4. In the Configure Conditions for the policy screen, click Add.
    5. In the Add/Edit Condition dialog, click the drop-down menu Value:.
    6. Select the appropriate vendor class.
    7. Activate Append wildcard. click Add and then OK.
    8. Click Next,
    9. Answer the question Do you want to configure an IP address range for the policy? with No and click Next.
    10. Activate option 060 and edit it, according to the policy you are at:
      • For PXEClient (UEFI x86), enter PXEClient.
      • For PXEClient (UEFI x64), enter PXEClient.
      • For PXEClient (BIOS x86 & x64), leave the option empty.
    11. Activate option 066 and enter the Fully Qualified Domain Name (FQDN) or the IP address of your TFTP server.
    12. Activate option 067 and enter the path to the appropriate .efi file on your TFTP server. For example, this might be grub/bootx64.efi for the PXEClient (UEFI x64) vendor class if you are using GRUB as the bootloader.
  4. Review your Scope Options; they should be similar to this:

  5. Go to Server Options, add option 066, and enter the Fully Qualified Domain Name (FQDN) or the IP address of your TFTP server.

Deploying the TFTP Server

In this step, we deploy that TFTP server that provides the bootloader and a minimal OS that will load the higher-level components of IGEL OS.

  1. Install a TFTP server, e.g. SolarWinds. see

  2. Specify the directory in which the PXE boot files will be stored, typically C:\TFTP-Root

  3. Copy the directories and files from the tftp/ directory of your OSC ZIP file to the TFTP root directory, in our example C:\TFTP-Root. The directory structure must be preserved.
    The most important contents are:
    • GRUB Bootloader for 64-bit EFI systems
    • GRUB Bootloader for i386/BIOS systems
    • Configuration file for GRUB Bootloader

Providing the PXE Configuration File (pxe-config.json)

The file pxe-config is used at an early stage of the boot process and will be provided by the TFTP server. It specifies the download paths for specific necessary files, an authentication token for connecting with the IGEL App Portal, and the version of the Base System that is to be installed. 

First, we retrieve the file from the UMS, then we edit it to adapt it to our environment. Afterward, we put it into the appropriate directory on the TFTP server.

Retrieving the File from the UMS

  1. Open the UMS Web App, go to Apps and click the icon.

  2. In the area PXE Configuration, select the version of the IGEL OS Base System you want to install and the validity period for the authentication token that enables access to the App Portal.

  3. Click Generate.

    The file pxe-config.json is downloaded by your browser.

Editing the "pxe-config.json" FIle

  1. In the OSC ZIP file (example:, check out the contents of the webserver/ directory. We will create a reference for each file in step 2.
  2. Edit pxe-config.json as follows:

    • "osc"/"partitions": Enter a list of the URLs of the files to be downloaded from your web server. The format is http://<WEB SERVER ADDRESS>/<PATH>/<FILENAME>

    • "apps"/"version": Ensure that the desired version of IGEL OS is specified.


          "osc": {
              "partitions": [
          "appdata": {
              "app_portal": "",
              "auth_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzUxMiJ9.eyJmaW5nZXJwcmludCI6IjQ2Njc
              "apps": [
                      "name": "base_system",
                      "version": "12.2.1"

Proving the PXE Configuration File (pxe-config.json) via the TFTP Server 

Copy pxe-config.json to <TFTP ROOT>/images/. Example file path: C:\TFTP-Root\images\pxe-config.json

Configuring the Web Server (IIS)

For installing the components of IGEL OS 12, we need a web server. In our example, we will use the Microsoft Internet Information Server (IIS).

  1. If IIS is not already available on your Windows server, install it.

  2. Add the file name extensions and the corresponding MIME types for all file types that are present in the webserver/ directory of the OSC ZIP file. In our example:
    • File name extension .bspl; MIME type application/octet stream
    • File name extension: .sys; MIME type application/octet stream
    • File name extension: .nvgfx; MIME type application/octet stream

  3. Specify a directory in which the required files will be stored, in our example C:\HTTP-Root

  4. Copy all files from the webserver/ directory of the OSC ZIP file into the directory on the web server that has been defined in the section "osc"/"partitions" of your pxe-config.json (see Editing the "pxe-config.json" File). In our example, the directory is C:\HTTP-Root and the files are osc.bspl, osc.nvgfx, and osc.sys. The files may vary depending on the version of your OSC ZIP file.

    Web Server Check

    We recommend checking the URLs for these files in a web browser to ensure the download is functional.

Installing IGEL OS via PXE

Start the devices in your PXE environment. 
If everything has been set up correctly, your devices boot into IGEL OS 12.