This chapter covers PXE boot and Windows Deployment Services (WDS), two critical technologies for network-based OS deployment. These topics are essential for the CompTIA A+ Core 2 (220-1102) exam, specifically under Domain 1.0 (Operating Systems), Objective 1.1: 'Given a scenario, configure and install Windows operating system features.' While not the most heavily tested area, understanding PXE and WDS is key for questions about unattended installations and network deployment, appearing in approximately 5-7% of exam questions. You will need to know the prerequisites, the boot process, and the roles of DHCP, TFTP, and the WDS server.
Jump to a section
Imagine a restaurant where customers don't bring their own food—they order from the kitchen. PXE boot is like a network restaurant for computers. When a computer turns on (customer arrives), it has no operating system (no food). It first yells 'I need an IP address!' like a customer asking for a table. The DHCP server (host) assigns it an IP (table number) and also tells it where the menu is—the TFTP server. The computer then downloads a small bootloader (the menu) via TFTP. The bootloader tells it what's available: 'You can have Windows, Linux, or a diagnostic tool.' The computer chooses one (based on its own settings or user input) and downloads the full OS image (the meal) from a file server, often using TFTP or HTTP. Once it has the OS, it runs it from memory, just like a customer eats the meal. The key is that the computer never stores the OS locally—it's served fresh each time. This is exactly how PXE (Preboot eXecution Environment) works: the network interface card (NIC) has a small firmware that knows how to request an IP and download a network bootstrap program (NBP). The DHCP server provides the TFTP server address via option 66, and the boot file name via option 67. The NBP then loads the full OS image. Without this, every computer would need a hard drive with an OS preinstalled, like every customer bringing their own lunch.
What is PXE Boot and Why Does It Exist?
PXE (Preboot eXecution Environment) is a client-server interface that allows a computer to boot from the network without a local storage device (hard drive, SSD, or USB). It is defined in the UEFI specification and was originally developed by Intel. PXE is crucial for large-scale OS deployment, diskless workstations, and recovery environments. Instead of imaging each machine manually, an administrator can configure a PXE server to deliver an OS image to multiple clients simultaneously.
How PXE Boot Works Internally
The PXE boot process involves several protocols and steps. The client's network interface card (NIC) contains PXE firmware that complies with the UEFI specification. When the computer starts, the BIOS/UEFI is configured to attempt a network boot. The firmware broadcasts a DHCPDISCOVER message on the local network. Unlike a standard DHCP request, the PXE client includes option 60 (Vendor Class Identifier) set to 'PXEClient' to indicate it is a PXE boot request.
A standard DHCP server can respond with an IP address and other network parameters, but a PXE-aware DHCP server (or a proxy DHCP server) also provides two critical options:
- Option 66 (TFTP server name): The IP address or hostname of the TFTP server that hosts the boot files.
- Option 67 (Bootfile name): The filename of the Network Bootstrap Program (NBP), such as bootmgfw.efi for UEFI systems or bootmgr.exe for BIOS systems.
The client then uses Trivial File Transfer Protocol (TFTP) to download the NBP. TFTP is a simple, connectionless protocol that runs on UDP port 69. It has no authentication or directory listing, making it lightweight but limited. The NBP is then executed in the client's memory. For Windows deployments, the NBP is typically bootmgfw.efi (UEFI) or bootmgr.exe (BIOS). This NBP then loads a boot configuration database (BCD) and presents a boot menu, often allowing the user to choose an OS image or boot to a recovery environment.
Key Components and Values
DHCP Server: Must be configured to provide IP addresses and PXE options. Alternatively, a DHCP proxy can be used to avoid modifying the existing DHCP server.
TFTP Server: Hosts the NBP and other boot files. Default TFTP port is UDP 69.
WDS Server: Windows Deployment Services is a Microsoft role that integrates DHCP, TFTP, and a file server. It provides a unified console for managing boot images (WinPE) and install images (OS).
Boot Image: A Windows PE (Preinstallation Environment) image that loads onto the client and provides a minimal Windows environment to run the setup.
Install Image: The actual Windows OS image (e.g., install.wim) that will be deployed to the client.
Default TFTP Block Size: 512 bytes (RFC 1350). Some implementations support block size negotiation via option negotiation (RFC 2347) to improve performance.
Timeout Values: The PXE client typically waits for a DHCP offer for a few seconds. If none is received, it may fall back to local boot.
Configuration and Verification Commands
To configure WDS on Windows Server: 1. Install the WDS role via Server Manager or PowerShell:
Install-WindowsFeature -Name WDS -IncludeManagementTools2. Initialize the WDS server:
wdsutil /Initialize-Server /RemInst:"C:\RemoteInstall"3. Add boot and install images:
wdsutil /Add-Image /ImageFile:"C:\Sources\boot.wim" /ImageType:Boot
wdsutil /Add-Image /ImageFile:"C:\Sources\install.wim" /ImageType:InstallConfigure DHCP options (if WDS is on the same server as DHCP, it can automatically add option 60). Alternatively, configure a DHCP scope with options 66 and 67.
Verification:
Check that the WDS server is responding: wdsutil /Get-Server
Monitor TFTP traffic: tftp -i <WDS_IP> get bootmgfw.efi (from another machine)
On the client, enable PXE boot in BIOS/UEFI and observe the boot process.
Interaction with Related Technologies
PXE boot relies on DHCP and TFTP. In modern environments, HTTP-based boot (UEFI HTTP Boot) is becoming more common as it is faster and more secure than TFTP. WDS supports both TFTP and HTTP for booting. Additionally, PXE can be used with multicast (via Windows Deployment Services) to deploy images to multiple clients simultaneously, saving network bandwidth. The interaction with Active Directory is also important: WDS can integrate with AD to provide secure client authentication and authorization.
Common Issues and Troubleshooting
DHCP not providing PXE options: Ensure option 60 is set to 'PXEClient' or options 66/67 are configured.
TFTP timeouts: Often due to firewalls blocking UDP port 69, or the TFTP server not being reachable.
Boot file not found: Verify the boot file name (e.g., bootmgfw.efi) exists on the TFTP server and the path is correct.
UEFI vs BIOS mismatch: The boot file must match the client's firmware type. UEFI clients require bootmgfw.efi; BIOS clients require bootmgr.exe.
Secure Boot: Some UEFI systems with Secure Boot enabled may reject unsigned boot files. Use Microsoft-signed boot files or disable Secure Boot temporarily.
Client PXE Initialization
When a computer is powered on, the firmware (BIOS/UEFI) initializes hardware and checks the boot order. If PXE boot is enabled and prioritized, the network interface card (NIC) firmware activates. The NIC broadcasts a DHCPDISCOVER packet with option 60 set to 'PXEClient'. This packet is sent to UDP port 67 (DHCP server). The client includes its own MAC address in the chaddr field. The broadcast is limited to the local subnet; if a DHCP relay agent is present, it forwards the request to a remote DHCP server. The client then waits for a DHCPOFFER. The default timeout for DHCP is typically 3 seconds, after which the client may retry up to 3 times before falling back to local boot.
DHCP Server Response
A PXE-aware DHCP server (or proxy) receives the DHCPDISCOVER and responds with a DHCPOFFER that includes an IP address, subnet mask, default gateway, and DNS servers. Additionally, it provides option 66 (TFTP server name) and option 67 (boot file name). The DHCP server may also set option 60 to 'PXEClient' in the response, but this is not required. The client then sends a DHCPREQUEST to accept the offer, and the server confirms with a DHCPACK. The entire DHCP handshake is complete. The client now has an IP address and knows the location of the boot file. The IP address is typically leased for a short duration (e.g., 15 minutes) since the client will not need it after booting the OS.
TFTP Download of NBP
With the IP address configured, the PXE client initiates a TFTP session to the server specified in option 66. It requests the file specified in option 67 (e.g., `bootmgfw.efi`). TFTP uses UDP port 69. The transfer starts with a read request (RRQ) packet. The server responds with data packets (typically 512 bytes each, unless block size negotiation is used). The client sends an acknowledgment (ACK) for each packet. This stop-and-wait protocol is slow but simple. Once all packets are received, the client has the Network Bootstrap Program (NBP) in memory. The TFTP session ends. The total download time depends on file size and network latency; a typical NBP is about 2-4 MB.
NBP Execution and Boot Menu
The client executes the NBP (e.g., `bootmgfw.efi`). This program is a minimal boot loader that understands the Boot Configuration Data (BCD) format. It reads the BCD store, which may be located on the TFTP server or embedded in the NBP. The BCD defines boot options, including the location of a Windows PE boot image (boot.wim). The NBP presents a boot menu to the user, allowing selection of an OS image or other tools. This menu can be customized in WDS. If no user input is received, a default selection is used after a timeout (typically 30 seconds). The menu is displayed using the UEFI graphics output protocol or BIOS text mode.
Download and Boot Windows PE
The selected boot option points to a Windows PE image (boot.wim) on the TFTP server (or via HTTP if configured). The NBP downloads this image using TFTP (or HTTP) and loads it into memory. Windows PE is a lightweight version of Windows that provides a command prompt and networking capabilities. Once loaded, Windows PE starts and runs a setup script (unattend.xml) that automates the OS installation. For WDS, the setup contacts the WDS server to obtain the install image (install.wim) and apply it to the local disk. After the install image is applied, the computer reboots into the newly installed OS. The PXE boot process is complete.
In enterprise environments, PXE boot and WDS are indispensable for mass deployment. Consider a large university with 500 new computers arriving each semester. Manually installing Windows on each machine would take days. Instead, the IT team configures a WDS server on the network. They create a single boot image with Windows PE and an unattended answer file that automatically partitions the disk, applies the Windows image, and joins the domain. The computers are set to PXE boot first. As each machine boots, it receives an IP from DHCP, downloads the boot image via TFTP, and starts the automated installation. The entire process takes about 20 minutes per machine, and multiple machines can be installed simultaneously. The WDS server can use multicast to send the image once to all clients, reducing network congestion.
Another scenario: a government agency uses PXE boot for diskless workstations. These machines have no local storage; they boot entirely from the network. Each time they start, they PXE boot into a virtual desktop image stored on a central server. This provides enhanced security because no data resides on the client. The PXE boot process is identical, but the boot image loads a full Windows desktop that runs from memory or mounts a network share. Performance depends on network speed and server load. Administrators must ensure high availability of DHCP and TFTP servers, often using redundant servers.
Common issues in production: DHCP scopes running out of IP addresses, especially during large deployments. TFTP timeouts due to packet loss or firewalls blocking UDP 69. Misconfigured options 66/67 pointing to wrong servers or filenames. UEFI and BIOS mixed environments require separate boot images and careful configuration. Also, Secure Boot can block unsigned boot loaders; using Microsoft-signed images is essential. Network engineers often use packet captures (e.g., Wireshark) to diagnose PXE boot failures by filtering for DHCP and TFTP traffic.
For the CompTIA A+ 220-1102 exam, Objective 1.1 (Configure and install Windows operating system features) includes network-based installations using PXE and WDS. You should know the purpose of PXE (network boot without local media), the role of DHCP (providing IP and boot server info), and TFTP (transferring boot files). The exam tests your ability to identify prerequisites and steps.
Common wrong answers: 1. 'PXE requires a hard drive.' Wrong—PXE is precisely for booting without a hard drive. 2. 'PXE uses HTTP to download the boot file.' The exam emphasizes TFTP as the protocol for the initial boot file transfer, though modern implementations may use HTTP. Stick with TFTP for the exam. 3. 'DHCP option 66 is the boot file name.' No, option 66 is the TFTP server; option 67 is the boot file name. 4. 'WDS is only for Windows 10.' WDS can deploy any Windows OS that has boot and install images.
Specific numbers/terms: Option 66 (TFTP server name), Option 67 (Bootfile name), TFTP port UDP 69, DHCP port UDP 67/68, and the term 'Network Bootstrap Program' (NBP). The exam may ask which protocol is used to download the initial boot file (TFTP). Edge case: If a client fails to PXE boot, it will typically fall back to the next boot device (e.g., hard drive). Another edge: Secure Boot enabled may prevent unsigned boot files from loading.
To eliminate wrong answers, remember the underlying mechanism: PXE boot is a multi-step process starting with DHCP (IP assignment), then TFTP (file transfer), then execution. Any answer that skips a step or uses the wrong protocol is incorrect. Also, note that PXE is not limited to Windows; it can boot Linux and other OSes, but the exam focuses on Windows via WDS.
PXE boot allows a computer to boot from the network without a local storage device.
The PXE boot process uses DHCP to obtain an IP address and learn the TFTP server location (option 66) and boot file name (option 67).
TFTP (UDP port 69) is used to download the Network Bootstrap Program (NBP) from the server.
Windows Deployment Services (WDS) integrates DHCP, TFTP, and a file server to deploy Windows OS images.
UEFI-based systems use bootmgfw.efi; BIOS-based systems use bootmgr.exe as the NBP.
Secure Boot may prevent unsigned boot loaders from loading; use Microsoft-signed images.
PXE boot can be used for diskless workstations and automated OS deployment in enterprise environments.
These come up on the exam all the time. Here's how to tell them apart.
PXE Boot (Legacy BIOS)
Uses bootmgr.exe as the NBP
Boot process uses BIOS interrupts
Limited to 2TB disk support
No Secure Boot support
PXE client uses UNDI driver
PXE Boot (UEFI)
Uses bootmgfw.efi as the NBP
Uses UEFI protocols for network and file I/O
Supports GPT and disks larger than 2TB
Supports Secure Boot (requires signed boot files)
PXE client uses UEFI network stack
Mistake
PXE boot requires a DHCP server on the same subnet.
Correct
PXE boot works across subnets using DHCP relay agents (IP helpers). The DHCPDISCOVER broadcast is forwarded to the DHCP server by the relay, which then sends a unicast reply back. This is standard in routed networks.
Mistake
TFTP is used for the entire OS installation.
Correct
TFTP is only used to download the initial boot loader (NBP) and possibly the Windows PE image. The actual install image (Windows OS) is typically transferred via HTTP or SMB from the WDS server, as TFTP is too slow for large files.
Mistake
PXE boot only works with Windows.
Correct
PXE is a vendor-neutral standard. It can boot any OS that has a compliant NBP, including Linux (e.g., using pxelinux.0) and various diagnostic tools. The CompTIA A+ exam focuses on Windows, but the technology is universal.
Mistake
Option 66 and 67 are always required for PXE boot.
Correct
If the DHCP server is also the PXE server (like WDS integrated with DHCP), it can inject the necessary options automatically. In some setups, a proxy DHCP server provides these options without modifying the main DHCP server. Also, the client can use a broadcast-based discovery for the boot server if options are missing, but this is less common.
Mistake
PXE boot works with any network card without configuration.
Correct
The NIC must support PXE firmware (most do), but the system BIOS/UEFI must have network boot enabled and set as the first boot device. Additionally, the network must allow DHCP and TFTP traffic (no firewall blocking).
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
PXE boot is a specific standard for network boot defined by Intel. Network boot is a broader term that can include other methods like BOOTP or HTTP boot. In the context of CompTIA A+, PXE is the standard used. PXE uses DHCP and TFTP, while other network boot methods may use different protocols. For the exam, consider PXE and network boot as synonymous.
No, PXE boot can work with any TFTP server and DHCP server that provide the necessary options. WDS is a Microsoft product that simplifies the process for Windows deployments, providing a management console and additional features like multicast. For Linux, you might use a TFTP server with pxelinux.0.
DHCP uses UDP ports 67 (server) and 68 (client). TFTP uses UDP port 69. If using HTTP for later stages, port 80 or 443 may also be needed. Ensure firewalls allow these ports between the client and servers.
Technically, PXE is designed for wired Ethernet because the firmware network stack typically only supports wired NICs. Some UEFI implementations support wireless PXE, but it is rare and not covered on the A+ exam. Assume PXE requires a wired connection.
A DHCP proxy server is used when you cannot modify the existing DHCP server. It listens for DHCPDISCOVER packets with option 60 set to 'PXEClient' and responds with the PXE-specific options (66 and 67) while the main DHCP server provides the IP address. This avoids reconfiguring the production DHCP server.
Check the following: 1) Is PXE boot enabled in BIOS/UEFI? 2) Is the network cable connected? 3) Can the client get an IP address? 4) Are DHCP options 66 and 67 configured correctly? 5) Is the TFTP server reachable and the boot file present? 6) Check firewall rules for UDP 67-69. Use packet capture to see DHCP and TFTP traffic.
A boot image (boot.wim) is a Windows PE image that boots the client and provides a minimal environment to run the setup. An install image (install.wim) contains the actual Windows operating system to be deployed. The boot image is downloaded first via TFTP, then the install image is applied from the WDS server.
You've just covered PXE Boot and Windows Deployment Services — now see how well it sticks with free 220-1102 practice questions. Full explanations included, no account needed.
Done with this chapter?