PXE issues

Recreate the PXE service point to troubleshoot a file not found PXE error. You can also use the Reboot to PXE / USB custom action to circumvent a problem that can occur during multiple rebooting of a target system.

About this task
If you notice the following error in the log file, troubleshoot using these common PXE issues:
File not found PXE error #. 

Assuming that the PXE service was operational at one time usually means that changes to a boot image were not distributed to the PXE service distribution points. Distributing boot image changes is described in Updating the distribution points for a boot image.

Also, it could be there is not a valid advertisement for this machine. Creating an advertisement is described in Advertising task sequences.

You must also add the target server MAC address and GUID to the Configuration Manager database, as described in Importing the servers into the Configuration Manager database.

PXE-initiated deployments require a Pre-boot Execution Environment (PXE) service point role (and some NTFS-formatted disk space), a DHCP server, Windows® Deployment Services (WDS), and a firewall port configuration. Using DHCP and WDS on the same machine requires you to configure WDS to listen on a port other than port 67. See Technet: Planning for PXE Initiated Operating System Deployments for more information.

If there are difficulties in getting the PXE service to work from the beginning, check that Windows Deployment Services (WDS) is installed and that it is correctly configured for the environment.

If the DHCP server is on the same server as WDS, make sure that DHCP option 60 is enabled. In some cases it might be necessary to restart the DHCP server.

If the prerequisites are met, use the following procedure to recreate the PXE service point.

  1. From the console, remove the PXE service role.
  2. Check the Program Files\Microsoft Configuration Manager\Logs\PXEsetup.log to verify that the role is removed successfully.
  3. Remove the Windows Deployment Service.
  4. Reboot the Configuration Manager site server, if WDS was installed on the site server.
  5. Reinstall WDS but do not configure it.

    It is not necessary to import images. However, make sure that WDS is installed correctly.

  6. Assuming DHCP and WDS are installed on the Configuration Manager server, make sure that DHCP Option 60 is enabled and choose Don’t listen on port 67.
  7. Reinstall the PXE service role.
  8. Check the PXEsetup.log to verify that the role was installed successfully.
  9. Update the PXE distribution points for the boot images now that the new role is installed.
  10. The target client should now be able to PXE boot to the Configuration Manager server.