PXE Remote Maintenance: Complete Network Boot Guide

HYSTOU M9 WiFi 6 BT5.2 2.5G LAN Dual Band Connectivity
PXE Remote Maintenance
Remote maintenance is essential for IT teams, especially when managing multiple devices across locations. However, many professionals face critical challenges when dealing with unbootable systems or bare-metal machines. PXE remote maintenance solves this problem effectively.
It allows you to boot and maintain computers entirely over the network, without relying on local storage like hard drives or USBs.

What Is PXE?

PXE stands for Preboot Execution Environment. It is a network boot standard developed by Intel. Simply put, PXE lets your computer start directly from its network card, before loading the local operating system.
This is the core advantage of PXE remote maintenance. Even if a computer’s hard drive is completely failed or corrupted, you can still boot into a maintenance system over the network.

Core Components of PXE

PXE relies on three essential services working together:
  • DHCP Server: Assigns IP addresses to clients and tells them where to find the boot server
  • TFTP Server: A lightweight file transfer protocol for sending small boot files
  • Boot Files: Special files that load the maintenance system kernel and environment

Common Problems & Deep Troubleshooting Guide

While PXE is powerful, it has specific requirements that often cause failures. Below are the most common issues with technical solutions and measurable troubleshooting steps.

1. Critical DHCP Configuration Errors

This is the #1 cause of PXE boot failures. PXE requires specific DHCP options that most default DHCP servers do not enable.
Critical Note: If your network uses VLANs or multiple subnets, PXE broadcasts will not cross routers by default. You must configure DHCP Relay (IP Helper) on your layer 3 switches to forward PXE requests to your PXE server.

2. Network Connectivity Issues

PXE is extremely sensitive to network latency and packet loss. For reliable operation:
  • Ensure client and server are on the same subnet (or DHCP Relay is properly configured)
  • Use Gigabit Ethernet (10/100Mbps works, but is much slower)
  • Test network connectivity with ping -t 192.168.1.100 from another machine
  • Check for duplicate IP addresses on the network

3. Legacy vs UEFI Boot File Mismatch

This is a very common mistake. Modern computers use UEFI instead of the old Legacy BIOS, and they require completely different boot files. Using the wrong file will cause PXE boot to fail silently.

4. Firewall Blocking TFTP Traffic

TFTP uses UDP port 69. Most operating system firewalls block this port by default. You must explicitly allow TFTP traffic on your PXE server.

How to Check If Your Computer Supports PXE

Before setting up PXE, confirm that your target computers support network boot. Here are the accurate methods for Windows and Linux systems.

Check via BIOS/UEFI

This is the only 100% accurate method:
  1. Restart your computer
  2. Press the boot menu key during startup (usually F2, F10, F12, or Del)
  3. Look for options labeled:
    • Network Boot
    • PXE Boot
    • LAN Boot
    • IPv4 PXE / IPv6 PXE
If you see any of these options, your computer supports PXE. If not, it does not have native PXE support.

Check via Device Manager (Windows)

  1. Right-click the Start menu and select Device Manager
  2. Expand the Network adapters section
  3. Right-click your Ethernet adapter and select Properties
  4. Go to the Advanced tab
  5. Look for properties related to:
    • Wake-on-LAN
    • Network Boot
    • PXE Support
If these options exist, your network card supports PXE.

Check via Terminal (Linux)

  • Open a terminal window
  • First, identify your network interface name:
    bash
    ip link show
  • Then use ethtool to check for PXE support (replace eth0 with your interface name):
    bash
    sudo ethtool eth0
  • Look for the “Wake-on” line. If it shows g (Wake on MagicPacket) Or mentions PXE, your card supports network boot.

Step-by-Step PXE Remote Maintenance Setup

This guide uses the most popular and easiest tools for PXE server setup. We recommend Tiny PXE Server for Windows or dnsmasq for Linux, as they combine DHCP and TFTP in a single package.

Step 1: Prepare the Server Environment

Prerequisite: Your PXE server must have a static IP address. Dynamic IP addresses will break PXE functionality.
  1. Assign a static IP to your server (e.g., 192.168.1.100)
  2. Disable any other DHCP servers on the same network (conflicts will cause failures)
  3. Download and install your chosen PXE server software
  4. Configure the DHCP server with the critical options from the table above

Step 2: Place Correct Boot Files & Maintenance Images

Critical: Choose the correct boot file based on your client’s boot mode.
Client Boot ModeRequired Boot File
Legacy BIOS (old computers)pxelinux.0
Modern UEFI (64-bit)bootx64.efi or ipxe.efi
UEFI (32-bit, rare)bootia32.efi
  1. Place the appropriate boot file in the root directory of your TFTP server
  2. Download a maintenance system image (WinPE for Windows, Clonezilla for disk cloning, or a Linux rescue image)
  3. Extract the entire contents of the ISO image to a subdirectory in your TFTP root
  4. Update your PXE configuration file to point to the correct kernel and initrd files

Step 3: Configure Client BIOS/UEFI Boot Priority

  1. Restart the target computer you want to maintain
  2. Press the BIOS/UEFI key during startup (F2, F10, F12, or Del)
  3. Navigate to Advanced > Network Stack
  4. Set PXE Boot or Network Boot to Enabled
  5. Go to the Boot menu
  6. Set Network Boot (LAN) as the First Boot Priority
  7. Save changes and exit BIOS/UEFI

Step 4: Boot Into Maintenance System & Perform Operations

  1. The client computer will now automatically start the PXE boot process
  2. It will send a DHCP broadcast request
  3. Your PXE server will respond with an IP address, TFTP server address, and boot file name
  4. The client will download the boot file from the TFTP server
  5. The boot file will load the maintenance system kernel and environment
  6. Once booted, you can perform any maintenance tasks:
    • Reinstall the operating system
    • Clone or backup hard drives
    • Repair corrupted system files
    • Scan for viruses and malware
    • Reset forgotten passwords

What If Your Computer Doesn't Support PXE?

Many consumer laptops and some modern ultrabooks have PXE disabled by default or removed entirely. Here are the solutions:

  1. USB PXE Boot: Create a special USB drive that loads the PXE client from USB, then continues the boot process over the network. This works on almost any computer with USB boot support.
  2. External Network Card: Use a USB-to-Ethernet adapter or PCIe network card that explicitly supports PXE boot.
  3. BIOS Modification: Some motherboards allow enabling PXE through modified BIOS files. This is advanced and carries a risk of bricking your device.

Pro Tips for Reliable PXE Remote Maintenance

  • Test on a single machine first: Always test your PXE setup on one computer before deploying to hundreds of devices.
  • Use separate VLANs for PXE: Isolate PXE traffic on its own VLAN to prevent interference with normal network operations.
  • Keep boot files updated: Regularly update your maintenance images with the latest drivers and security patches.
  • Monitor server performance: PXE can be network-intensive during large-scale deployments. Ensure your server has sufficient bandwidth.
  • Document everything: Keep detailed records of your PXE configuration, boot files, and troubleshooting steps for future reference.

Conclusion

PXE remote maintenance is an indispensable tool for modern IT teams. It eliminates the need for physical media, reduces downtime, and allows you to manage hundreds of devices from a single location.
By understanding the difference between Legacy and UEFI boot modes, configuring the correct DHCP options, and following the step-by-step guide, you can set up a reliable PXE server in just a few hours.
Whether you’re maintaining industrial PCs in a factory, servers in a data center, or computers in a school lab, PXE will save you countless hours of manual work.
Hystou Mini PC Official Logo

HYSTOU

HYSTOU has established its R&D headquarters in Shenzhen, drawing on over a decade of experience. Our core team members, who previously served at renowned companies such as Inventec and Quanta Computer, form the backbone of our technical expertise. With robust R&D and innovation capabilities, we remain steadfast in our commitment to pursuing excellence in the field of technology products.

Facebook Twitter Youtube Tumblr
HYSTOU M9 Mini PC Intel i5-1340P Vertical & Horizontal Placement Design

HYSTOU M9 Mini PC

Hystou H6 Industrial Mini PC with Fan-Cooled System

Hystou H6 Industrial Mini PC – Fan-Cooled Triple Display

Hystou H4T-10th industrial fanless mini PC front view

Industrial Fanless Mini PC | Intel 10th Gen i5 | Hystou H4T-10th

HYSTOU GT-3050 Mini PC Design: Compact Chassis with Multiple I/O Ports

HYSTOU RTX 3050 Mini Gaming PC – 8K Workstation with Intel Core i7/i5

Shopping Cart
Scroll to Top

Important Notice on Fraud Prevention

Recently, scammers have been impersonating our company staff to commit payment fraud. To protect your interests, please pay attention to the following matters:

Verify Sender: Check if the email domain is @hystou.com. Immediately delete any emails from non-Hystou domains.

Double-Check: For any account modification requests, cross-verify via the customer service hotline listed on our official website hystou.com or through existing partnership channels.

Refuse Private Transactions: Do not trust claims like “urgent notifications,” “confidentiality requirements,” or “tax policy updates.” All business changes must follow official procedures.

Click to view the announcement details