Jason is right. If your MDT solution works and is “solid” then you can use that to model your OSD solution. It stinks that there is no way to directly import or even transfer actions between MDT and SCCM, but if you’re MDT process works then you’ve already done the hard part. It will just be a matter of manually recreating the steps in an SCCM OST task sequence.
Mike From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, March 31, 2016 2:23 PM To: [email protected] Subject: [MDT-OSD] RE: Transitioning from MDT to OSD There is no way to import a stand-alone MDT TS into ConfigMgr. Effectively though, they do the exact same thing, with slight differences, so there’s no reasons you couldn’t manually transfer the existing MDT TSes into ConfigMgr and have it work (with some minor adjustments). There’s no reason to reinvent the wheel here. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bain.John Sent: Thursday, March 31, 2016 1:15 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Transitioning from MDT to OSD Hello, I currently learning about SCCM 2012 and OSD deployments and I was wondering is it worth importing my already developed MDT solution into SCCM or should I recreate the MDT deployment as an OSD deployment. Which would be the proper SCCM way ? John ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
