Tech Community Live: Endpoint Manager edition
Jul 21 2022, 08:00 AM - 12:00 PM (PDT)

MDT 8456 Now Available

Published Jan 28 2019 10:30 AM 22.4K Views
Microsoft

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.

12 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-326724%22%20slang%3D%22en-US%22%3EMDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-326724%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20pleased%20to%20announce%20that%20the%20Microsoft%20Deployment%20Toolkit%20(MDT)%2C%20version%208456%2C%20is%20now%20available%20on%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmdtdownload%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fmdtdownload%3C%2FA%3E%20and%20replaces%20MDT%20version%208450.%20This%20update%20introduces%20support%20for%20Windows%2010%20version%201809%20and%20Windows%20Server%202019%20as%20well%20as%20the%20latest%20version%20of%20Windows%20Assessment%20and%20Deployment%20Kit%20(ADK).%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EAs%20well%20as%20support%20for%20the%20latest%20versions%20of%20Windows%20and%20the%20ADK%2C%20here%20is%20a%20summary%20of%20the%20major%20changes%20in%20MDT%208456.%3C%2FP%3E%0A%3CUL%20style%3D%22list-style-position%3A%20inside%3B%22%3E%0A%3CLI%3ENested%20TS%20for%20LTI%3C%2FLI%3E%0A%3CLI%3EModern%20LXP%20Support*%3C%2FLI%3E%0A%3CLI%3ESupport%20for%20Configuration%20Manager%20version%201810**%3C%2FLI%3E%0A%3CLI%3EIsVM%20evaluates%20to%20False%20on%20Parallels%20VMs%3C%2FLI%3E%0A%3CLI%3EIsVM%20%3D%20False%20when%20VMware%20VM%20is%20configured%20with%20EFI%20boot%20firmware%3C%2FLI%3E%0A%3CLI%3EGather%20does%20not%20recognize%20All%20in%20One%20chassis%20type%3C%2FLI%3E%0A%3CLI%3EMDT%20doesn't%20automatically%20install%20BitLocker%20on%20Windows%20Server%202016%3C%2FLI%3E%0A%3CLI%3EBDEDisablePreProvisioning%20typo%20in%20ZTIGather.xml%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E*%20Starting%20with%20Windows%2010%201809%2C%20Language%20Interface%20Packs%20(LIPs)%20are%20delivered%20as%20Local%20Experience%20Packs%20(LXPs).%20LXPs%20are%20AppX%20bundles%20that%20do%20not%20get%20automatically%20selected%20when%20specified%20in%20the%20unattend.xml%20file%20and%20the%20deployment%20will%20fail.%20LXPs%20should%20not%20be%20set%20as%20default%20and%20the%20user%20should%20select%20an%20applied%20LXP%20from%20Windows%20settings.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E**%20We%20primarily%20tested%20this%20build%20of%20MDT%20with%20the%20configuration%20listed%20above.%20Anything%20outside%20of%20that%20will%20have%20a%20high%20probability%20of%20still%20working%2C%20but%20your%20mileage%20may%20vary%20as%20we%20haven%E2%80%99t%20explicitly%20tested%20other%20combinations.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-326724%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20pleased%20to%20announce%20that%20the%20Microsoft%20Deployment%20Toolkit%20(MDT)%2C%20version%208456%2C%20is%20now%20available%20on%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmdtdownload%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fmdtdownload%3C%2FA%3E%20and%20replaces%20MDT%20version%208450.%20This%20update%20introduces%20support%20for%20Windows%2010%20version%201809%20and%20Windows%20Server%202019%20as%20well%20as%20the%20latest%20version%20of%20Windows%20Assessment%20and%20Deployment%20Kit%20(ADK).%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-326724%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Emdt%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOS%20deployment%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-400580%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-400580%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20deploying%20Windows%2010%201809%20from%20a%20Windows%20Server%202016%20with%20MDT8456%20there%20are%20two%20network%20drives%20(Z%20and%20Y).%3C%2FP%3E%3CP%3EUsually%20the%20deployment%20only%20use%20the%20network%20drive%20Z%3A%20.%20Now%20we%20see%20Z%20and%20Y%20connected.%20Litetouch%20script%20is%20changed%20with%20MDT8456.%20The%20Litetouch%20Script%20connects%20drive%20Z%3A%20with%20the%20%22Servername%22%20and%20Y%3A%20with%20the%20IP-adress%20(confirmed%20by%20BDD.log).%20Did%20other%20users%20recognize%20the%20same%3F%20Any%20known%20Side%20effects%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20checked%20again%20and%20this%20effect%20is%20coming%20up%20with%20MDT8456%20and%20updating%20an%20existing%20deployment.%20%3Cimg%20id%3D%22smileyembarrassed%22%20class%3D%22emoticon%20emoticon-smileyembarrassed%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fi%2Fsmilies%2F16x16_smiley-embarrassed.png%22%20alt%3D%22Smiley%20Embarassed%22%20title%3D%22Smiley%20Embarassed%22%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20deployment%20still%20works%20fine.%20At%20the%20end%20of%20the%20deployment%20process%20those%20drives%20are%20disconnected.%20%3Cimg%20id%3D%22smileyhappy%22%20class%3D%22emoticon%20emoticon-smileyhappy%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fi%2Fsmilies%2F16x16_smiley-happy.png%22%20alt%3D%22Smiley%20Happy%22%20title%3D%22Smiley%20Happy%22%20%2F%3E%3C%2FP%3E%3CP%3EIf%20there%20is%20a%20reason%20and%20this%20can%20be%20fixed%2C%20let%20me%20know.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390107%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390107%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F247029%22%20target%3D%22_blank%22%3E%40jllorente%3C%2FA%3EFrom%20initial%20tests%20I've%20performed%20with%208456%2C%20it%20seems%20to%20receive%20the%20same%20error.%26nbsp%3B%20I'll%20investigate%20this%20further%20and%20report%20back.%26nbsp%3B%20Although%20I%20could%20have%20them%20as%20app%20installs%20instead%20(callin%20them%20with%20a%20WUSA%20command%20line%20to%20do%20them)%20the%20apply%20patches%20method%20which%20worked%20in%20Win10%201803%20etc%20was%20just%20an%20easier%20and%20more%20efficient%20way%20of%20doing%20so.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390066%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390066%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F287209%22%20target%3D%22_blank%22%3E%40YYCBB%3C%2FA%3E%3CSPAN%3E%26nbsp%3BYes%20PowerShellS%202.0%20is%20still%20needed%20even%20though%20MS%20says%20not%20to%20use%20it%20anymore%20for%20security%20reasons.%20I%20had%20a%20case%20open%20with%20the%20engineers%20last%20year%20and%20they%20are%20working%20on%20getting%20PowerShell%202%20out%20of%20SCCm%20and%20MDT.%20No%20time%20line%20was%20given.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-377750%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-377750%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8458%22%20target%3D%22_blank%22%3E%40Yvette%20O'Meally%3C%2FA%3E%26nbsp%3B%20Can%20you%20comment%20on%20the%20rationale%20for%20ISVM%3DFalse%20when%20using%20VMware%20with%20EFI%3F%3CBR%20%2F%3EIt's%20easy%20enough%20to%20overwrite%20the%20logic%20via%20editing%20ZTIGather%20or%20CustomSettings.ini%2C%20but%20it%20doesn't%20make%20sense%20on%20why%20it%20should%20behave%20this%20way%20out%20of%20the%20box%20when%20it%20doesn't%20for%20Hyper-V%20with%20Gen2.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-359751%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-359751%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there!%20Does%20this%20new%20MDT%20version%20fixes%20the%20issue%20with%20Windows%2010%201809%20where%20the%20deployment%20fails%20with%20error%26nbsp%3B%22Failure%205627%20%2F%20Task%20Sequence%20Error%200x80004005%22%20when%20the%20Windows%20Update%20packages%20are%20added%3F%20Thanks%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-354345%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-354345%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F187820%22%20target%3D%22_blank%22%3E%40Tim%20Nielsen%3C%2FA%3E%2C%20the%201809%20ADK%20is%20the%20supported%20version.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ethanks%3C%2FP%3E%0A%3CP%3EYvette%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-354344%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-354344%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F287209%22%20target%3D%22_blank%22%3E%40YYCBB%3C%2FA%3E%26nbsp%3B%20PowerShell%201.0%20is%20not%20longer%20supported%20and%20PowerShell%202.0%20has%20been%20deprecated.%26nbsp%3B%20See%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdevblogs.microsoft.com%2Fpowershell%2Fwindows-powershell-2-0-deprecation%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdevblogs.microsoft.com%2Fpowershell%2Fwindows-powershell-2-0-deprecation%2F%3C%2FA%3E.%20%26nbsp%3B%20We%20recommend%20using%20a%20higher%20version.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%0A%3CP%3E-Yvette%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353634%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353634%22%20slang%3D%22en-US%22%3E%3CP%3Ebrand%20new%20implementation%20of%20Server%202016%2FCM1810%2FWindows%2010%201809%20ADK%2FMDT8456%20this%20combination%20appears%20to%20have%20a%20requirement%20for%20Powershell%202.0%20components%20to%20be%20able%20to%20create%20MDT%20boot%20images.%20Spent%20a%20whole%20day%20trying%20to%20figure%20out%20why%20we%20couldn't%20create%20MDT%20boot%20images%20via%20the%20sccm%20console.%20Have%20never%20required%20to%20have%20powershell%202.0%20to%20complete%20the%20same%20work%20at%20previous%20clients%20using%20previous%20MDT%20versions.%20Can%20anyone%20confirm%20this%20is%20a%20new%20%22undocumented%22%20pre-req%20with%20MDT%208456%20configuration%20manager%20integration%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-335123%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-335123%22%20slang%3D%22en-US%22%3E%3CP%3EDoes%20this%20require%20a%20new%20ADK%20to%20be%20installed%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328490%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328490%22%20slang%3D%22en-US%22%3EWhilst%20many%20of%20us%20have%20updated%20MDT%20before%2C%20these%20announcements%20should%20always%20link%20to%20the%20official%20instructions.%20CM%20customers%20have%20bricked%20their%20system%20because%20they%20followed%20the%20lazy%20description%20of%20click%20and%20run%20given%20on%20the%20download%20page.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328190%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328190%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20mention%20that%20support%20has%20been%20added%20for%20Server%202019%20and%20Windows%2010%201809%20but%20the%20ServerManager.XML%20file%20still%20has%20the%20original%20settings%20for%20Windows%2010%20in%20it's%20list%20of%20roles%20and%20features.%26nbsp%3B%20Also%20the%20newly%20added%20Server%202019%20roles%20to%20the%20file%20have%20the%20same%20ID%20as%20Server%202016%20Core%20but%20when%20you%20look%20through%20the%20roles%20and%20features%20for%202019%20they%20are%20different%20I%20am%20just%20not%20sure%20how%20the%20file%20is%20read%20to%20know%20where%20it%20gets%20the%20ID%20of%20the%20feature%20to%20add%20or%20remove.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20it%20possible%20to%20look%20at%20an%20updated%20version%20of%20this%20file%20that%20supports%20the%20individual%20releases%20of%20Windows%2010%20going%20forward%20so%20we%20can%20be%20sure%20of%20the%20roles%20and%20features%20we%20are%20adding%20and%20removing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3EDavid%20Bradtberg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327099%22%20slang%3D%22en-US%22%3ERe%3A%20MDT%208456%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327099%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20mention%20that%20language%20packs%20are%20now%20delivered%20as%20LXPs%20but%20that%20MDT%20cannot%20automatically%20select%20these%20or%20set%20them%20as%20default.%20Is%20there%20then%20something%20in%20Group%20Policy%20which%20we%20can%20use%20to%20achieve%20that%3F%20Or%20alternatively%2C%20since%20you%20mention%20it's%20AppX%2C%20can%20PowerShell%20be%20used%20to%20achieve%20this%3F%20If%20we%20deploy%20Windows%2010%20computers%20but%20are%20unable%20to%20set%20%22English%20(United%20Kingdom)%22%20in%20an%20automated%20manner%2C%20I%20would%20expect%20that%20we%20will%20receive%20complaints%20from%20our%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EDan%20Jackson%20(Senior%20ITServices%20Technician)%3C%2FP%3E%3CP%3ELong%20Road%20Sixth%20Form%20College%3C%2FP%3E%3CP%3ECambridge%2C%20UK.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jan 28 2019 10:29 AM
Updated by: