thestig220 Posted October 11, 2016 Report post Posted October 11, 2016 (edited) I am new to SCCM, and I am not the guy who set this environment up. Last Friday, our sccm deployment method decided to take a crap. We have a distribution point with PXE configured in 2007. At first, WDS would not start and everything in the SMSBoot file was missing. Here is what I tried. -Remove PXE from DP -Remove WDS role from DP -Delete temp files -Delete remote-install file -reinstall WDS (I NEVER configured) -Reinstall the PXE role from SCCM to the DP. I get an install complete. -create new boot image and readvertised to systems. I have done this three times already and no avail. The DHCP server is on a separate server and only has option 66 configured; That is it, that is how it has worked for 5 years. I really need help with this issue, I have already spent so many hours trying to figure this out and I am completely out of brain power. Edited October 11, 2016 by thestig220 Quote Share this post Link to post Share on other sites More sharing options...
Hobbs155 Posted October 11, 2016 Report post Posted October 11, 2016 Have you checked the Task Sequence is set to use the new boot wim and the task sequence has been deployed to a collection? Quote Share this post Link to post Share on other sites More sharing options...
thestig220 Posted October 12, 2016 Report post Posted October 12, 2016 new task sequence, new boot image on dist, everything. pxe-e53 error. Quote Share this post Link to post Share on other sites More sharing options...
mike.terrill Posted October 13, 2016 Report post Posted October 13, 2016 Just a guess, but it is possible that IIS is looking for a different version of Windows BITS Extensions than what is installed. Check your application.config file and then compare that to the file version in the Global Assembly Cache. This can happen if you upgraded your operating system (like from Server 2012 to Server 2012 R2). Quote Share this post Link to post Share on other sites More sharing options...
