[mdt] Correct use of MDT?

[bondbill2k2]

I've recently changed jobs, previous roles I've used Ghost, Xenprovisioning and MDT for a base image with nothing really on it all software done locally or via MSI.

 

In the new job we currently use WDS for everything which seems somewhat dated, MDT handles drivers much nicer and works far faster IMO. I've setup the deployment of Win7 and Win10 using MDT however Id like to deploy each OS to a VM then install numerous applications then recapture this to a WIM file which gets used for all classroom deployment. This capture is also used as the base image for all future deployments. Any software or updates can then be added to the image and recaptured.

 

So far I've been running into issues but I wanted to check I'd understood the 'sysprep and capture' task sequencer which to me sounds similar to xendesktop or ghosts create a golden image. I'd then recapture the VM each time I add updates then redeploy to devices. Is that correct or have I got this completely wrong?

Edited May 22, 2017 by bondbill2k2

[Guest kiest90]

Is there a reason for not migrating to MDT? It seems like a lot of work when a much better solution is available free of charge

[Guest kiest90]

Ignore my previous reply. Personally I've never been a fan of using the MDT method of capturing images. I've always created a capture image in WDS and capture my images via the image created

[Guest obsidianpillar]

I've recently changed jobs, previous roles I've used Ghost, Xenprovisioning and MDT for a base image with nothing really on it all software done locally or via MSI.

 

In the new job we currently use WDS for everything which seems somewhat dated, MDT handles drivers much nicer and works far faster IMO. I've setup the deployment of Win7 and Win10 using MDT however Id like to deploy each OS to a VM then install numerous applications then recapture this to a WIM file which gets used for all classroom deployment. This capture is also used as the base image for all future deployments. Any software or updates can then be added to the image and recaptured.

 

So far I've been running into issues but I wanted to check I'd understood the 'sysprep and capture' task sequencer which to me sounds similar to xendesktop or ghosts create a golden image. I'd then recapture the VM each time I add updates then redeploy to devices. Is that correct or have I got this completely wrong?

 

The general rule is to create a template VM that you want to capture, apply a checkpoint pre-capture, then use either WDS or MDT to capture the image (I'd use MDT) and then revert back to the checkpoint. This prevents you using up your three Sysprep counts. You'd need to re-sysprep the machine every time you create a new image, obviously giving it a new checkpoint before you capture so the changes you make will be modified.

[bondbill2k2]

The general rule is to create a template VM that you want to capture, apply a checkpoint pre-capture, then use either WDS or MDT to capture the image (I'd use MDT) and then revert back to the checkpoint. This prevents you using up your three Sysprep counts. You'd need to re-sysprep the machine every time you create a new image, obviously giving it a new checkpoint before you capture so the changes you make will be modified.

 

Sounds good and how i've been doing it but I ran into issues when trying to recapture, today I completely wiped the MDT server (only set it up last week so its not a big loss) and started again. The task sequence you use for capture is that just a basic all default sysprep and capture, nothing required in the config.ini etc?

[Guest obsidianpillar]

Sounds good and how i've been doing it but I ran into issues when trying to recapture, today I completely wiped the MDT server (only set it up last week so its not a big loss) and started again. The task sequence you use for capture is that just a basic all default sysprep and capture, nothing required in the config.ini etc?

 

Hi, if your referring to the "CustomSettings.ini" File then yes, you are correct. I don't modify that and leave it at standard for capturing. It's a case of following through the wizard and it should capture fine. Normal requirements apply such as not joined to the domain etc and you should be fine.

[bondbill2k2]

Getting somewhere now, its capturing when I run the litetouch.vbs form the deployment scripts processing sysprep but errors on the last 'Creating Wim' stage of the task sequencer reporting unable to capture drive D (there is no drive D on the image just a C and a reserved area without a drive assigned). A small 800MB file is created in the captures folder.

[PotNoodleTech]

Your on the right track - WDS is purely to PXE boot an image from MDT. MDT is awesome, slap all your O/S, drivers, apps in and let dem IT suites build baby!!

[gshaw]

Using MDT for our Win10 test builds and aiming to go one step further and lose the "Master" image entirely. Just built from the standard WIM and slot everything else in dynamically.

 

Win7 is a bit more of a pain until MS release some updated media, tried slipstreaming the Convenience Update in but seems to cause errors in the deployment for some reason as yet unknown

[Olliesaurus]

Suggest reading and testing this out, its amazing for reference imaging, no need for checkpoints or making sure you don't lose your base image, just set it off before you leave work and you will have a fully updated and captured WIM for importing the next morning.