MDT Package SCCM: Creating One Within Configuration Manager

Integrating Microsoft Deployment Toolkit (MDT) into SCCM significantly expands what your task sequences can do — adding a large set of extra task sequence variables and steps that plain SCCM task sequences don’t have on their own. Before you can use any of that inside your own task sequences, you need to create the MDT package.

Creating the MDT Package

1. Confirm MDT is already integrated into your SCCM console (this is a one-time setup step via the MDT installer’s “Configure ConfigMgr Integration” option).
2. In the SCCM console, right-click Task Sequences and choose Create MDT Task Sequence.
3. Run through the wizard — any valid selections will do, since this task sequence itself can be deleted afterward. Its real purpose is that the wizard creates the MDT Toolkit Package for you as part of the process, if one doesn’t already exist.

Using It in Other Task Sequences

Once the MDT package exists and has been distributed to your distribution points, any task sequence can reference it via the MDT-specific steps under the task sequence editor’s toolkit section — select Use Toolkit Package and point it at the package you just created. This unlocks the MDT-specific steps (like Gather, Apply Driver Package via database queries, and the extended ZTI variable set) inside your regular SCCM task sequences.

Important Update: MDT Integration Is No Longer Supported (2026)

This is worth reading before you follow the steps above on a new setup. Microsoft retired MDT in early 2026, and separately from that general retirement, Microsoft’s own guidance now states specifically that MDT integration with Configuration Manager is no longer supported — and actively recommends removing MDT task sequence steps and MDT-ConfigMgr integration entirely, warning that keeping it in place risks task sequence corruption and modification failures going forward. If you already have MDT integrated into SCCM and it’s working, Microsoft’s position is that it will continue to function for now, but building new MDT-dependent task sequences or adding fresh MDT integration to a ConfigMgr environment today is no longer something Microsoft supports or recommends. For new deployment task sequence work, look at ConfigMgr’s native (non-MDT) task sequence steps or Windows Autopilot instead.

Resources

• Microsoft