Microsoft Deployment Toolkit release notes
This article provides details on the latest release of the Microsoft Deployment Toolkit (MDT). These details include supported platforms, prerequisites, and any limitations. It assumes familiarity with MDT version concepts, features, and capabilities.
MDT build 8456 is the latest version available on the Microsoft Download Center.
This update begins support for Windows 10, version 1809, and Windows Server 2019. For more information, see the supported platforms section.
Here is a summary of the significant changes in MDT build 8456.
Supported configuration updates
- Windows ADK for Windows 10, version 1809
- Windows 10, version 1809
- Configuration Manager, version 1810
The following list is a summary of the major changes in this version:
- Nested task sequence support for LTI scenario
- Modern language pack supportNote 1
- Support for Configuration Manager version 1810Note 2
- IsVM evaluates to False on Parallels VMs
- IsVM = False when VMware VM is configured with EFI boot firmware
- Gather doesn't recognize All-in-One chassis type
- MDT doesn't automatically install BitLocker on Windows Server 2016
- BDEDisablePreProvisioning typo in ZTIGather.xml
MDT releases are no longer tagged with year or update version. To align better with the current branches of Windows 10 and Configuration Manager, and to simplify the branding and release process, it's now simply Microsoft Deployment Toolkit. The build number is used to distinguish each release. For example, the latest build available for download is 8456.
Unlike Configuration Manager with a predetermined release schedule, MDT only releases as required to support new versions of Windows 10, the Windows ADK, or Configuration Manager current branch. Any known issues with these components will be documented in this article as necessary.
The following OS versions are supported for deployment with MDT:
- Windows 10, version 1809
- Windows 10, version 1803
- Windows 10, version 1709
- Other supported versions of Windows 10
- Windows 8.1
- Windows 7
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2
MDT requires the following components, which are included in Windows:
- Microsoft .NET Framework 4.0
- Windows PowerShell version 3.0
MDT requires the latest Windows ADK for Windows 10. MDT also requires the Windows PE add-on for the Windows ADK.
Windows recommends using the Windows ADK that matches the version of Windows you're deploying. For example, use the Windows ADK for Windows 10 version 1809 when deploying Windows 10 version 1809. For more information on Windows ADK component supportability, see DISM supported platforms and USMT requirements.
When integrating MDT with Configuration Manager for ZTI and UDI scenarios, use the latest version of Configuration Manager current branch.
The MDT installation process removes any existing instances of MDT installed on the same computer. Existing deployment shares, distribution points, and databases are preserved during this process. They must be upgraded when the installation is complete.
The current release of MDT supports upgrading from the following versions of MDT:
- MDT build 8450
Create a backup of the existing MDT infrastructure before attempting an upgrade.
After installing MDT, upgrade an existing deployment share by running the Open Deployment Share Wizard from the Deployment Shares node in the Deployment Workbench. Specify the path to the existing deployment share directory, and then select the Upgrade check box. This process also upgrades existing network deployment shares and media deployment shares, so those shares should be accessible. Don't upgrade with active deployments, because in-use files can cause upgrade problems.
Existing MDT task sequences present in Configuration Manager aren't modified during the installation process of MDT. They should continue to work without any issue. No mechanism is provided to upgrade these task sequences. If you want to use any of the new MDT capabilities, create new MDT-integrated task sequences in Configuration Manager.
When the upgrade process is complete:
Run the Configure ConfigMgr Integration Wizard after the upgrade. It registers the new components and installs the updated ZTI task sequence templates.
Create a new Microsoft Deployment Toolkit Files package for any new ZTI task sequences you create. You can use the existing MDT Files package for any ZTI task sequences created before the upgrade. Create a new MDT Files package for new ZTI task sequences.
Modern language pack support
Starting with Windows 10 version 1809, language interface packs (LIPs) are delivered as local experience packs (LXPs). LXPs are AppX bundles. When specified in the unattend.xml file, they aren't automatically selected, and the deployment fails. Don't set LXPs as default. Users should select an applied LXP from Windows settings.
Frequently asked questions
What's the MDT support life cycle?
For more information, see Microsoft Deployment Toolkit support life cycle.
Is this release only supported with Windows 10, Windows ADK, or Configuration Manager version X?
We primarily tested this build of MDT with the configuration listed above. Unless there are any explicit known issues, anything outside of the above configuration has a high probability of still working. Your mileage may vary as we haven’t explicitly tested other combinations.
How do I get help with MDT?
Use one of the following methods to get help with MDT (in prioritized order):
Post to the MDT forum. MVPs and others in the community watch and respond to posts there. This method is probably the most efficient way to get help.
Contact Microsoft Support. Open a support case and get some professional help.
If you can consistently reproduce an issue and think it's a product bug, file it in the Windows 10 Feedback Hub. The product team investigates everything that's reported. When filing feedback, use the Enterprise Management category and OS Deployment subcategory. This categorization helps classify and route your feedback to the MDT team.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.