Microsoft Deployment Toolkit (MDT) alternative

MDT alternative: keep deploying Windows on-premises, bare metal, with MasteriDesk

Microsoft retired MDT in January 2026: no more updates, fixes or support. For IT teams that still need to install blank devices on their own network, MasteriDesk covers the essentials: PXE boot compatible with UEFI and legacy BIOS, standalone USB media, automatic Dell, HP and Lenovo drivers, BIOS updates and BitLocker encryption, on a WinPE, WMI and DISM engine.

01End of MDT

End of MDT: what the Microsoft Deployment Toolkit retirement means for your deployments

For years, MDT was the free go-to tool for automating Windows installation. Its retirement leaves a need that has not gone away: preparing new devices, or reinstalling existing ones, on-premises.

  • No more fixes or support. Microsoft no longer releases updates or security fixes for MDT, and no longer supports it.
  • Installations still run, with no guarantee. Existing MDT deployments keep working, but their compatibility with future versions of Windows and the ADK is no longer validated.
  • No direct migration path. Microsoft offers no in-place upgrade to another tool: your deployment chain has to be rebuilt.
  • Microsoft alternatives built for other scenarios. Microsoft points to Windows Autopilot, which configures devices shipped with Windows preinstalled through Intune, or to Configuration Manager (OSD), which requires a full infrastructure to run.
  • Bare metal is still needed. Blank devices, reinstalls after an incident, remote sites, data that must stay in-house: many organisations still need to install Windows themselves, on their own network.
See all features
MDT retirement timeline

December 2024: Microsoft announces the deprecation of MDT. January 2026: retirement takes effect, with no updates, fixes or support. Source: Microsoft Learn.

The MasteriDesk answer

A relay installed on your network, a web portal, and your devices start from scratch: GPT-partitioned disk, Windows image, drivers, BIOS, domain, activation and BitLocker, tracked in 9 steps.

02Comparison

MDT or MasteriDesk: a point-by-point comparison

What you used to do with MDT, often paired with WDS, and what MasteriDesk does instead.

CriterionMDT (+ WDS)MasteriDesk
StatusRetired by Microsoft: no updates, no fixes, no supportMaintained and updated by LogoSapience, a French software publisher
ConsoleDeployment Workbench, installed on a Windows serverWeb portal in the SecuriDesk panel, in a sovereign cloud or on your premises
Network bootPXE usually provided by WDS, to install and configureLocal probe as PXE server or DHCP proxy, UEFI and legacy BIOS, no change to DHCP
DriversOut-of-Box Drivers packages to download, sort and keep up to dateSynchronised Dell, HP and Lenovo catalogue; package chosen by model (WMI) and injected by DISM
BIOS, TPM and Secure BootScripts and manufacturer utilities to add to task sequencesBuilt in: BIOS updated, TPM 2.0 and Secure Boot enabled, battery profile
BitLockerTask sequence steps to configureEnabled after installation, recovery key backed up to Active Directory
MonitoringMonitoring to enable on the deployment share9 steps per device, detailed log, targeted retry of failures, history exportable to CSV
Remote sitesDeployment shares to replicate (DFS-R, linked shares)Local cache: one download per model and per site; USB media for sites without PXE
After installationOut of scopeSecuriDesk takes over: applications, patches, updates and security analysis

MDT was free; MasteriDesk is licensed per device, on quotation. See pricing.

03Migration

Migrating from MDT to MasteriDesk in four steps

There is no in-place upgrade from MDT: the switch is prepared, then validated on a scope you choose.

  1. Take stock of what you have

    Deployment shares, WIM images, task sequences, drivers and scripts: identify what is still used and what can go.

  2. Install the local probe

    A relay on your network that connects to the portal: no inbound port to open on your firewall.

  3. Bring over images and standards

    Import your ISOs or Sysprep reference images, then set licences, BIOS passwords and encryption once and for all. Dell, HP and Lenovo drivers arrive on their own.

  4. Pilot, then roll out

    Validate the full chain on one site or a batch of devices, in your own environment, before extending it to your whole fleet.

25devices installed at the same time, adjustable
0inbound ports to open on your network
9 stepstracked in real time, device by device
< 20 mintarget time to prepare a device, versus 2 hours
Frequently asked questions

FAQ: replacing MDT with MasteriDesk

Does MDT still work after its retirement?

Yes. According to Microsoft, existing installations keep working. However, MDT no longer receives updates, fixes or support, and its compatibility with future versions of Windows and the ADK is no longer ensured.

Why not just move to Windows Autopilot?

Autopilot customises devices shipped with Windows preinstalled and relies on Intune and Microsoft Entra ID. It does not deploy a system image to a blank disk. To reinstall devices on-premises, without depending on the Microsoft cloud, MasteriDesk covers that need.

Do I need to keep WDS for PXE boot?

No. The MasteriDesk local probe acts as a PXE server or DHCP proxy, compatible with UEFI and legacy BIOS, without changing your existing DHCP server.

Can I reuse my Windows images?

Yes. MasteriDesk deploys .WIM or .ISO images, as a clean install or by cloning a reference image prepared with Sysprep, to a GPT-partitioned disk.

What happens to my MDT task sequences?

With MasteriDesk, they give way to a three-step wizard (image and licences, drivers and hardware, domain and BitLocker) and to standards defined once. Application installs, scripts and policies are then handled by SecuriDesk.

How do I equip a site without a PXE server?

From the Library, you create standalone USB media for a target model, protected by a password whose expiry you set, then send it to the local technician.

Which hardware does MasteriDesk support?

Drivers for Dell, HP and Lenovo business ranges are retrieved automatically. The deployment engine, based on WMI and DISM, is brand-independent: for a custom-built PC or a consumer range, you import your own driver package.

Where are our files and BitLocker keys stored?

ISOs and drivers are downloaded by the relay at installation time, then deleted. BitLocker keys are backed up to your Active Directory, never on our side. The portal is hosted in a sovereign cloud or installed on your premises.

How much does MasteriDesk cost?

MasteriDesk is licensed per device; the price depends on the size of your fleet and the support you need. See pricing or request a quote.

Prepare for life after MDT, without disruption

Let’s talk about your current MDT setup and see together how MasteriDesk takes over your deployments, site by site.

MasteriDesk — an MDT alternative for bare-metal Windows deployment on-premises, over the network (PXE) or from USB media. Published by LogoSapience.