Windows 10: MDT 2013 Update 2013 Build 8298 - Sysprep "disconnects" NIC

Hello Guys


We have upgraded our MDT 2013 to Update 1 build 8298.


And we have quite a few issues that we didn't have before.


We have some pretty simple task sequences we use to build images, one for each OS. Currently
Windows 7x64, Windows 8.1x64 and Windows 10x64. Each os has a separate virtual machine in our VMware environment. We don't capture the image in MDT since our deployment system requires and older WinPE to run (Capasystems.com).


I pick the Syspreb task so it does what needs to be done at the end of the build. Shutdown the machine when it's done, pxe boot into capa and then proceed to capture the image.


This is pretty basic and has worked in the past.


After the upgrade I boot from the litetouch ISO like we normally do and using a VMxnet3 driver make the connection to the share and this runs smoothly all the way to the sysprep part.


When the machine is done syspreping it completely "drops all network connections" and the build "fails". See the attached pictures.


I'm having a hard time figuring out why this happens - Any ideas?


Tried with different drivers, old and new. Even tried running it on hyper-v but it yields the same results. Every task sequence was built from scratch since the format part was changed.




Windows 7 - same for Windows 10





:)

 

Importing Win10 into MDT 2013

I was unable to import it using the install that was available for free download. However, I got it working with the download that I got directly from the volume licensing center.

Still having issues capturing an image with it though. Getting a failure after running Litetouch, just before the sysprep phase. I read somewhere that MDT 2013 update 1 preview isn't working with later builds of the tech preview, or the final build. Assuming
we have to wait for another MDT update.

 

Windows 10 1709 sysprep fail

Unfortunately this did not work for me.

 

I made an account to reply back with "Me too!!111".

Our MDT setup has been upgraded though the years from MDT 2008, 2010, 2012, to 2013, update1 and this latest 8298 build and we are experiencing the same issue.

Our MDT WinPE is version 10 with a custom boot that launches an autoIT login screen authenticating the user against AD and pulling the computer name via vbscript LDAP lookup. Authentication changes what a person can/cannot see for deployment. We use the MDT image in our WDS PXE boot.

When using a stock sysprep and capture against a MSDN "Windows 10 Enterprise (x64) - DVD (English)" SHA1 30AD1CDF5D0670F12788005131E24862F6AB8AAB it destroys the system during sysprep due to the generalize flag. I have disabled the tilemodelsvc, updated the system via our WSUS server nether prevent the generalize flag from breaking the guest. I see the network become unavailable almost immediately.

We have tried it in our ESX 5.5 U3, Virtualbox, Physical E6530, E7450. All break at the same spot causing the LTICopyScripts.wsf to not be found (aka network share is lost, drivers are not found, and the system as a whole is butchered). This screen shot is me attempting to load device manager after the deployment error (just before I click the error message about not finding LTICopyScripts.wsf)





I have posted an issue to MS MDT feedback (ID 1803004). Login and provide any additional feedback. It's not bad now that this doesn't work for us since we are not really far behind on drivers but each month and more patches get released my team lags on deploying 10. We are using the deployment tasks to rip out the items we don't need but it would be nice to not have to do it each time.