Windows 10 Edu Capturing in SCCM

[Stringent]

After punting for Windows 10 build 1607 on our new machines, I installed and configured Windows 10 Edu on it, installed drivers and software required. Made sure SCCM was up to date (version 1606) and made new Capture Media. Took the new PC off the domain, enabled local admin account, no password, removed any profiles off the machine and ran the created CD. Progress bars go through fine, then just as the PC is about to reboot after sysprepping I get a BSOD (WHEA UNCORRECTABLE ERROR) and the machine reboots. It doesn't go into Windows PE and continue the capture process. It is using Secure Boot on the BIOS. Disable and use legacy boot instead?

 

I've looked through error logs, and can't find anything obvious as to why its doing this. Any pointers/suggestions? Its an HP Pro 400 All-in-One PC. My gut is thats its driver related ... But do I just uninstall them and try sysprepping again?

Edited August 30, 2016 by Stringent

[Arthur]

Any pointers/suggestions?

Are you able to create a VM and then image that?

[Stringent]

I am actually trying that now. Using VMWare Workstation, so will see if that grabs up OK. One step at a time, then see if I can get it to deploy correctly, to the correct partition.

[snagrat]

What ADK you have on SCCM as there is a problem with 1511 and capturing.

 

Ensure ADK is also 1607 version

[Stringent]

Hi Snagrat, Oh forgot about that! So much else going on here at the moment! I've got version 10.1.10586.0 which was done pre 1607 ... So I'll also try that. Still compiling my VM image as well as a backup.

[Stringent]

Looks like the VM image is capturing ...

 

It rebooted into WindowsPE and then I get the Error 0x80220014.

 

I just noticed that the Boot Images are still on the previous version despite updating the ADK. Updating the distribution point gives an error as well ... So looks like I'll have to update the boot images manually.

 

Is it worth applying Hotfix 3143760 on my Configuration Manager as well? I know its specifically for 1511 fixing network issues as Snagrat said, but as I'm on SCCM 1606, surely that would have been included?!

 

Sigh. Seems like all this advancement is causing a lot of headaches. Too much, too young, too fast ...

[Homer]

Personally mate I find it easier capturing in MDT and then using images in SCCM - much less headache

 

Obviously only of use to you if you have MDT set up too

[Stringent]

Hey Homer (saying that is just fab btw, even said with a Moe voice in my head!) thanks for the suggestion, if this fails then I'll probably look into it. Having created a new capture media from the 1607 ADK my VM machine has rebooted and looks like its capturing ... So thats progress on one level! Just going to try the capture media in the new actual machine I built and see what happens.

 

Thanks all for your support so far. I work in a secondary school, we used to have more than one Network Manager, but due to cuts, its now just me managing ... Well everything. From our VMWare System, to Exchange, SCCM, support etc etc and now a new build to deploy with the switching infrastructure ... Its all very crazy. So to have some sane voices just reminding me of other things is appreciated! I'll also try to help others where I can.

[Stringent]

Well capturing the physical machine just isn't happening. It goes though the Sysprep and just as its about to reboot, BSOD. No drivers, didn't even run any fancy scripts to remove the app provisioning (start somewhere and work on!)

 

I have a VM captured so will try and deploy that. Silly question, do I enable legacy boot for the new machine and deploy the image with 2 partitions (old school), or try and deploy just the OS to partition 4 with UFEI boot enabled?

[Arthur]

Silly question, do I enable legacy boot for the new machine and deploy the image with 2 partitions (old school), or try and deploy just the OS to partition 4 with UEFI boot enabled?

Images created on a gen. 1 VM will work on both UEFI and non-UEFI based PCs, whereas images created on a gen. 2 VM will only work on UEFI-based PCs.

 

... there is no point in using UEFI-based VMs for reference images, always use Generation 1, because that image can be deployed to both Generation 1 and Generation 2 VMs, meaning also BIOS-based machines, and UEFI-based machines.

 

Source: https://app.pluralsight.com/library/courses/deploying-windows-10-mdt-configmgr/transcript (Johan Arwidmark)

[Stringent]

Some amazing wins today. So happy. Managed to get Windows 10 to deploy via SCCM to my test machine. Building an image in a VM worked, and even the driver injection worked!

 

Also the new switching arrived for the new build and I get a local link via 10GB Fiber, so heres hoping it will work in the remote building when I hook it all up. Ahh a breather for the weekend.

 

Thanks again guys. I'm off to have a coffee. Nespresso. What else.