posts/2022/build-capture-windows-10-22h2/

[utterances-bot]

Build and Capture Windows 10 22H2 Reference Image – Mike Galvin - Technical Consultant

A detailed guide on how to create a Windows 10 22H2 reference image using Microsoft Deployment Toolkit

https://gal.vin/posts/2022/build-capture-windows-10-22h2/

[elkader1983]

Hello, first of all thanks for your setup-script. I’ve adapted it to run in my environment. A few questions and problems are still left.

1. Why do you build a deployment and a build share?
2. The share and access rights are noch correct, you add administrators but connect with mdtAdmin.
3. I want to capture a reference image which was earlier created and configure a rollout with this image.

computer is connected to domain; not working starting with litetouch.vbs - sysprep runs through, pc restarts, try to login administrator, password is wrong. booting from litetouch ISO ends up with sysprep problems

Can you please tell me, how to capture my image? Thanks.

[Digressive]

Hi elkader1983, thanks for the comment.

Why do you build a deployment and a build share?

I do this to separate the two shares to help with managing. I think of it like the deployment share is the "public" share for other techs or users to access to do builds or run other task sequences. The build share is for people who need to make references images.

The share and access rights are noch correct, you add administrators but connect with mdtAdmin.

This is an error on my part and I'll fix this in the next release - thank you for making me aware of it.

I want to capture a reference image which was earlier created and configure a rollout with this image.

You might need to provide some more information as to what stage in image creation you are at, but I'll try to help with what you've said.

If you've already run the task sequence created by the script, then a .wim image should be in the build share under the captures folder. You should import this to the deployment share's operating systems with the MDT console.

Once it's imported, you'll need to create a "deploy" task sequence using the image just captured. I have a guide that can walk you through this.

Please let me know if you need more information.

[elkader1983]

Hello Mike,I’ve managed it yesterday - but it took me countless hours to get behind - but troubleshooting is what I like. Call me crazy, but otherwise I wouldn’t know how things work.I need to rebuild both shares and run only with one share now. I used your script I adapted and don’t know if it was causing the problems. Maybe it was something with the capture task and PE setup - I only use x64 now and insert drivers for different vendors (HP, Lenovo, DELL, Intel, Realtek) to boot up different types of desktops.Right now I have a successful capture and will replicate this setup for another two sites.It was the second time I used MDT and the first time I had also some issues with BIOS/UEFI - the community is great and I also fixed it that time.The last thing I had yesterday was that the E1000 from vSphere VM could no initialize in PE - so I changed to VMXNET3 and inserted the drivers.I don’t know maybe it was because I use an old ML350G6 with only ESXi 6.0 U3 - I cannot run 6.5 U3 or higher because the Smart Array drivers crash every time for my P812i - I have an old but running setup and use this server only a few weeks a year to setup rollouts.Nevertheless your work is great and thanks for your response. I will mark your blog and come by again.Cheers from Austria.LukasMit

[Digressive]

Hi Lukas, its good to hear you solved the problem and many more it sounds like! Thanks for replying and letting me know. All the best to you.

[elkader1983]

Hello, today I’m doing the replication to another two servers.I found out that there’s a problem with MDT 8456 and the latest PE - they are incompatible because of the missing x86 components.So I’ve installed the latest 2004 version of PE.With the actual version you can not open PE tab in Share and MMC crashes.Win11 is without x86 support, so I think that’s the point.Right now I have the problem that with the capture task and started LiteTouch - sysprep won’t start, pops up no errors and restart won’t boot PE, just restarts into Administrator-Session.I think there’s something missing in the mdt right now because of the incompatible version of PE.Sysprep without LiteTouch will go through without errors.I’m digging again…

[elkader1983]

Hello Mike,

I wanted to know if you can tell me how to stop pulling WIM after the rollout of the standard-images?

I’ve also needed to uncomment in unattend.xml – because the LTIBootstrap.vbs was missing in C:\

If I’m restarting again to the LTI-Stick it pulls another WIM.

If I’m starting another LTI-Stick to test multiple sites, it states, that one task is still running and I can start a new one.

I just want to rollout the standard-image on every client and not pull another WIM of every client.

Hopefully you can help me to configure the task sequence and or the unattend.xml.

Thanks

Lukas

[Digressive]

Hi Lukas,

If the task sequence is pulling a WIM then it has probably been created from the Capture template - there are different template for different type of Task Sequence.

If you open your current task sequence then you should see an entry called capture WIM - disabling this will prevent it from pulling a WIM.

[AndyCap147]

Hi Mike,

Thanks for your excellent work and your willingness to share.

After some wrangling I've got to the point of booting the VM using litetouch, however, the VM simply restarts after reaching the MDT splashscreen. I don't reach the option of choosing the task sequence. A dialogue box appears to flash up but it's so quick I can't see any info ( 14 seconds between start and reboot).

I don't get any error, nor are there any in MDT monitoring or on the hypervisor.

Do you have any thoughts as to what could be the issue?

Thanks

Andy

[Digressive]

@AndyCap147 Hi Andy, here's a couple of things to check:

If you have the latest version of the WIndows ADK - you'll need to uninstall it and install the previous version (ADK for Windows 11, version 22H2 - https://go.microsoft.com/fwlink/?linkid=2196127)

If you are running that ADK or a previous version then try removing the username, password and domain information from the bootstrap.ini and/or the customsettings.ini

Don't forget to regenerate the boot media after doing any of these things!

Kind regards, Mike

[nmb2b]

Hi,does mdt support windows server core(without desktop)?

[Digressive]

@nmb2b Yep!

[nmb2b]

Sorry, there may be some ambiguity.I mean installing mdt on the server core.does it support?

[Digressive]

@nmb2b ah I see what you mean! I've never tried it but I think it would work as long as you didn't want to administer it using the Deployment Workbench on the Server Core. You'd have to connect to it remotely.

Hope that helps!

[JoeBundza]

Hi Mike,

I'm using your guide to create a new deployment of 22H2. I have a couple questions. Just to give you a summary I'm using a VM to test my deploys through Hyper-V hosted on my work computer which is domain joined. Our MDT server is located on a network file server. I recently re-updated the LiteTouch.iso to see if that may help since I moved the LiteTouch from my local PC onedrive to the server under the boot Root directory. Since then I'm getting a bunch of errors I'll work through troubleshooting.

I'm running into an issue where I can't login as a domain user after imaging. I have to use local admin it is connected to the domain initially the DNS wasn't being set to our DNS server so I made an Apply Network task under State Restore to manually set the DNS to our two DNS ip's which would be okay.

It's also hanging up after the initial login of the admin account for 10-20 minutes saying "this is taking longer than expected." I'm not sure if it's doing updates/installing in the background but when I login I see it's still going through the Task Sequence.

Thanks Joe

[JoeBundza]

To Update, I'm also having issues with Imaging now. It's failing in the Task Sequence but the operating system works and most of the apps install. It's giving some errors. https://imgur.com/a/dl3inlh

I wasn't able to get the SMSTS logs via network It's running on a Hyper-V VM on my computer. I can try with a USB to have it write to the USB