How do I update the Deployment Share properly in MDT?

by · Published · Updated

Applies to: Microsoft Deployment Toolkit (MDT) 8456 and later
Last updated: May 2025

Problem

You’ve made changes in MDT—such as importing drivers, applications, or Task Sequences—and need to regenerate the deployment boot images to reflect those updates.

Solution

The “Update Deployment Share” process in MDT builds the LiteTouch boot images (.wim and .iso) and updates supporting files needed for deployment. It must be run after certain changes to keep your deployment environment consistent and functional.

When Should You Update the Deployment Share?

Change MadeRequires Update?
Added/removed boot-critical drivers✅ Yes
Modified bootstrap.ini✅ Yes (to regenerate ISO/WIM)
Changed Unattend.xml❌ No (applies at runtime)
Added new Task Sequence❌ No (unless you need new boot media)
Added applications or scripts❌ Optional, unless referenced by boot
Changed CustomSettings.ini only❌ No

Step-by-Step Guide

1. Open Deployment Workbench

  • Launch Deployment Workbench
  • Right-click your Deployment Share (e.g., DeploymentShare$) Select Update Deployment Share

2. Choose Update Option

You’ll see two options:

  • Optimize the boot image updating process
    • Faster; use this if you’re not modifying drivers or boot configuration
  • Completely regenerate the boot images
    • Use if:
      • You added new drivers
      • You edited bootstrap.ini
      • You’re seeing boot-related issues

Click Next, then Finish.

3. Wait for the Process to Complete

  • This will generate:
    • LiteTouchPE_x64.wim
    • LiteTouchPE_x64.iso
    • (And x86 versions, if enabled)
  • Files are located in: <DeploymentShare>\Boot\

4. Deploy the Updated Boot Image

If using WDS (PXE boot):

  • Open WDS console
  • Right-click Boot Images > Replace Image
  • Browse to the updated .wim file in the Boot folder

If using USB boot media:

  • Copy the new .iso to your imaging USB
  • Or regenerate the USB using tools like Rufus

Best Practices

  • Always regenerate boot media after changing bootstrap.ini or drivers
  • Keep older versions backed up in case of issues
  • Name ISO and WIM files with version or date suffixes for easy tracking

Notes

  • Updating the Deployment Share does not affect existing deployments unless new boot media is used
  • You can script this process using PowerShell and Update-MDTDeploymentShare

Tags:

You may also like...