Not sure why you're losing your NIC somewhere in the process. What is the virtual NIC you used in the base Win 10 image? Did you install VMware Tools in that image? My answer is to use some other imaging system. Microsoft Corporation Microsoft Deployment Toolkit 2013 star 4.9.
I have verified the Deployment share has the latest updated driver and that the deployment share is updated, but it still keeps failing there.Īny of you run into this issue? If so, how did you get around it? Upon further investigation, there is no longer a network adapter installed (driver removed by sysprep presumably). We have no issues with capturing an updated Windows 8.1 image with the exact same VM specs and applications installed, however when we try to capture the Windows 10 VM, we open the deployment share, run the Litetouch Script, choose to capture the machine image and put it in the capture folder on the deployment share, it starts to do it's stuff, goes through its execution of Sysprep, but then it errors out saying it cannot find the f file (and gives the file path to the file on the deployment share). Background, We have MDT2013 Update 1 running on a Win 2k8 Server with WDS services and the windows 10 AIK. So I have a perplexing issue with not being able to complete a Windows 10 VM image capture.
0 kommentar(er)
