PXE (Preboot Execution Environment)

PXE (Preboot Execution Environment) is a system that enables a computer to boot over a network before an operating system is installed. Thanks to this technology, a computer can be started via its network interface card without requiring physical storage devices such as a local hard drive or optical drive. With PXE, an operating system image is retrieved from a server on the network (typically a TFTP server), loaded into the system’s RAM, and executed from this environment.

PXE Operation Diagram (Generated by Artificial Intelligence)

Historical and Current Usage

PXE was originally developed to install operating systems on terminals that lacked local storage and were known as thin clients. Such systems operate the operating system from a central server to simplify management. Today, PXE is primarily used in large-scale enterprise environments to remotely and automatically deploy operating systems to client computers.

Core Components of PXE

For PXE technology to function, the following core components are required:

• PXE-Enabled Network Interface Card (NIC): PXE support is provided through firmware embedded in the network card. During startup, this card obtains an IP address from a DHCP server and downloads a boot image (such as WinPE) over the network into system memory.
• DHCP Server: Assigns an IP address to the client computer and provides the name and network location of the boot image required for initialization.
• TFTP Server: Makes files such as the boot image requested by the PXE client accessible over the network. TFTP is the primary transfer protocol used during the PXE boot process.

PXE Operation Process

The PXE boot process consists of the following steps:

1. When a computer with PXE support is powered on, the PXE code within the network card’s firmware is activated.
2. The computer sends a broadcast request to the DHCP server to obtain an IP address along with the name and location of the boot image.
3. The DHCP server responds to this request.
4. The computer connects to the TFTP server to request the boot image and necessary files.
5. The TFTP server transmits the requested files to the client.
6. The computer loads these files into memory and completes the network boot process.

During this process, the client receives its IP address from the DHCP server and the path to the Network Boot Program (NBP) from the PXE server. The client then downloads and executes the NBP.

PXE Booting Across Different Networks

When the client and server reside on different IP networks, routers must be configured to ensure DHCP and PXE requests reach their intended servers. In such cases, IP helper addresses are configured on the routers to direct DHCP and PXE requests to the correct servers.

PXE and Configuration Manager

When used with Configuration Manager, PXE can be employed to deploy operating systems over the network. In this method, operating system and boot images are sent to a PXE-enabled distribution point. This approach can be used both to update existing computers and to install operating systems on new systems.

Security Warnings

The PXE protocol lacks authentication and encryption mechanisms and is therefore insecure. For this reason, PXE clients and servers should only be used in physically secure and controlled network environments.