Windows 10: MDT Skips .wim creation step during capture

Hi All,As mentioned in the title;During the MDT Capture wizard every steps works as intended OS installation, apps, sysprep, however it skips the "Create wim" step completely and continues with a shutdown. Any idea how to fix this?I have logs available if needed.MDT is being done within Hyper-V.W10 22H2.iso

:)

 

MDT Stops capturing after 3470 kb

Hi Michael,

Would you be kind enough to share how you got your WIM to capture to network. Was it specific rules you setup in your customsettings.ini or additional steps in your SCCM/MDT Task Sequence?

I'm able to get my offline WIM captured but it stores it local in C:\Statestore. I already tried adding these variables to my customsettings.ini but it does not send the WIM to network share:

Optional Full WIM Backup

ComputerBackupLocation=NETWORK

BackupShare=\\lax-scm-15\offline_wim_backups$

BackupDir=LA_Backups

BackupFile=%OSDComputername%.wim

Thanks

 

Capturing reference Win10 1803 image for MDT 2013


Hi Kari,
This is tremendous job thank you for all your efforts to create this great workflow. I believe many admins are really appreciated to learn this. I have a question if I want to capture a custom image for MDT deployment for Win 10 1803 how these steps are will change it since the TS are taking care of drive partitioning and we have customsettings.ini and bootstrap.ini files created. I try your workflow except to create the partitioning answer file, only i create unattended answer.xml with the OEM settings but it does not work. Also, I use a script to delete all Windows Store Apps which is really important for our image during the time when the reference machine was connected to the internet, and according to another article that is an issue when Sysprep to capture the WIM. The wim file is created without any errors but when start the dep[loyment failed with Error: 5640 50: Run DISM.exe. What is your suggestion about this scenario?
Thank you for your time and effort here!

 

Questions regarding sysprep and capture in MDT

I have a question regarding the sysprep and capture function in MDT 2013.

I have done a sysprep & capture on a Windows 10x64 machine with software and drivers included using MDT.

So the next step I did was to deploy the captured .iso file onto a new machine which had the usual configuration steps including setting up the computer name, timezone and keyboard layout etc and everything was start up fine and all the software and drivers were also configured & installed properly.

However, the issue is that machine's SID and computer name were completely the same as the one I ran the sysprep & capture on. Was this supposed to be like this? Because I did some research and a sysprep is supposed to change the SID as it is treated as a new machine. Also, I did configure a new computer name for the machine during the deployment setup but I have no idea why its the same name as the other machine.
I would appreciate any answers given. Thank you.