Allow MDT steps to be migrated when using the wizard
The migration wizard is not able to migrate "third-party" steps in a task sequence, including Microsoft Deployment Toolkit steps. For many of my customers this a huge blocker to have a smooth migrating experience from test to the production environment. MDT steps should not be seen as "third-party" and be migrated.
Updated by bobmn for sangeev/OSD
Scott Williams commented
Boosting this after recent twitter conversations.
It would be good to have better handling for "third party" extensions in task sequences. Maybe rather than just not working it could create a "placeholder action" instead.
As for MDT, it would be really good if ConfigMgr natively support MDT extensions