Blog Post

Configuration Manager Blog
1 MIN READ

MDT 8456 Now Available

yvetteomeally's avatar
yvetteomeally
Icon for Microsoft rankMicrosoft
Jan 28, 2019

We are pleased to announce that the Microsoft Deployment Toolkit (MDT), version 8456, is now available on https://aka.ms/mdtdownload 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.

Updated Jan 28, 2019
Version 1.0
mdt
OS deployment
  • Deleted's avatar
    Deleted
    Jan 31, 2019
    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.
  • DanJ_LRSFC's avatar
    DanJ_LRSFC
    Copper Contributor
    Jan 29, 2019

    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.

     

    Thanks,

    Dan Jackson (Senior ITServices Technician)

    Long Road Sixth Form College

    Cambridge, UK.

  • David Bradtberg's avatar
    David Bradtberg
    Copper Contributor
    Jan 30, 2019

    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.

     

    Thanks

    David Bradtberg

  • YYCBB's avatar
    YYCBB
    Copper Contributor
    Feb 19, 2019

    brand new implementation of Server 2016/CM1810/Windows 10 1809 ADK/MDT8456 this combination appears to have a requirement for Powershell 2.0 components to be able to create MDT boot images. Spent a whole day trying to figure out why we couldn't create MDT boot images via the sccm console. Have never required to have powershell 2.0 to complete the same work at previous clients using previous MDT versions. Can anyone confirm this is a new "undocumented" pre-req with MDT 8456 configuration manager integration?

  • jllorente's avatar
    jllorente
    Copper Contributor
    Mar 04, 2019

    Hi there! Does this new MDT version fixes the issue with Windows 10 1809 where the deployment fails with error "Failure 5627 / Task Sequence Error 0x80004005" when the Windows Update packages are added? Thanks in advance!

  • DanielDavila's avatar
    DanielDavila
    Brass Contributor
    Mar 20, 2019

    yvetteomeally  Can you comment on the rationale for ISVM=False when using VMware with EFI?
    It's easy enough to overwrite the logic via editing ZTIGather or CustomSettings.ini, but it doesn't make sense on why it should behave this way out of the box when it doesn't for Hyper-V with Gen2.

  • mattmn160's avatar
    mattmn160
    Iron Contributor
    Mar 28, 2019

    @YYCBB Yes PowerShellS 2.0 is still needed even though MS says not to use it anymore for security reasons. I had a case open with the engineers last year and they are working on getting PowerShell 2 out of SCCm and MDT. No time line was given.

Share