[sccm 2012] PXE-T01: The specified file was not found. PXE-E3B: TFTP Error - File not found

[Garacesh]

I updated to the latest SDK and removed the old boot images like a tool thinking I could just make new ones.

Can you make new ones? Can you heck! At least, clearly not in any kind of user-friendly manner...

 

SMSPXE.log reads the following:

The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!>

http://SCCM-server.domain.]LOG]!>

http://SCCM-server.domain.]LOG]!>

]LOG]!>

Which doesn't help because it doesn't tell me what file it's looking for that it can't find. So no leads there..

 

Needless to say I'm a bit off with both SCCM for not being straightforward, and more so with myself for getting stuck in this mess in the first place.

 

As the internet suggests, I've disabled PXE in SCCM, removed the ADK, PXE Add-on and the WDS role from the server, rebooted it, renamed %windir%/temp to temp.old, renamed RemoteInstall to RemoteInstall.old, re-enabled the WDS role, re-installed ADK/PXE Add-on, then re-enabled PXE in SCCM and I'm just back where I started.. Still nothing.

 

I did manage to generate 2 new boot images (one x86 and one x64) from the files stored in \\Server\sms_sitecode\OSD\boot\i386\boot.wim and \...\x64\boot.wim and I've set the task sequences I have to use the x86 boot image generated this way (since they were all set to use the previous x86 boot image before I went and mucked it all up...), then they were the wrong version so I managed to re-distribute those with the "Reload this boot image with the current Windows PE version from the Windows ADK" option ticked (which I guess I should've done in the first place, huh?) so that their version matched the Windows ADK version (10.1.17763.1) but I'm still getting the same errors.

 

At a loss for ideas now.

Edited October 4, 2018 by Garacesh

[Garacesh]

A solution has been found!

 

The ADK creates new deployment images as C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim and \\...\x86\en-us\winpe.wim

 

I copied those across to \\server\SMS_sitecode\OSD\boot\x86\winpe.wim and \..\OSD\boot\amd64\winpe.wim and imported them into SCCM, which resulted in a pair of boot images with the correct version (10.0.17763.1) straight from the get-go. Distributing them to the Distribution Point, and ticking the Deploy this boot image from the PXE-enabled distribution point got everything up and running again.

 

Leaving this thread here in the hopes that it might help someone in future

Edited October 4, 2018 by Garacesh

[RiverliteNathan]

There is also a nice easy powershell script that will regenerate the boot images from the ADK if you ever need a second option. See https://gallery.technet.microsoft.com/RegenerateBootImageWinPE10-f508f1e4#content