Skip to main content

PXE issues

To troubleshoot a "File not found PXE error," re-create the PXE service point. You can also use the Reboot to PXE/USB custom action to circumvent a problem that might occur after rebooting a target system multiple times.

About this task

If the following error is displayed in the log file, it might be related to one of several common PXE issues:
File not found PXE error #.
Refer to the information that follows for possible solutions.

If the PXE service was operational at one time, the issue might be caused by changes to a boot image that were not distributed to the PXE service distribution points.

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

You must also add the target server MAC address and GUID to the Configuration Manager database.

PXE-initiated deployments require a Preboot 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 server requires you to configure WDS to listen on a port other than port 67. See Microsoft System Center – Planning for PXE Initiated Operating System Deployments webpage for more information.

If you have problems 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 error still exists, try the following actions:
  1. Stop the Windows WDS.
  2. Either delete or rename the windows\Temp folder and create a new windows\Temp folder.
  3. Restart the WDS.

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

If the prerequisites are met, use the following procedure to re-create the PXE service point.

Procedure

  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 WDS.
  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 file 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.

The target client should now be able to PXE boot to the Configuration Manager server.