%3CLINGO-SUB%20id%3D%22lingo-sub-274287%22%20slang%3D%22en-US%22%3EMDT%208450%20Now%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-274287%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Dec%2021%2C%202017%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20The%20Microsoft%20Deployment%20Toolkit%20(MDT)%2C%20build%208450%2C%20is%20now%20available%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D54259%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Microsoft%20Download%20Center%20%3C%2FA%3E%20.%20This%20update%20supports%20the%20Windows%20Assessment%20and%20Deployment%20Kit%20(ADK)%20for%20Windows%2010%2C%20version%201709%2C%20available%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fwindows%2Fhardware%2Fwindows-assessment-deployment-kit%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Microsoft%20Hardware%20Dev%20Center%20%3C%2FA%3E%20(adksetup.exe%20file%20version%2010.1.16299.15).%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Here%20is%20a%20summary%20of%20the%20significant%20changes%20in%20this%20build%20of%20MDT%3A%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3ESupported%20configuration%20updates%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3EWindows%20ADK%20for%20Windows%2010%2C%20version%201709%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EWindows%2010%2C%20version%201709%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EConfiguration%20Manager%2C%20version%201710%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EQuality%20updates%20(titles%20of%20bug%20fixes)%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3EWin10%20Sideloaded%20App%20dependencies%20and%20license%20not%20installed%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3ECaptureOnly%20task%20sequence%20doesn't%20allow%20capturing%20an%20image%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EError%20received%20when%20starting%20an%20MDT%20task%20sequence%3A%20Invalid%20DeploymentType%20value%20%22%22%20specified.%20The%20deployment%20will%20not%20proceed%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EZTIMoveStateStore%20looks%20for%20the%20state%20store%20folder%20in%20the%20wrong%20location%20causing%20it%20to%20fail%20to%20move%20it%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3Exml%20contains%20a%20simple%20typo%20that%20caused%20undesirable%20behavior%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EInstall%20Roles%20%26amp%3B%20Features%20doesn't%20work%20for%20Windows%20Server%202016%20IIS%20Management%20Console%20feature%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EBrowsing%20for%20OS%20images%20in%20the%20upgrade%20task%20sequence%20does%20not%20work%20when%20using%20folders%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EMDT%20tool%20improperly%20provisions%20the%20TPM%20into%20a%20Reduced%20Functionality%20State%20(see%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4018657%2Ftpm-is-in-reduced-functionality-mode-after-successful-deployment-of-wi%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20KB%204018657%20%3C%2FA%3E%20for%20more%20information)%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EUpdates%20to%20ZTIGather%20chassis%20type%20detection%20logic%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EUpgrade%20OS%20step%20leaves%20behind%20SetupComplete.cmd%2C%20breaking%20future%20deployments%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EWindows%2010%20ADK%201607%20and%20later%20UEFI%20boot%20issue%20on%20some%20hardware%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EIncludes%20updated%20Configuration%20Manager%20task%20sequence%20binaries%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20See%20the%20following%20post%20on%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fmsdeployment%2F2015%2F12%2F22%2Fhow-to-get-help-with-mdt%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20How%20to%20get%20help%20with%20MDT%20%3C%2FA%3E%20.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EFrequently%20Asked%20Questions%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20In%20anticipation%20of%20some%20questions%20that%20you%20may%20have%20about%20this%20release%20(or%20MDT%20in%20general)%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Q%3A%20%3C%2FSTRONG%3E%20The%20Inevitable%20Current%20Branch%20Versioning%20Soup%20Question%3B%20some%20variation%20of%2C%20%E2%80%9Cis%20this%20only%20supported%20with%20ADK%2FWin10%2FSCCM%20version%20X%E2%80%9D%3F%20%3CBR%20%2F%3E%20%3CBR%20%2F%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.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EQ%3A%20%3C%2FSTRONG%3E%20When%20is%20the%20next%20planned%20release%20of%20MDT%3F%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We%20do%20not%20currently%20have%20a%20timeframe.%20We%20will%20release%20any%20tactical%20changes%20as%20needed%20which%20may%20be%20required%20to%20support%20new%20builds%20of%20Windows%2010%20or%20Configuration%20Manager.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EQ%3A%20%3C%2FSTRONG%3E%20Is%20this%20the%20last%20release%20of%20MDT%3F%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20No%2C%20we%20will%20continue%20to%20iterate%20and%20invest%20in%20the%20product.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%E2%80%94%20Aaron%20Czechowski%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-274287%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Dec%2021%2C%202017%20The%20Microsoft%20Deployment%20Toolkit%20(MDT)%2C%20build%208450%2C%20is%20now%20available%20on%20the%20Microsoft%20Download%20Center.%3C%2FLINGO-TEASER%3E
First published on TECHNET on Dec 21, 2017
The Microsoft Deployment Toolkit (MDT), build 8450, is now available on the Microsoft Download Center . This update supports the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1709, available on the Microsoft Hardware Dev Center (adksetup.exe file version 10.1.16299.15).

Here is a summary of the significant changes in this build of MDT:

  • Supported configuration updates

    • Windows ADK for Windows 10, version 1709

    • Windows 10, version 1709

    • Configuration Manager, version 1710



  • Quality updates (titles of bug fixes)

    • Win10 Sideloaded App dependencies and license not installed

    • CaptureOnly task sequence doesn't allow capturing an image

    • Error received when starting an MDT task sequence: Invalid DeploymentType value "" specified. The deployment will not proceed

    • ZTIMoveStateStore looks for the state store folder in the wrong location causing it to fail to move it

    • xml contains a simple typo that caused undesirable behavior

    • Install Roles & Features doesn't work for Windows Server 2016 IIS Management Console feature

    • Browsing for OS images in the upgrade task sequence does not work when using folders

    • MDT tool improperly provisions the TPM into a Reduced Functionality State (see KB 4018657 for more information)

    • Updates to ZTIGather chassis type detection logic

    • Upgrade OS step leaves behind SetupComplete.cmd, breaking future deployments

    • Windows 10 ADK 1607 and later UEFI boot issue on some hardware

    • Includes updated Configuration Manager task sequence binaries




See the following post on How to get help with MDT .



Frequently Asked Questions

In anticipation of some questions that you may have about this release (or MDT in general):

Q: The Inevitable Current Branch Versioning Soup Question; some variation of, “is this only supported with ADK/Win10/SCCM version X”?

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.

Q: When is the next planned release of MDT?

We do not currently have a timeframe. We will release any tactical changes as needed which may be required to support new builds of Windows 10 or Configuration Manager.

Q: Is this the last release of MDT?

No, we will continue to iterate and invest in the product.



— Aaron Czechowski