24H2 MDT sysprep issues

[tayyab12]

Hi everyone

i am about to launch myself out the window over this. i have been working on upgrading my image to 24h2 from 23h2. i have upgraded the ADK tools. Done a fresh install of windows 11 education. i have updated it and added all the apps i needed. all done via vmware. i use MDT to sysprep and capture the image. so i go ahead and sysprep the machine. a window pops up saying processing sysprep plugins etc then after a while an error pops up with "Can not find script file "\\servername\d$\deploymentshare\scripts\LTIcleanup.wsf"

 

Done some research but found very little information on this. if i was to sysprep my current image of 23h2 it works fine. just 24h2 dosent seem to wanna work at all. Everything is being done the same i usually do it. 

 

i would really appreciate any help

[timbo343]

Try this thread - https://www.edugeek.net/forums/topic/223559-mdt-wds-adk-update-for-windows-11/#findComment-2002041

 

 

I spent a week trying to get 24H2 and 24H2.6 to sysprep and managed to finally get it to work. Hopefully the notes work for you.

 

[timbo343]

On the back of this, i've read not to use VMWare. It's preferred to use HyperV but I have it working in Virtualbox.

 

I tested the exact same process with 22H2, 23H2, 24H2 and 24H2.6 and the 24H2 releases failed. I tested Win11 LTSC2024 too.

 

[random8910]

Your machine doesn't have network and its trying to run the LTICleaup.wsf script off your MDT server.

 

You need to verify you can get that machine access to your deployment share. If you do not want to do that, you can run sysprep with your unattend file manually and then capture the image with a PXE of your choice.

Edited May 29, 2025 by random8910

[tayyab12]

Right a step closer, thanks for your help guys but now another issue is that it reboots into litetouch again. like it does the loading files screen but then goes into the litetouch login as if it was imaging a pc. usually on my current build it goes on to the next step of Create WIM. Not sure what is going on here. everything like the custom ini file and ts is the same as it has been with 23h2 so not sure what else i need to change.

 

Custom ini file:

 

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
UserExit=UserExit.vbs
OSDComputername=#GetOfflineComputername()#
FinishAction=REBOOT
OSInstall=Y
SkipCapture=NO
DoCapture=YES
SkipTaskSequence=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipComputerName=NO
SkipDeploymentType=NO
SkipDomainMembership=NO
SkipUserData=YES
SkipLocaleSelection=YES
SkipSummary=YES
SkipTimeZone=YES
SkipFinalSummary=YES
EventService=http://SERVERNAME:9800

[timbo343]

I had the exact same issue and I think it was to do with the boot images.

 

Here is my Connect.ini for the CaptureShare (as I have a capture and deployment share)

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
DoCapture=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=NO
SkipBitLocker=NO
EventService=http://*ServerName*:9800

 

Here is the bootstrap.ini for the Capture Share:

[Settings]
Priority=Default

[Default]
DeployRoot=\\*ServerName*\Win11_Capture$

 

Make sure you have the correct OS in the Operating Systems folder for that CaptureShare and you might need to do a full Update Deployment Share.

 

Have a look at this video as there might be some pointers that could help - 

 

[tayyab12]

Fixed from that article TIMBO343  although a messy fix which ms need to fix asap. Had to run the commands below to kick start it. it should automatically just start creating the WIM but 24h2 is a pain along with many other issues. Cheers guys

 

Run Diskpart

Run List disk

Run Select Disk 0

Run List Part (to show the partitions - this is optional)

Run Select Part 3 (which is the primary partition)

Run assign letter=c

Run Exit

Run startnet.cmd to kick capture of sysprepped machine.

[timbo343]

Glad to hear it's working for you. It is very messy for sure however i doubt MS will fox it as there is no more delvelopment work to MDT.