We recently upgraded our SCCM 2012 R2 deployment to SCCM 1511 Branch in hopes to begin testing the Windows 10 1511 Branch. During the upgrade we uninstalled the ADK 8.1 and installed ADK 10. So far everything we can think of to test is functional except for the B&C TS. Our Deployment TS work just fine from prior capture images.
I'm also not sure where the SCCM 1511 OSD threads were at so I'm sorry if this is in the wrong area.
Our B&C Task Sequences for Win7 and Win81 have always gone smoothly (outside of our own typos or errors during testing), however, this time around while trying to capture Windows 10 1511 Education the TS fails at the very last step of Capture Reference Machine (which is part of the stock tasks that we don't change). We are capturing using a VM in VMware 5.5 with an E1000 NIC (I've even tried the VMXnet3 without any luck). The boot image being used has been upgraded to v10.0.10586.0 WinPE automatically with our SCCM upgrade and I have verified the additional NIC drivers are still applied to it for the misc NICs in our environment.
We have our Capture TSes deployed as available to our VMs we use to capture and I can manually boot into WinPE via PXE and verify all the required devices (the NIC driver is provided and has an IP, the DISK is shown via diskpart, and the local device TIME is accurate). At this point we receive the wizard to select the available TS provided to this VM.
I select the Win10 Capture TS and it begins... it runs through the tasks we have configured (which is almost 100% stock from the B&C Wizard except for we've added in Office 2016). Everything in the log shows up as return code 0 and I can watch the process go from; pre-downloading WinPE for next boot-up, Prepare Configuration Manager Client, Prepare OS, SysPrep, reboot, loads local version of WinPE... fails.
While it is failed I can press F8 for a command window to debug and I find that the NIC isn't loaded and no IP was given. Which explains why it errors out since it cannot communicate to our SCCM server and save a network copy of the WIM file it will capture.
However, my concern is that during the start of this capture TS it loads a WinPE boot image (PRI0006C) with a working NIC, however, at the last step for "Capture Reference Machine" the WinPE that is downloaded for the final reboot (logs show it downloads PRI0006C and I've witnessed it downloaded the correct WinPE) but during this WinPE bootup it doesn't load a functional NIC.
Is anyone else having this issue with a capture Win 10 TS or what might I be missing as to why booting WinPE initially has a working NIC driver, but during the actual capture WinPE boot it does not?
I'm currently at the point of manually booting back into WinPE (PRI0006C) and running dism.exe to manually capture the partition locally and then manually mapping a drive to our SCCM repository to copy the WIM file up (which is possible because the NIC works when WinPE loads manually via PXE).