Deploy Windows Captured Image Using SCCM and MDT

by

Let’s understand how to Deploy a Windows Captured Image Using SCCM and MDT. This post will help you manage the deployment of a Windows Captured Image and deploy a Windows Image using MDT + SCCM.

Let’s learn how to deploy Windows 10 images using the Microsoft Deployment Tool (MDT). The same image can be used in SCCM or MECM.

In my previous post, I described the working mechanism of the Sysprep tool and the process of capturing the Windows Image. Learn How to Sysprep Capture Windows 10 Image using DISM.

Since we had successfully captured the Windows image, the next step would be to deploy the captured image.

Patch My PC
Index
Deploy Windows Captured Image (Windows 10 Image)
Prerequisites
Implementation Activities and Tasks
Import Custom Image for Deployment
Prepare the Driver Repository
Create and Configure the MDT Task Sequence
Customize the Task Sequence
Answer files (unattend.xml)
Create a Selection Profile
Creating an Offline MDT Deployment Media
Configure MDT Deployment Share Rules
WinPE Drivers
Why need to Update Deployment Share
Split a Windows Image File (.wim) 
Deploy Windows Captured Image Using SCCM and MDT – Table.1

Deploy Windows Captured Image (Windows 10 Image)

We have many options for managing and proceeding with the deployment. We will choose the Microsoft Deployment Toolkit (MDT) to deploy the captured WIM File.

Microsoft Deployment Tool (MDT) allows you to create Zero Touch Installations to deliver an automated deployment scenario.

Adaptiva
  • Requires no interaction by the user.
  • Users do not need to know any configuration information before initiating the deployment process.
  • You can customize your task sequence much more easily.
  • It can preconfigure the user profile and apply user-based settings and customizations.
  • With CopyProfile, you can change default user settings and apply them to the user profile on the system during deployment.

Prerequisites

  • Microsoft Deployment Toolkit (MDT) 8456 Download
  • Windows ADK 10 v1903 Download
  • WinPE Addon for Windows ADK 10 v1903 Download
  • Windows 10 Image
  • Configure MDT Deployment Share to Create Reference Image

Implementation Activities and Tasks

Please remember the following implementation activities and tasks for MDT Server Components:

First, in the Deployment WorkBench, set up the MDT Deployment Share and import the necessary source files. Next, move on to configuring the Task Sequence, which involves importing the source files to the server, creating the folder structure, importing the custom Image (Captured WIM File), and importing essential device drivers.

After that, create the Task Sequence by importing applications, editing the Unattend.xml file, and configuring the MDT deployment share with the rules required to make a dynamic deployment process.

Moving on to the target machine, create the selection profiles and generate a bootable USB with media for mass deployment.

Finally, update the Deployment Share with the boot image by updating the media content with the boot image, source files, and task sequence. Additionally, create an Offline Media for deployment.

Deploy Windows Captured Image Using SCCM and MDT - Fig.1
Deploy Windows Captured Image Using SCCM and MDT – Fig.1

Import Custom Image for Deployment

  • Expand the Deployment Shares and the MDT Deployment Share.
  • Create a folder structure inside the Operating Systems. This helps organize selection profiles. Right Click in Operating Systems > Created Folder and select Import Operating System
Deploy Windows Captured Image Using SCCM and MDT - Fig.2
Deploy Windows Captured Image Using SCCM and MDT – Fig.12

Select the Custom Image file to add a captured image you wish to deploy.

Deploy Windows Captured Image Using SCCM and MDT - Fig.3
Deploy Windows Captured Image Using SCCM and MDT – Fig.3

Click on Browse; specify the location of the wim file. After Specifying the full path, you can check the box to move the files to the deployment share and click Next. To save your time!

Don’t forget to keep a copy of imported Images.

Deploy Windows Captured Image Using SCCM and MDT - Fig.4
Deploy Windows Captured Image Using SCCM and MDT – Fig.4

Select Setup files that are not needed and click Next.

Deploy Windows Captured Image Using SCCM and MDT - Fig.5
Deploy Windows Captured Image Using SCCM and MDT – Fig.5

Accept this default directory name or specify the directory’s name and click Next.

Deploy Windows Captured Image Using SCCM and MDT - Fig.6
Deploy Windows Captured Image Using SCCM and MDT – Fig.6

Review the values and click Next.

Deploy Windows Captured Image Using SCCM and MDT - Fig.7
Deploy Windows Captured Image Using SCCM and MDT – Fig.7

You will get a message: “The Import Operating System Wizard completed successfully.” Click Finish.

Deploy Windows Captured Image Using SCCM and MDT - Fig.8
Deploy Windows Captured Image Using SCCM and MDT – Fig.8

The captured image of the reference computer is added under Operating Systems.

Deploy Windows Captured Image Using SCCM and MDT - Fig.9
Deploy Windows Captured Image Using SCCM and MDT – Fig.9

Prepare the Driver Repository

You must download all device drivers for the required models from the OEM Manufacturer’s website. Once you have downloaded the necessary drivers, store them in a folder for a specific model.

Deploy Windows Captured Image Using SCCM and MDT - Fig.11
Deploy Windows Captured Image Using SCCM and MDT – Fig.10

Download, Extract and Import Drivers within your folder into MDT

Next, we want to create a folder structure in MDT under the Out-of-Box Drivers node to organize our drivers.

To add drivers for the operating system of different hardware models, Check this Microsoft Blog.

Create and Configure the MDT Task Sequence

Right-click on the Task Sequence node and select “New Task Sequence.”

Deploy Windows Captured Image Using SCCM and MDT - Fig.11
Deploy Windows Captured Image Using SCCM and MDT – Fig.11

Provide the Task sequence ID and Task sequence name.

Deploy Windows Captured Image Using SCCM and MDT - Fig.12
Deploy Windows Captured Image Using SCCM and MDT – Fig.12

Select Template Standard Client Task Sequence from the available list.

Deploy Windows Captured Image Using SCCM and MDT - Fig.13
Deploy Windows Captured Image Using SCCM and MDT – Fig.13

Select OS: Choose the imported Custom Image to deploy with this Task Sequence.

Deploy Windows Captured Image Using SCCM and MDT - Fig.14
Deploy Windows Captured Image Using SCCM and MDT – Fig.14

Select Do not specify a product key at this time.

Deploy Windows Captured Image Using SCCM and MDT - Fig.15
Deploy Windows Captured Image Using SCCM and MDT – Fig.15

Fill in the fields Full Name, Organization, Internet Explorer Home Page (these fields can be modified through Answers File at a later stage), and click Next.

Deploy Windows Captured Image Using SCCM and MDT - Fig.16
Deploy Windows Captured Image Using SCCM and MDT – Fig.16

Select Don’t specify an Administrator password at this time Option. Click Next.

Deploy Windows Captured Image Using SCCM and MDT - Fig.17
Deploy Windows Captured Image Using SCCM and MDT – Fig.17

Review the details and click Next.

Deploy Windows Captured Image Using SCCM and MDT - Fig.18
Deploy Windows Captured Image Using SCCM and MDT – Fig.18

The task Sequence creation process was completed successfully. Click Finish to close the wizard.

Deploy Windows Captured Image Using SCCM and MDT - Fig.19
Deploy Windows Captured Image Using SCCM and MDT – Fig.19

We have a pretty bare-bones task sequence that will only install Windows and nothing else.

We need to edit Task Sequences and add custom steps to perform other actions required with this Windows installation into a target machine.

Deploy Windows Captured Image Using SCCM and MDT - Fig.20
Deploy Windows Captured Image Using SCCM and MDT – Fig.20

Customize the Task Sequence

You can edit the task sequence by navigating to the Task Sequences, right-clicking on the created task sequence Name, and selecting Properties.

Deploy Windows Captured Image Using SCCM and MDT - Fig.21
Deploy Windows Captured Image Using SCCM and MDT – Fig.21
Deploy Windows Captured Image Using SCCM and MDT - Fig.22
Deploy Windows Captured Image Using SCCM and MDT – Fig.22

Under the Preinstall section, we will configure the Inject Drivers step to use the selection profile > Nothing in the task sequence.

Deploy Windows Captured Image Using SCCM and MDT - Fig.23
Deploy Windows Captured Image Using SCCM and MDT – Fig.23

We will add a custom Task Sequence Variable step above the Inject Drivers step to set our DriverGroup001 variable to point to the model’s path that we are installing the %model% variable filled.

Deploy Windows Captured Image Using SCCM and MDT - Fig.24
Deploy Windows Captured Image Using SCCM and MDT – Fig.24

Task Sequence will appear below; apply changes, click Apply and OK.

Deploy Windows Captured Image Using SCCM and MDT - Fig.25
Deploy Windows Captured Image Using SCCM and MDT – Fig.25

Answer files (unattend.xml)

Right-click on the task sequence you created and choose “Properties.” On the “OS Info” tab, click on “Edit Unattend.xml,” which will be Windows System Image Manager.

Deploy Windows Captured Image Using SCCM and MDT - Fig.26
Deploy Windows Captured Image Using SCCM and MDT – Fig.26

It started automatically generating a catalog file for the selected WIM. Depending on your configuration, this process could take a while. 

Deploy Windows Captured Image Using SCCM and MDT - Fig.27
Deploy Windows Captured Image Using SCCM and MDT – Fig.27

Once the generation is complete, you’re free to change your Unattend.xml. 

For all unattended settings that can be applied to the answer file. For a complete description of the components, see the Microsoft Docs Unattend Components.

Deploy Windows Captured Image Using SCCM and MDT - Fig.28
Deploy Windows Captured Image Using SCCM and MDT – Fig.28

Run the Validation check, click the Tools menu and select Validate Answer File.

Deploy Windows Captured Image Using SCCM and MDT - Fig.29
Deploy Windows Captured Image Using SCCM and MDT – Fig.29

You should see that your validation answer file has errors in the Messages area at the bottom of the screen. Double-click on any results to take a right to that setting to remediate any issues.

Make the necessary changes, validate the answer file, and save and exit. 

Deploy Windows Captured Image Using SCCM and MDT - Fig.30
Deploy Windows Captured Image Using SCCM and MDT – Fig.30

Create a Selection Profile

Selection profiles in the Advanced Configuration node allow users to filter content in the Deployment Workbench.

Selection profiles are used for several purposes in the Deployment Workbench and Lite Touch deployments. For example, they can be used to: 

  • Control which drivers and packages are injected into the boot images. 
  • Control which drivers are injected during the task sequence. 
  • Control what is included in any media that you create. 
  • Control what is replicated to other deployment shares. 
  • Filter which task sequences and applications are displayed in the Deployment Wizard.  

Expand Advanced Configuration. Right-click on Selection Profiles and select New Selection Profile.

Deploy Windows Captured Image Using SCCM and MDT - Fig.31
Deploy Windows Captured Image Using SCCM and MDT – Fig.31

Provide the Selection profile name and Comments for best practice.

Deploy Windows Captured Image Using SCCM and MDT - Fig.32
Deploy Windows Captured Image Using SCCM and MDT – Fig.32

Here, we can select the available applications, Operating Systems, Drivers, Packages, and Task Sequences that we need to include in the Image.

Note: Selecting more than necessary will result in larger ISO files and USB storage requirements.

Once done with the selection, click on Next.

Deploy Windows Captured Image Using SCCM and MDT - Fig.33
Deploy Windows Captured Image Using SCCM and MDT – Fig.33

Here, we will get a summary page with detailed information.

Deploy Windows Captured Image Using SCCM and MDT - Fig.34
Deploy Windows Captured Image Using SCCM and MDT – Fig.34

Click on the Finish button to complete the process.

Deploy Windows Captured Image Using SCCM and MDT - Fig.35
Deploy Windows Captured Image Using SCCM and MDT – Fig.35

A custom Selection Profile has been created based on your selection.

Deploy Windows Captured Image Using SCCM and MDT - Fig.36
Deploy Windows Captured Image Using SCCM and MDT – Fig.36

Note: If you need to make any changes later, you can modify the selection profiles by right-clicking> properties in the completed profile.

Deploy Windows Captured Image Using SCCM and MDT - Fig.37
Deploy Windows Captured Image Using SCCM and MDT – Fig.37

Creating an Offline MDT Deployment Media

Right Click on Media and select New Media.

Deploy Windows Captured Image Using SCCM and MDT - Fig.38
Deploy Windows Captured Image Using SCCM and MDT – Fig.38

Under New Media Wizard, provide the Media path by clicking on the Browse option. We have created a new directory under C drive named “MDT Offline Media.”

Note: The path of the provided directory should be empty.

Now select the selected profile from the drop-down list that was created earlier.

Deploy Windows Captured Image Using SCCM and MDT - Fig.39
Deploy Windows Captured Image Using SCCM and MDT – Fig.39

Review the selected values and Click on Next.

Deploy Windows Captured Image Using SCCM and MDT - Fig.40
Deploy Windows Captured Image Using SCCM and MDT – Fig.40

Please wait for a while to complete the process. Once you get a message, “The Process completed successfully,” Click on Finish.

Deploy Windows Captured Image Using SCCM and MDT - Fig.41
Deploy Windows Captured Image Using SCCM and MDT – Fig.41

Under Media, you can now see that new media has been created.

Deploy Windows Captured Image Using SCCM and MDT - Fig.42
Deploy Windows Captured Image Using SCCM and MDT – Fig.42

Right-click in media [in my case, MEDIA001] and choose Properties.

Deploy Windows Captured Image Using SCCM and MDT - Fig.43
Deploy Windows Captured Image Using SCCM and MDT – Fig.43

Select the Platforms Supported; provide the appropriate name for ISO.

Deploy Windows Captured Image Using SCCM and MDT - Fig.44
Deploy Windows Captured Image Using SCCM and MDT – Fig.44

Configure MDT Deployment Share Rules

To automate media Installations, you modify the two rules files (Bootstrap.ini and CustomSettings.ini). The rules control the Windows Deployment Wizard on the client and provide the following settings to the machine being deployed:

  • Computer name
  • Domain to join, and organizational unit (OU) in AD to hold the computer object.
  • Whether to enable BitLocker
  • Regional settings: You can manage hundreds of locations using the rules.

Click on the Rules tab, where you will get the default settings.

Deploy Windows Captured Image Using SCCM and MDT - Fig.45
Deploy Windows Captured Image Using SCCM and MDT – Fig.45

Important! Generate a computer name based on a serial number
A serial number can contain 15 characters, but the Windows setup limits a computer name to 15 characters. More Details Configure MDT deployment share rules

Below the configurations I used, you can modify the Rules in the deployment process based on Toolkit Reference.

CustomSettings.ini

Select the Rules tab and modify the properties window using the sample information.

[Settings]
Priority=Default
[Default]
_SMSTSORGNAME=Test Infra
OSInstall=YES
OSDComputerName=PC-%SerialNumber%
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBitLocker=YES
SkipCapture=YES
SkipComputerName=YES
SkipComputerBackup=YES
SkipDeploymentType=YES
DeploymentType=NEWCOMPUTER
SkipDomainMembership=YES
SkipAdminPassword=YES
AdminPassword=P@ssWord
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
SkipPackageDisplay=YES
SkipProductKey=YES
SkipSummary=YES
TimeZoneName=UTC
SkipTimeZone=YES
SkipUserData=Yes
SkipTaskSequence=YES
TaskSequenceID=W10X64
_SMSTSOrgName=Test Infra
SkipFinalSummary=NO

Bootstrap.ini

Click Edit Bootstrap.ini will open the configuration in Notepad and modify it using the following information.

[Settings]
Priority=Default
[Default]
SkipBDDWelcome=YES

Click Apply to save the changes and OK to close the Media Properties.

WinPE Drivers

You can create separate folders under your Out-of-Box Drivers node for WinPE_x86 and WinPE_x64 drivers and add the drivers. In the Windows PE tab, in the Platform drop-down list, make sure x64 is selected. Select the Drivers and Patches tab.

By default, MDT will inject all network adapters and mass storage drivers into the WIM file. From the Selection profile drop-down list, choose the selection profile that you created
for WinPEx64.

Deploy Windows Captured Image Using SCCM and MDT - Fig.46
Deploy Windows Captured Image Using SCCM and MDT – Fig.46

Why need to Update Deployment Share

Generally, you need to update the deployment share when you make changes that affect the boot image. That would include:

  • A driver needs to be injected into WinPE was added.
  • Modified the boot image settings.
  • Changes to the Bootstrap.ini file.
  • Updated any of the scripts or files.

Update the deployment share by right-clicking the MDT Build Lab deployment share and selecting Update Deployment Share. Use the default options for the Update Deployment Share Wizard.

It will only inject drivers into WindowsPE from the specified folder in your selected profile.

Deploy Windows Captured Image Using SCCM and MDT - Fig.47
Deploy Windows Captured Image Using SCCM and MDT – Fig.47

Split a Windows Image File (.wim) 

We need to configure or validate this setting once before deployment with an image larger than 4GB, as FAT32 is required to boot the UEFI System with a maximum supported file size of 4GB. 

After splitting the Image into a set of smaller (.swm) files, it can handle images larger than 4GB when installing Windows images from USB or DVD.

In the Deployment share > Control > Settings.xml. Open with Notepad to modify.

Deploy Windows Captured Image Using SCCM and MDT - Fig.48
Deploy Windows Captured Image Using SCCM and MDT – Fig.48

Make Sure the Settings.xml File has the following settings: Save and close the Notepad.

<SkipWimSplit>False</ SkipWimSplit>
Deploy Windows Captured Image Using SCCM and MDT - Fig.49
Deploy Windows Captured Image Using SCCM and MDT – Fig.49

Important Tips! Before updating media content, it’s better to close all the opened instances of Deployment Share, a path used by some other process. If needed, sign out of the logged-in User Account, log in to Server, and open Deployment Share> Advanced Configuration> Media> Update Media Content.

Right-click on Media and select Update Media Content.

Deploy Windows Captured Image Using SCCM and MDT - Fig.50
Deploy Windows Captured Image Using SCCM and MDT – Fig.50

The ISO Image creation will be in progress, and it will take longer to complete the process.

Deploy Windows Captured Image Using SCCM and MDT - Fig.51
Deploy Windows Captured Image Using SCCM and MDT – Fig.51

Once Media generation is completed successfully, Click on Finish to close the wizard.

Deploy Windows Captured Image Using SCCM and MDT - Fig.52
Deploy Windows Captured Image Using SCCM and MDT – Fig.52

Media has been created successfully; you can see the ISO files for deployment have been made under the path you specified.

Create a bootable USB from the ISO for offline deployment, depending on your target devices.

We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.

Author

Jitesh Kumar has over five years of experience in the IT Industry. He writes about and shares his experiences related to Microsoft device management technologies and IT infrastructure management. His primary focus is the Windows 10 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.

10 thoughts on “Deploy Windows Captured Image Using SCCM and MDT”

  5. Hi Jitesh,

    Thanks for putting your efforts making such a detailed deployment knowledge article on Windows 10. It was really helpful to me.

    I have got a few Questions on setting up Computer name during OSD?

    1.What’s is best way to configure PC Name?

    2. How to configure TS so That it can Name the Device based on whether it’s Laptop,Desktop or a Tablet?

    I Look forward to hearing from you soon.

    Regards,
    Vishal

    Reply

    • Thanks Vishal..

      You can configure variable IsDesktop , IsLaptop and IsTablet to distinguish devices inside the Customsettings.ini rules. Based on your environment requirements you can customize the rules.
      Here’s the sample Rules –

      [Settings]
      Priority=ByLaptop, ByDesktop, Default
      Properties=ComputerType,MyCustomProperty

      [ByLaptop]
      SubSection=Laptop-%IsLaptop%
      ComputerType=L

      [By Desktop]
      SubSection=Desktop-%IsDesktop%
      ComputerType=D

      [By Tablet]
      SubSection=Desktop-%IsTablet%
      ComputerType=T

      OSDComputerName=%ComputerName%-%SerialNumber%

      As these variables are handled by ZTIGather.wsf where there’s no pre defined variable for Tablet, You can prefer the solutions prescribed by Keith.

      Add a step Set Task Sequence Variable – IsTablet = True in Task Sequence.

      In the Options tab, add WMI Query with the following-

      SELECT * FROM Win32_ComputerSystem WHERE PCSystemType = 2 and PCSystemTypeEx = 8

      Reply

  6. February 21, 2022

    https://www.anoopcnair.com/sysprep-capture-windows-10-image-using-dism/
    Learn How to Sysprep Capture Windows 10 Image using DISM
    https://www.anoopcnair.com/deploy-windows-captured-image-using-sccm-mdt/
    Deploy Windows Captured Image Using SCCM and MDT

    Hello,
    I wonder if there is an easier way to use “sysprep” and its deployment.
    What I would like is to use a simple PC with Windows 10 Pro on “one” (system partition and installation partition) and an external hard drive.

    And to use “sysprep” and “DISM” only. I understand that IT works on servers and virtual machines but this is not my case. Finally, I just use “VirtualBox” and I am not an expert. And regarding the servers my level is that of a chimpanzee.

    If you have the time and a suggestion for me, simple, I would like to know it.
    Thanks for sharing your knowledge.

    Reply

  9. Dear Anoop,

    I am looking for some help here in regards to my SCCM. In one my company we was using one form before going for actual OSD deployments. In this form we was able to define host name, User name of machine, domain and etc….How we can do that? It was simple web based form….and machine added for OSD was visible into the list of machines you want to image. Any help would be really appriciated.

    Many Thanks!

    Mukesh Kharade

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.