24H2 MDT Failure

[ITGURU]

We already deploy 23h2 via MDT which works fine.

I've now build a 24H2 VM and running litetouch.vbs to sysprep and capture the same way (as works successfully) as the 23 h2 image.

It syspreps and reboots the machine but then re-launches the capture wizard and get the error below

however on the 23h2 build, it reboots and starts capturing the image immediate.

Are there updates required for the 24H2 build for MDT to work successfully?

[jthompson]

MDT makes a lot of use of WMI to gather information on the computer, but 24H2 no longer has the wmic utility which the MDT scripts may be depending on. Not exactly sure if that's the root cause of your error, but I've a hunch that it may be.

 

Your level of success with 24H2 in MDT is likely going to depend on what your task sequence is wanting to do, and how much of the computer info it needs is being gathered under WinPE (which will still have wmic) as opposed to under 24H2.

[ITGURU]

MDT makes a lot of use of WMI to gather information on the computer, but 24H2 no longer has the wmic utility which the MDT scripts may be depending on. Not exactly sure if that's the root cause of your error, but I've a hunch that it may be.

 

Your level of success with 24H2 in MDT is likely going to depend on what your task sequence is wanting to do, and how much of the computer info it needs is being gathered under WinPE (which will still have wmic) as opposed to under 24H2.

 

Workaround for now appears to be boot from install media, 'repair my pc' and run dism to capture the image to network share. Import into MDT and change image in Task sequence, then it restores ok.

[DDR5]

Thanks for this post, as I was about to start one myself!

 

I built a 23H2 image a while ago just to test and it captured/deployed fine. I've been waiting for 24H2 though and built an image as normal, and have spent the last few hours trying to figure this out, without success...

[jthompson]

Which ADK are you using?

[ITGURU]

Which ADK are you using?

 

I'm going to use the workaround

- Run sysprep within windows

- Run the dism capture to network path

- import wim as an OS

- change the TS to the new WIM image

- Successfully applied to a machine and it networked fine.