Windows 10: MDT 2013 Task Sequence hangs second partition on diskpart on VMware

Hi,
I'm using MDT and trying to install Windows 10 1909 on a VMware machine.
During WinPE, Task Sequence hangs when creating second partition (OS). Pressing F8 to debug doesn't work.
The VM is set to Legacy, not EFI.
The Task Sequence works on a physical machine. It used to work and don't understand why it doesn't work anymore.
Any idea how to debug this ?
Thank you very much for your comments.
Best Regards,
Jo

:)

 

Can the Windows 10 Pro free upgrade be automated using a MDT task sequence?

Can the Windows 10 Pro free upgrade be automated using a MDT task sequence? I have a number of customers who are using Windows 8 Pro and have a volume activation key. They want to take advantage of the Windows 10 Pro free upgrade for their end users and
want the process automated using a MDT task sequence

 

MDT 2013 Update 2 - Imaging Windows 10 Pro x64

Hi Guys,

I am completely stumped why MDT 2013 will not deploy a basic image of windows 10 from the source files I have added. My deployment share works perfectly fine for windows 7.

So I have done the following:

• Imported Windows 10 pro x64.iso , with source files (downloaded from MVLMS)
• Created a "standard Task Sequence" with default settings (pointing to this image)
• Created a selection profile for the windows 10 drivers on the device (known to be working)

The task sequence gets roughly 50% way through and then throws an error "the windows 10 installation failed to complete" this error occurs shortly after a message that states devices ready 100%.

The logs indicate that it's trying to run a command that can only be run within a windows environment, however that is the extent of the error recorded.

Thanks

Matt

 

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