On January 6, 2026, Microsoft retired MDT with immediate effect and pulled the installer from the Download Center the same day. No deprecation period, no final release. If you didn’t already have the MSI saved somewhere, you now have to get a little creative just to install the product you’re trying to migrate away from. Hint: The Internet Archive.
That changed the conversations I’m having with customers. Nobody is really asking if they should move away from MDT anymore. The question is how much work it’s going to be.
For the operating system deployment and task sequence logic, the answer is usually: less than you think. DeployR gives you a familiar task sequence engine, conditions, nested task sequences, error handling, and most of the design carries over quite nicely.
Then someone expands the Applications node and there are maybe 240 applications in there. That’s usually the part nobody planned for. So, I wrote a tool for it.
TL;DR: It’s a single PowerShell script with a UI that reads your MDT deployment share, figures out which applications can be migrated automatically and which ones need a human decision, copies the content into a proper local source structure, and creates them as Application content items in DeployR with the version set to Active.
Note: This script supports both DeployR Enterprise and the free DeployR Community.
It also has a dry-run mode and CSV export, so you can survey the deployment share before changing anything.
Try it out, and let me know what you think: https://github.com/DeploymentResearch/DRFiles/blob/master/Scripts/DeployR/Convert-MDTAppsToDeployR.ps1
Johan, This worked great thank you for all your hard work.
Nice Tool