In this video guide, we cover what’s actually happening on a client during OSD in Configuration Manager. This deep dive guide covers what is going on and how to troubleshoot different stages of an OSD task sequence failure on the client. This should be an excellent resource for seasoned ConfigMgr admin’s as well non-ConfigMgr admin’s who want to understand how to troubleshoot OSD errors in SCCM. Topic’s in this session include wpeinit.log, winpeshl.ini, SMSTS.LOG, DiskPartScript.txt, unattend.xml, DISM, SetupACT, NetSetup.LOG, AppEnforce.log, WUAHandler.log, UpdatesDeployment.log, CAS.log and many more components involved in OSD!
Thanks so much for your excellent videos. Re: the install updates step in the task sequence. The option (required or available) has to match the deployment type of the software update group to ‘Unknown computers’? And therefore does it really matter if you use available or required when deploying to ‘Unknown computers’ for the purposes of installing updates during OSD as long as both parts match?
Where Can I check the Memory required to perform bare metal deployment in SCCM Task Sequence. Which Steps validate it and TaskSequence Variable located in which place?
I'm Justin Chalfant! I'm the founder of
Thanks so much for your excellent videos. Re: the install updates step in the task sequence. The option (required or available) has to match the deployment type of the software update group to ‘Unknown computers’? And therefore does it really matter if you use available or required when deploying to ‘Unknown computers’ for the purposes of installing updates during OSD as long as both parts match?
Up to you.
I thought so. Just that the terminology in this instance is a little misleading. ‘Available’ usually means optional but in this case its mandatory.
Where Can I check the Memory required to perform bare metal deployment in SCCM Task Sequence. Which Steps validate it and TaskSequence Variable located in which place?
Sorry for the delay did you figure this out?