graumachine Posted November 15, 2016 Report post Posted November 15, 2016 Hi there, Can anyone confirm that it is possible to succesfully deploy Windows 10 Professional via Config Manager? I have tried a lot of different stuff, but Task Sequence keeps failing after the first reboot, before the client is installed. Windows 10 Enterprise works flawlessly. I have two SCCM setups (2012 SP2 and 1606), both behave the same. Is there a hidden requirement somewhere for Enterprise version? //Peter Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted November 15, 2016 Report post Posted November 15, 2016 Windows 10 pro is fully supported. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted November 15, 2016 Report post Posted November 15, 2016 hi Peter, please post the smsts.log file so we can determine why it failed, first thoughts would be to verify the cdkey and/or unattend.xml references Quote Share this post Link to post Share on other sites More sharing options...
graumachine Posted November 16, 2016 Report post Posted November 16, 2016 Thanks for your replies. Good to know that Pro is supported so I can justify the effort to continue my troubleshooting. :-) SMSTS.log is attached. Currently I'm trying to deploy on SCCM 2012 SP2 with MDT 2013 and ADK10. Task sequence is via MDT, almost just next, next, finish. Quote Share this post Link to post Share on other sites More sharing options...
graumachine Posted November 16, 2016 Report post Posted November 16, 2016 I could add that I've been through quite an ordeal trying to frind the proper installation media, finally ending up with media from our Microsoft partner agreement. Weird thing is that the same task sequence works wonderfully with an Enterprise image, but if I replace the OS with Pro, the task sequence won't finish properly. No difference if the Pro image is from partner source or a converted .ESD. I don't see any errors as such in smsts.log. But _SMSTaskSequence folder is left on C:\ and the Config Manager client never gets installed. Quote Share this post Link to post Share on other sites More sharing options...