Microsoft has abruptly pulled the plug on the venerable Microsoft Deployment Toolkit (MDT), sending any administrators still clinging to the platform scrambling for alternatives.
Redmond retired MDT with "immediate" notice. This means there won't be any more fixes, support, updates, security patches, or enhancements. Microsoft also warned that "MDT download packages might be removed or deprecated from official distribution channels."
It also means that any hope of future compatibility updates for new Windows releases are dashed, although existing deployments should continue to work for the time being.
MDT has survived for many years and is a set of free tools for deploying Windows operating systems and applications. It has, however, been on the chopping block for some time. Microsoft announced deprecation in December 2024, and many affected administrators will have already migrated to an alternative. The house that Gates built recommends Windows Autopilot or Configuration Manager Operating System Deployment (OSD) as alternatives.
We asked Microsoft the reason behind the "immediate retirement notice" but the company has yet to explain. A user on social media wrote: "there are security flaws that Microsoft chose not to fix. Instead they retired the product immediately."
Other affected users noted that "Autopilot and config manager seem way overkill."
One suggested three reasons why MDT had to go: "It is free, it does not invade the customer's privacy (no telemetry), it does not force customers to Azure cloud." Ouch.
MDT is undoubtedly a platform from a bygone era at Microsoft. It dates back more than two decades to a time before Azure. It supports Zero-touch (ZTI) and User-driven (UDI) installations. The former is fully automated, while the latter requires a user to respond to prompts during installation.
It also supports Lite-touch installations (LTI) where operating system software can be installed via bootable media, such as a DVD or USB drive.
The writing has been on the wall for MDT. In addition to putting it on the deprecation list, Microsoft has not made many meaningful updates to the service, so its retirement is not particularly surprising, even if the immediate nature will raise a few administrator eyebrows.
As one user noted: "Not entirely unexpected, but that definitely closes a chapter on some of my early-career knowledge." ®
Source: The register