I'm wondering what I've gotten into and how to get out of this catch-22. We're migrating our CM 2007, with MDT 2010 task sequences over to CM 2012 R2 with MDT 2013 integrated.
I set up the first test migration job and selected to migrate one of our simpler OS deployment task sequences. The job migrated everything except the task sequence itself. From what I'm finding is that it failed because it is an MDT 2010 integrated TS. All of the info I find though is for migrating to CM 2012 and say to upgrade my original task sequence to MDT 2012 integration before attempting to migrate them. But, since MDT 2012 is not supported with CM 2012 R2, wont that fail as well? I cannot upgrade my original task sequences to MDT 2013 because that doesn't support CM 2007. How should I migrate my task sequences from CM 2007 over to CM 2012 R2? Thanks Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCTS, MCITP, MCSA [Profile<https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/profile>] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb [Description: Description: Description: Description: Description: Description: Description: win7logoTiny]Microsoft Support for Windows XP ends April 2014! Click here to find out more about Windows 7<https://processmgt.mcit.med.umich.edu/sites/mcit/customer/applicationsoftware/Pages/Windows7.aspx>! ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
<<inline: image001.png>>
