How to Capture a Windows Image with Microsoft Deployment Toolkit (MDT)

Windows image capture isn’t just a geeky exercise—it’s a fundamental process that enables IT administrators to deploy streamlined, customized operating system images quickly across numerous devices. Whether you’re managing a fleet of Windows 11 systems or preparing a secure environment with the latest Microsoft security patches, using the Microsoft Deployment Toolkit (MDT) can save you hours of manual effort. In this article, we’ll dive into the process of capturing a Windows image using MDT, with a detailed, step-by-step guide that covers every aspect from setting up your deployment share to executing the final capture on a reference machine.

Understanding the Power of MDT​

MDT is a free solution from Microsoft that helps you automate the deployment of Windows operating systems along with applications, settings, and configurations. By preparing a reference computer—essentially a “master” system with your preferred settings—MDT utilizes tools like Sysprep and the DISM tool to create a capture image (.WIM file). This image can later be deployed across your environment via SCCM, WDS, or even MDT itself.
The beauty of MDT is in its modularity. By segmenting the deployment process into clearly defined steps, you can customize nearly every aspect of your image capture and deployment. If you’re wondering how all these pieces fit together, let’s explore each step in detail.

Step 1: Creating and Configuring a New Deployment Share​

The first step in your journey is to set up a deployment share—a centralized repository that stores your operating systems, scripts, and configuration files. This share becomes the backbone of your MDT deployment.

• Launch the Deployment Workbench from your MDT console.
• Right-click on “Deployment Shares” and select “New Deployment Share.”
• Choose a new path for your deployment share. This is where all the magic happens!
• Provide a name and a brief description when prompted. It’s a good idea to select a name that easily identifies the purpose, especially if you manage multiple environments.
• Continue through the wizard by repeatedly clicking “Next” until you reach the Progress tab. The wizard will then create your new deployment share.

Once the share is created, you’ll need to adjust its properties to prepare it for image capture:

• Right-click on the newly created deployment share and select “Properties.”
• Under the “Rules” tab, add the directive:
  • OSCapture=YES
  This step is crucial—it tells MDT to capture the image at the right time.
• Under the “General” tab, if you’re working with Windows 11, uncheck the x86 platform support. This ensures your deployment targets only the 64-bit environment.
• Switch to the “Windows PE” tab, set the platform to x64, and uncheck “Generate a Lite Touch bootable ISO image.”
• Lastly, under the “Monitoring” tab, enable monitoring for the deployment share to keep track of your deployments in real time.

Once you’re done, click “Apply” and “OK” to save your configurations.
• Summary: Creating a deployment share sets the foundation for your image capture. Configuring the share with OSCapture=YES and ensuring the correct platform settings are in place is key for successful deployments.

Step 2: Importing the Operating System​

With your deployment share ready, the next step is to import the operating system files that will serve as the basis for your image.

• Ensure you have mounted the operating system ISO. This provides direct access to a full set of source files.
• In the Deployment Workbench, expand your deployment share, and right-click on “Operating Systems.”
• Select “Import Operating System.” Here, choose the “Full set of source files” option.
• Navigate to and select the mounted OS image. MDT will then import the operating system files into the share.
• It’s good practice to give the OS a recognizable name at this stage, especially if you plan on maintaining multiple operating systems. This naming convention will help you easily select the correct OS later during the task sequence creation.

• Summary: Importing the OS into MDT ensures that your deployment share contains the complete operating system files required for customization and capture.

Step 3: Creating a New Task Sequence​

Now that your deployment share knows which operating system to work with, it’s time to create a task sequence. Think of a task sequence as a detailed script that instructs the system on how to prepare and capture the image.

• In the Deployment Workbench, expand your deployment share, then right-click on “Task Sequences” and select “New Task Sequence.”
• Provide a Task Sequence ID and a descriptive Task Sequence Name. Keep the IDs simple and logical (e.g., “TS_CaptureWin11”).
• In the “Select Template” tab that follows, choose the “Sysprep and Capture” option. This template is designed explicitly for capturing images.
• Proceed to the “Select OS” tab and choose the operating system you imported in Step 2.
• Continue walking through the wizard—this is where you set credentials and make other necessary configurations. Don’t forget to set a secure administrator password.
• Finally, click “Finish” to create the task sequence.

This sequence tells MDT exactly what to do: prepare the image (sysprep the system), reboot into Windows Preinstallation Environment (WinPE), and use DISM to capture the Windows image.
• Summary: A well-crafted task sequence is at the heart of the capture process. By using the “Sysprep and Capture” template, you ensure that the system is properly prepared for imaging, with all tasks executed in the correct order.

Step 4: Updating the Deployment Share​

After configuring the share and setting up the task sequence, it’s essential to propagate these changes. Updating the deployment share regenerates the necessary boot images and ensures that your capture settings are in place.

• In the Deployment Workbench, right-click on your deployment share and select “Update Deployment Share.”
• In the update wizard, make sure to check the “Completely regenerate the boot images” option.
• Click “Next” until you reach the final step, and then complete the update process.

Regenerating the boot images is a critical step because it embeds your capture instructions into the Lite Touch boot images. These images are what your reference computer will use to boot into WinPE, from which the capture process will run.
• Summary: Updating the deployment share finalizes the configurations. Regenerating boot images is particularly important to guarantee that custom changes, like the OSCapture setting, are applied correctly.

Step 5: Completing the Deployment on a Reference Computer​

The final stage of capturing your Windows image involves deploying the task sequence on a reference computer—essentially your model system that has been fully customized.
Here’s how you do it:

• Ensure your reference computer (the one you plan to capture) is connected to the same network as the MDT server.
• On the reference computer, press the Windows key + R to open the Run dialog.
• Type the UNC path to access your deployment share (for example, \192.168.13.22\deploymentshare). You may need to enter valid domain user credentials to gain access.
• In the shared folder, navigate to the “Script” directory and run the LiteTouch.vbs script.
• Once the Windows Deployment Wizard opens, provide the required username and password.
• Select “Capture Windows 11 image” (or your appropriate OS) and choose the “Capture an image of this reference computer” option.
• Confirm the UNC path on the MDT server where you want the captured WIM file to be saved. Ensure that the folder has NTFS read/write permissions; otherwise, your imaging process could be interrupted.
• Specify the desired file name for the WIM file.
• Initiate the Task Sequence by confirming all the options.

Once you start the task sequence, here’s what happens behind the scenes:

• The system enters Sysprep mode, which generalizes and cleans the operating system.
• The computer then reboots into WinPE, a lightweight Windows preinstallation environment.
• The DISM tool (Deployment Imaging Service and Management Tool) operates within WinPE to create a captured image of the reference computer.
• After a few minutes (depending on hardware performance and OS complexity), the process completes, and the captured WIM file is saved in the “Captures” folder on the MDT deployment share.

• Summary: Running the LiteTouch.vbs script on your reference computer launches the imaging process. Sysprep and DISM work in tandem within the WinPE environment to create a deployable .WIM file.

Practical Considerations and Tips​

While the steps above provide a clear-cut procedure for capturing a Windows image using MDT, here are some additional practical insights to consider:

• Make sure that your reference computer is configured exactly as required. Any unnecessary software or misconfigurations will be captured along with your image.
• Always test your captured image using a virtual machine or a spare physical device before deploying it across a production environment. This helps you verify that all customizations and applications work as expected.
• Consider maintaining a separate MDT share for development and testing so that production images remain untouched until fully validated.
• Incorporate regular Windows 11 updates and Microsoft security patches into your reference computer before capturing the image. This ensures that your deployed systems are both secure and current.
• MDT seamlessly integrates with other tools like System Center Configuration Manager (SCCM) and Windows Deployment Services (WDS), broadening your deployment strategies. Whether you’re using cybersecurity advisories to prepare a hardened baseline or simply automating daily deployments, MDT’s flexibility is a boon.

• Real-World Example: Imagine a mid-sized enterprise preparing for a company-wide refresh on Windows 11. Instead of manually installing Windows on hundreds of systems, the IT team creates a single reference machine loaded with essential applications (like Office 365, antivirus software, and custom scripts), performs all custom configurations, and captures that image using MDT. The resulting .WIM file not only automates subsequent deployments but also minimizes errors and downtime across the organization.

FAQs and Best Practices​

Below are some frequently asked questions that often come up during the image capture process:
• How do I capture an OS image using MDT?
– By preparing a reference computer with the operating system, applications, and custom settings, then creating a task sequence for image capture using the “Sysprep and Capture” template in MDT. Finally, run the task sequence to use Sysprep and DISM to capture a .WIM file.
• What is a sysprep image?
– A sysprep image is a generalized image created after running the Sysprep tool, which strips unique system information, making the image deployment-ready and minimizing conflicts when deployed on multiple hardware configurations.
• Can MDT capture Windows 11 images?
– Absolutely! MDT supports Windows 11, provided you configure your deployment share and task sequence correctly (e.g., disabling x86 support if not needed).
• Should I update my deployment share every time I make a configuration change?
– Yes, particularly when you modify settings that affect the boot images (like OSCapture). Regenerating the boot images ensures that all changes are properly integrated into the deployment environment.
• Summary:
– A solid understanding of both MDT and Windows image capture processes not only simplifies OS deployment but also enhances system reliability across networks.

Concluding Thoughts​

Capturing a Windows image using the Microsoft Deployment Toolkit is a process that, while detailed, offers substantial benefits to enterprise IT administrators. The systematic approach—starting from setting up a deployment share, importing the operating system, creating a tailored task sequence, updating your share, and finally capturing the image on a reference computer—ensures that every image is consistent, secure, and ready for widescale deployment.
Using MDT, you not only gain expert control over the deployment process but also build a foundation that can evolve with advancements in Windows 11 updates, integration with Microsoft security patches, and new cybersecurity advisories. With careful planning and adherence to best practices, MDT becomes an indispensable tool in your IT deployment arsenal.
Deploying this custom image means you’re prepared for rapid deployment across hundreds of devices with minimal manual intervention—a true game-changer in today’s fast-paced IT environments.
• Overall Summary:
– Create a customized deployment share → Import the full OS files → Design a precise task sequence → Update the deployment share → Run the LiteTouch script on the reference computer → Capture, validate, and deploy your Windows image.
Armed with this guide, you’re well-equipped to implement a streamlined, efficient imaging process that meets both your organizational needs and the ever-evolving landscape of Windows technology.

---

Source: The Windows Club How to capture Windows Image using Microsoft Deployment Toolkit (MDT)