Note in addition to the answers by Torsten and Jorgen, that MDT when integrated into ConfigMgr functions as an add-on. Thus it is simply supplementing existing functionality, not replacing it.
So, assuming MDT integration into ConfigMgr:
Can you create a TS with extended functionality provided by MDT?
- Yes, absolutely. Although sometimes referred to as an MDT TS at this point, it is not really; it is simply a native ConfigMgr OSD TS with additional functionality provided by MDT.
Can you directly use or migrate an existing task sequence from stand-alone MDT?
- No. You can manually migrate it and create an equivalent TS, but there is no way to directly import or automatically migrate a TS from stand-alone MDT.
Can you use anything created in the MDT workbench?
- No. As eluded to, these tools create two different task sequences. Only standalone MDT TSes can use things defined in the MDT workbench. ConfigMgr TSes leverage packages and applications created in ConfigMgr. The one exception is the MDT database which
is traditionally created (and potentially managed) in the MDT workbench -- OSD in ConfigMgr can use this (although that's not really something reflected in the actual TS but rather implemented by the MDT scripts).
Can a ConfigMgr TS use MDT variables?
- Yes. Once you create a TS in ConfigMgr using the MDT integration, the bulk of the scripts used by MDT stand-alone are also used in the TS. It's these scripts that provide access to the MDT DB as mentioned above as well as MDT variables which are accessible
to the ConfigMgr task sequence as task sequence variables.