Windows 10: MDT Can't capture a Win11 24H2 reference image

I'm having an issue that seems to be isolated to Win 11 24H2 version. re-tested 23H2 and it captures normally. But when I do a clean install of win11 iso 24h2, put in audit mode, add apps that's neededside note: I have do have to update a regedit setup / state file below but that is normal and I'm able to capture past reference images. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\State]Update to "ImageState"="IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE".When I Do the same thing for Win11_24h2, I get prompted for server credentials with lett

:)

 

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!

 

MDT: Capture and sysprepped reference image

Hello All,

This is my first post in this forum. However I have already followed the excellent tutorials about Windows 10 customization and used some tricks. Now I need some help.

I use MDT 8450 to create a reference image for Windows 10 Pro 1803 with Sysprep. After installing the reference image with a MDT deploy task sequence - task most things are automated.

I run sysprep /generalize /oobe /shutdown

Log in in audit mode and customize the Administrator profile. After that I run sysprep again.

sysprep /generalize /oobe /shutdown /unattend:C:\folder/copyprofile.xml

the unattend xml file has only the copyprofile true switch in it.

Once the system is shut down (VM) I boot into PXE and start the standard capture task of MDT. I switched off the Syspre section of the MDT task since I already ran Sysprep. The wim file is created fine.

After that re-start the VM (not the captured wim file) and now it comes what iritates me. Windows 10 starts a bit slower and ends up at the login screen and not with the OOBE process. I see the same if I replace instal.wim of the Windows 10 ISO with the captured WIM and start the ISO in a VM it installs Windows 10, but ends up at the login screen too and not going through OOBE process.

I would expect after I captured a WIM file, the VM would start with the OOBE process since sysprep run with shutdown option. The only thing between was I PXE booted and captured it. It seems during the capture process something has happened which might Windows think OOBE process is already done. I have to revert to last snapshot and then Windows does the OOBE process.

Thanks

Edy

 

not able to capture image using MDT

not able to capture image using MDT