Microsoft is trying desperately to move away from placing major version numbers on its products. As seen with Windows 10 and also System Center Configuration Manager, a new release of the Microsoft Deployment Toolkit (MDT) also attempts to eliminate major version numbers.
You may notice that we are not tagging this release with a year or update version. To better align with the current branches of Windows 10 and Configuration Manager, and to simplify the branding and release process, we are now just referring to it as the “Microsoft Deployment Toolkit”, using the build number to distinguish each release.
Build 8443 of MDT is now available HERE on the Microsoft Download Center. The update also requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607, which can be found HERE on the Microsoft Hardware Dev Center.
Microsoft also states in a new FAQ that because of the change in versioning customer shouldn’t expect MDT releases to be as frequently as other products and that there’s no date to be announced when to expect a new build. MDT will not necessarily match the same cadence as System Center Configuration Manager, though it will support both Current Brand and Long Term Servicing Branch.
Here’s what’s new in this version:
Supported configuration updates
- Windows ADK for Windows 10, version 1607
- Windows 10, version 1607
- Windows Server 2016
- Configuration Manager, version 1606
- Deployment Wizard scaling on high DPI devices
- Johan’s “uber bug” for computer replace scenario
- Multiple fixes for the Windows 10 in-place upgrade scenario
- Several fixes to Configure ADDS step
- Removed imagex/ocsetup dependencies, rely solely on DISM
- Includes the latest Configuration Manager task sequence binaries (version 1606)
Looking for an awesome, no-nonsense technical conference for IT Pros, Devs, and DevOps? IT/Dev Connections kicks off in San Francisco in 2017!