nry Posted February 23, 2016 Report post Posted February 23, 2016 My keys are there and I have removed and re-added the PXE from the DP etc. and I still have the same issue...all getting a little frustrating now I have, for the sake of trying, ran through the Windows 10 deployment guide on here, it all went perfectly, no errors etc. but I can't PXE boot from that either, same error as always, 53, missing boot file....and those files are there Quote Share this post Link to post Share on other sites More sharing options...
nry Posted February 23, 2016 Report post Posted February 23, 2016 I noticed you said you removed the MP and re-added it...will this affect anything else such as packages/applications etc.? Thanks, Chris Quote Share this post Link to post Share on other sites More sharing options...
nry Posted February 23, 2016 Report post Posted February 23, 2016 Well....typical SCCM fashion...I repeated the remove PXE then re-add PXE...low and behold it booted and gave me my task sequence choices! It failed which I think ids down to a missing NIC driver which I'll try adding in and see if that sorts it...but one step closer now! Quote Share this post Link to post Share on other sites More sharing options...
nry Posted February 23, 2016 Report post Posted February 23, 2016 And typically I used the new (incorrect!) version of the Windows 10 ADK...so now installing the correct (older!) version...I hit the: Windows PE initialization failed with error code 0x80220014 Error It wasn't the NIC driver... Quote Share this post Link to post Share on other sites More sharing options...
ZeZe Posted February 23, 2016 Report post Posted February 23, 2016 Yes, be careful the ADK you install. Use the RTM Quote Share this post Link to post Share on other sites More sharing options...
nry Posted February 23, 2016 Report post Posted February 23, 2016 And now an error installing the older ADK...SQL Server 2012 Express with an MSI error in C:\Windows\Installer....one step forward, one back Quote Share this post Link to post Share on other sites More sharing options...
nry Posted February 24, 2016 Report post Posted February 24, 2016 Well I think we're all back and running! Refreshed the ADK to the older ADK 10 verison, deleted and re-ran the Windows 10 deployment guide on here and this setup the new boot images etc.... Need to run through the build in full, but my old Win7 deployment kicked off OK and it presented the Windows 10 too... In the end I had to run through this to get PXE back: untick the enable PXE checkbox on the distribution point. Answer yes that you want to remove the Windows Deployment service. remove boot images from your distribution point, then delete %windir%\temp check with server manager. If WDS is done uninstalling there is a reboot pending. Reboot. check if the remoteinstall folder is located on your system. If it fails to delete due to permission issues with the SMSTempBootFiles path, delete all folders except that one and then rename the remoteinstall folder something else. reboot Add the PXE point again by checking the box on the distribution point properties. Check the distrmgr.log and see if the remoteinstall folder reappears.. Replicate the boot image to the DP again. After they land you can try running an F12 and it should roll smoothly. Courtesy of: https://community.spiceworks.com/topic/628123-sccm-2012-r2-pxe-boot-fails-bcd-error-0xc98 1 Quote Share this post Link to post Share on other sites More sharing options...
nry Posted February 25, 2016 Report post Posted February 25, 2016 To confirm it is all back behaving as expected! Win7 x64 deployments working fine, Windows 10 deployment also working but I've not set these up within MDT further yet, just the base no-touch install. Quote Share this post Link to post Share on other sites More sharing options...
