PXE boot is one of the most common methods used in SCCM/Configuration Manager (ConfigMgr) for Operating System Deployment (OSD). However, administrators often encounter PXE boot failures that prevent task sequences from starting. These issues can stem from DHCP misconfigurations, missing boot images, or distribution point problems. In this guide, we’ll walk through the most frequent PXE errors, explain how to analyze log files such as smspxe.log, and provide step‑by‑step troubleshooting techniques to quickly restore OSD functionality.
If you want to know more about the PXE boot process in the Configuration Manager, then you should start with this Microsoft article. The article explains the PXE boot process in Configuration Manager.
Troubleshooting SCCM OSD PXE Issues
To effectively troubleshoot PXE boot issues in SCCM/Configuration Manager (ConfigMgr/MECM), it’s important to understand the components involved in the PXE process. PXE relies on several elements—such as DHCP configuration, Distribution Points, boot images, and network connectivity—and a failure in any of these can prevent the client from starting the task sequence. By breaking down each component, administrators can quickly pinpoint the root cause and apply the right fix.
1. Verify IP Helper Configuration for PXE Boot
IP helpers are used to forward DHCP broadcast requests to DHCP servers located in different network subnets. By default, a DHCP request generated by a client computer is a broadcast that cannot travel outside its local subnet or VLAN. To enable PXE boot across multiple subnets, IP helpers must be configured on the routers so that DHCP broadcasts are forwarded to the DHCP server and the PXE‑enabled Distribution Point (DP).
If you suspect an issue with IP helper configuration, work with your organization’s network team to validate that IP helpers are correctly forwarding DHCP requests to both the DHCP server and the PXE‑enabled DP.
To configure IP helpers on routers, you will need the following details:
- Source VLAN/Subnet used for PXE‑based OS deployment
- IP address of the PXE‑enabled Distribution Point
- DHCP server IP address
2. DHCP Discovery Troubleshooting for PXE Boot in SCCM
If the PXE boot process fails before Windows PE (WinPE) loads, the client will display a PXE error code on the screen. Below are some of the common error messages you may encounter during SCCM/ConfigMgr OSD deployments.
PXE-E51: No DHCP or proxyDHCP offers were received
The PXE‑E51 error indicates that the PXE client did not receive a response to its DHCPDISCOVER message. This failure usually points to a problem with DHCP availability or network forwarding.
Possible causes include:
- No DHCP server available in the network, or the DHCP service is down.
- The DHCP server is not configured to respond to PXE client requests.
- IP helpers are not configured on routers to forward DHCPDISCOVER broadcasts to the DHCP server or PXE‑enabled Distribution Point in a different subnet.
PXE-E52: proxyDHCP offers were received. No DHCP offers were received
The PXE‑E52 error indicates that the PXE client has received one or more proxyDHCP offers but did not receive a valid DHCP offer. This situation typically points to DHCP availability or configuration issues in the environment.
Possible causes include:
- No DHCP server available in the network, or the DHCP service is down.
- The DHCP server is not configured to respond to PXE client requests.
- IP helpers are not configured on routers to forward DHCPDISCOVER broadcasts to the DHCP server or PXE‑enabled Distribution Point in a different subnet.
PXE-E53: No boot filename received
The PXE‑E53 error occurs when the PXE client receives a reply to its DHCPDISCOVER message but the boot file information is missing. Without the boot file details, the PXE boot process cannot continue into Windows PE (WinPE).
Possible causes include:
- DHCP Options 66 and 67 are not properly configured to provide the PXE server and boot file name details. This applies if you are using a DHCP server to supply PXE boot information to clients.
- IP helpers are not configured on routers to forward DHCPDISCOVER broadcasts to the PXE server in a different subnet.
3. PXE Boot Stuck at “Start PXE over IPv4/IPv6
This is another common issue encountered during SCCM/ConfigMgr Operating System Deployment (OSD) using PXE boot. When initiating a PXE‑based image deployment, the client may display the “Start PXE over IPv4” or “Start PXE over IPv6” message and then remain stuck on that screen without progressing further.
Understanding why PXE boot hangs at this stage is critical for effective SCCM PXE troubleshooting, as it often points to problems with network configuration, DHCP/IP helpers, or boot image availability.
Cause:
The PXE boot request may be rejected by SCCM/ConfigMgr due to one of the following reasons:
- The Task Sequence is deployed only to Unknown Computers. As a result, any PXE boot request from a known device (already present in SCCM) will be rejected.
- The device was previously imaged using SCCM, and its record already exists in the SCCM database.
- A USB‑to‑Ethernet adapter is being reused across multiple devices, and the adapter’s MAC address is already present in the SCCM database, causing conflicts.
You can see the following entries in the SMSPXE.LOG file on the PXE-enabled distribution Point for the device you are trying to PXE boot. The location of the smspxe.log file on the PXE-enabled distribution point is \\DP server\SMS_DP$\SMS\Logs
D3:15:C2:5C:6A:C7, X023984C-15DB-99Z2-A25D-F43DB2F4X123: Device is in the database.
D3:15:C2:5C:6A:C7, X023984C-15DB-99Z2-A25D-F43DB2F4X123: no advertisements found
Solution:
The device record already exists in SCCM/ConfigMgr. To resolve this, delete the machine entry from the SCCM database. You can locate the record using the Device Serial Number, MAC address, or SMBIOS GUID. Note that the serial number will only be available if the client was previously active and had submitted hardware inventory to SCCM.
Find the device in SCCM with the MAC address:
Find the Device in SCCM with the SMBIOS GUID / Device ID:
Using a USB‑to‑Ethernet Adapter for PXE Boot – Whitelist USB to Ethernet Adapter
If you are using a single USB‑to‑Ethernet adapter to build multiple devices via PXE boot, the MAC address of the adapter must be whitelisted in SCCM/ConfigMgr. Without whitelisting, SCCM may reject PXE requests because the same MAC address is detected across different machines.
To whitelist the adapter’s MAC address in SCCM:
- Navigate to Hierarchy Settings Properties.
- Go to the Client Approval and Conflicting Records tab.
- Add the MAC address under Duplicate Hardware Identifiers.
This will allow SCCM to ignore the hardware ID of the devices for the purpose of PXE boot and client registration.
✅ Best Practices Checklist for PXE Boot in SCCM
- DHCP & IP Helpers
- Ensure DHCP services are running and properly configured.
- Configure IP helpers on routers to forward DHCPDISCOVER requests to PXE servers across subnets.
- Task Sequence Deployment
- Deploy Task Sequences to the correct device collections (not just Unknown Computers).
- Remove stale or duplicate device records from the SCCM database.
- Device Identifiers
- Use MAC address or SMBIOS GUID for reliable device identification.
- Whitelist MAC addresses of USB‑to‑Ethernet adapters if reused across multiple PXE deployments.
- Boot Image & Drivers
- Verify NIC drivers are included in the boot image.
- Confirm boot images are distributed to PXE‑enabled Distribution Points.
- Logs & Monitoring
- Review SMSPXE.LOG on the PXE‑enabled DP for request/response details.
- Check smspxe.log for rejection messages, duplicate identifiers, or missing boot file info.
- General Hygiene
- Document whitelisted adapters and device records for future reference.
- Regularly audit SCCM collections and PXE configurations to prevent conflicts.
Conclusion
PXE boot issues in SCCM/ConfigMgr OSD deployments often stem from misconfigured DHCP options, missing IP helper settings, or duplicate device records in the database. By systematically verifying DHCP services, IP helper configurations, and device identifiers, administrators can quickly isolate and resolve most PXE errors. Leveraging tools like SMSPXE.LOG for detailed diagnostics and applying best practices such as whitelisting USB‑to‑Ethernet adapter MAC addresses ensures smoother, more reliable PXE‑based imaging. With these troubleshooting steps in place, you can minimize deployment failures and maintain a consistent, scalable OSD workflow across your environment.
Related Posts:
- SCCM Application Deployment Failed with Error 0x87d01106 | ConfigMgr
- SCCM Client Installation Failed With Error Code 0x87d00215
- PXE-E99: Unexpected network error – SCCM OSD
- Configuration Manager OSD task sequence fails with error code 0x80004005
- MECM OSD Task Sequence Failed with Error 0x80072EE7
- SCCM Client Push Installation Failed with Error 0x800706ba
- Failed to Add Update Source for WUAgent of type (2) and id ({ID). Error = 0x80004005
- SCCM OSD – Domain Join Failed with Error code 0x54b on HP Elitebook 840 G8
- ccmsetup failed with error code 0x87d00227
- Fix Application Deployment error 0x87d00213 in ConfigMgr
- CMG Connection Point Status Disconnected | SCCM | ConfigMgr
- CMG Setup – Subscription ID drop down not populating
- CMG Setup – Error when granting Contributor permission to the Azure AD app
- Failed to connect with DP – Error Code 0x8004100e | ConfigMgr | SCCM
- SCCM Client Installation Failed with error 0x87d0027e
- ConfigMgr OSD – PXE Troubleshooting
- SCCM WSUS sync error – Sync Failed – WSUS server not configured
- SCCM Software Distribution Troubleshooting
Subscribe to Techuisitive Newsletter
Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.