Skip to main content

Methods and Details

This article provides technical details and information on PXE boot. Configure network boot settings in the hardware type section.

Overview of Network Boot Protocols

Legacy PXE Boot / BIOS PXE Boot

Supported by most older and many newer devices.

  1. The client requests boot information via DHCP.
  2. It receives the server address and the bootloader filename in response.
  3. It'll download the bootloader via TFTP and execute it.
UEFI PXE Boot

Many newer devices support this.

  1. The client requests boot information via DHCP.
  2. Receive the server address and file name of the bootloader in response.
  3. Download the EFI bootloader via TFTP and execute it.
UEFI HTTP Boot

Supported by some newer devices. Requires UEFI version 2.5 or later.

  1. The client requests boot information via DHCP.
  2. Receive a URL to the bootloader.
  3. Download the EFI bootloader via HTTP and execute it.

Secure Boot

To use Secure Boot, first register the openthinclient OS EFI bootloader as trusted in the thin client’s BIOS/UEFI.

The exact procedure depends on the specific BIOS/UEFI. Either enable a special mode that allows a one-time unsecured boot and remembers the bootloader’s signature, or select a bootloader from a list.

Disable Secure Boot if the setup process is relatively cumbersome.

Back to top