MDT 8456 Now Available

We are pleased to announce that the Microsoft Deployment Toolkit (MDT), version 8456, is now available on and replaces MDT version 8450. This update introduces support for Windows 10 version 1809 and Windows Server 2019 as well as the latest version of Windows Assessment and Deployment Kit (ADK).

As well as support for the latest versions of Windows and the ADK, here is a summary of the major changes in MDT 8456.

  • Nested TS for LTI
  • Modern LXP Support*
  • Support for Configuration Manager version 1810**
  • IsVM evaluates to False on Parallels VMs
  • IsVM = False when VMware VM is configured with EFI boot firmware
  • Gather does not recognize All in One chassis type
  • MDT doesn't automatically install BitLocker on Windows Server 2016
  • BDEDisablePreProvisioning typo in ZTIGather.xml

* Starting with Windows 10 1809, Language Interface Packs (LIPs) are delivered as Local Experience Packs (LXPs). LXPs are AppX bundles that do not get automatically selected when specified in the unattend.xml file and the deployment will fail. LXPs should not be set as default and the user should select an applied LXP from Windows settings.


** We primarily tested this build of MDT with the configuration listed above. Anything outside of that will have a high probability of still working, but your mileage may vary as we haven’t explicitly tested other combinations.

Occasional Visitor

You mention that language packs are now delivered as LXPs but that MDT cannot automatically select these or set them as default. Is there then something in Group Policy which we can use to achieve that? Or alternatively, since you mention it's AppX, can PowerShell be used to achieve this? If we deploy Windows 10 computers but are unable to set "English (United Kingdom)" in an automated manner, I would expect that we will receive complaints from our users.



Dan Jackson (Senior ITServices Technician)

Long Road Sixth Form College

Cambridge, UK.

Regular Visitor

You mention that support has been added for Server 2019 and Windows 10 1809 but the ServerManager.XML file still has the original settings for Windows 10 in it's list of roles and features.  Also the newly added Server 2019 roles to the file have the same ID as Server 2016 Core but when you look through the roles and features for 2019 they are different I am just not sure how the file is read to know where it gets the ID of the feature to add or remove.


Is it possible to look at an updated version of this file that supports the individual releases of Windows 10 going forward so we can be sure of the roles and features we are adding and removing.



David Bradtberg

Occasional Contributor
Whilst many of us have updated MDT before, these announcements should always link to the official instructions. CM customers have bricked their system because they followed the lazy description of click and run given on the download page.
Occasional Visitor

Does this require a new ADK to be installed?