What is that issue; how it can be fixed:

To test, we added a bare metal client to the database, placed the resultant client record within a collection, and advertised a simple image deployment task sequence. When booting the pc, we get an immediate “PXE-T01: File not found”. Now, since we no longer configure DHCP options to point to the PXE server, nor to tell the PXE client which boot filename to acquire, exactly what file does the TFTP daemon use when responding to a PXE request.  The smspxe.log reflects the fact that the PXE client is communicating with the service and requesting a boot file.

10.10.1.29 is the SCCM server

10.10.1.35 is the DHCP server

10.10.1.146 is the PXE client

So far, I have completely removed the PSP/WDS services, restarted the server, reinstalled WDS/PSP, and again restarted the server.

Solution1:

On Server which is hosting WDS service

1. Stop the WDS service.
2. Delete C:\WINDOWS\TEMP\PXEBootFiles\Windows
3. Start the WDS service
4. Check smspxe.log again and see if <![LOG[Unable to delete directory… exists.

This solved above issues, and my folders in …\SMSBoot\x86 …\SMSBoot\x64 and …\SMSBoot\ia64 were populated with the needed files.

Solution 2:

1. Uninstall PSP role from SCCM console
2. Stop the WDS service
3. Delete C:\WINDOWS\TEMP\PXEBootFiles\Windows
4. Start the WDS service.
5. Install PSP role

This entry was posted on Friday, May 9th, 2014 at 10:00 am and is filed under Windows FTP. You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.