← All work
Sustaining OS deployment through Microsoft's MDT end-of-life
Outcome: The client's OS deployment moved cleanly onto supported, SCCM-native tooling ahead of the end-of-life, on automation I built where the vendor offered none, sparing them a costly manual rebuild and turning a looming liability into a non-event.
The problem
A client's OS deployment ran entirely on Microsoft's Deployment Toolkit when Microsoft announced its end-of-life. There was no migration tool, no playbook, and no vendor path forward, just a deadline. Rebuilding the deployment logic by hand would have been slow, error-prone, and expensive, and doing nothing meant losing OS deployment the moment MDT went unsupported.
What I did
- Wrote PowerShell to read the MDT task-sequence logic end to end, its variables, scripts, and conditional flow, and reshape it into task sequences SCCM/MECM understood natively.
- Drove the conversion through native SCCM modules and WMI methods exposed only on the SCCM site servers, internals with no documented path for this kind of use, because no one had built it before.
- Validated parity across deployment scenarios before cutover, since the approach was novel and had nothing to check against.