Late on the response, but that's exactly what you need to do: delete the MDT-related actions and migrate it over. You can then at least use it for reference, and if the TS is long and/or complex you can cut and paste the tasks/groups into the new TS.
-Phil _________________________________________________________________ Phil Schwan | Technical Specialist, Enterprise Windows Services Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. [linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Tuesday, January 21, 2014 8:05 AM To: '[email protected]' Subject: [MDT-OSD] RE: Migrating Task Sequences from CM 2007 to CM 2012 R2 I fully expect to recreate the task sequences. I am just trying to at least get the original ones over so that I can copy/paste my custom actions and logic, and try to avoid re-inventing the wheel. I tried disabling the actions first, hoping that it was the package reference that was tripping it up, but that didn't work. I deleted the MDT actions (all of the "Use Toolkit Package" and "Gather" steps) and that worked. That should get me what I need. Thanks for the info Daniel. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, January 21, 2014 7:52 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Migrating Task Sequences from CM 2007 to CM 2012 R2 It's probably best to recreate them, even if you somehow get them to migrate successfully you lose all the functionality you would get with ConfigMgr 2012 R2/MDT 2013 because the backend XML isn't there. http://technet.microsoft.com/en-us/library/gg712672.aspx#Plan_migrate_OSD It does look like it is possible, but again I wouldn't recommend it. http://social.technet.microsoft.com/Forums/en-US/293935a6-37c4-4277-b6a7-dd6b3b2f8738/cant-migrate-task-sequences-that-contain-mdt-tasks Looks like it's not possible to migrate any MDT integrated task sequences though. You have to remove those steps first. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Tuesday, January 21, 2014 7:43 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Migrating Task Sequences from CM 2007 to CM 2012 R2 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 The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments.
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
<<inline: image005.jpg>>
<<inline: image006.png>>
