Regarding number one, I can look for a specific example when I get back to my desk but there are references all throughout Microsoft's documentation on the migration tool regarding using CM2012 as the source.
-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 Jason Wallace Sent: Tuesday, September 24, 2013 7:14 AM To: [email protected] Subject: [mssms] Migrating Objects from 2012 to 2012 Hello folks I am writing a process document on migrating objects from Test to UAT and UAT to PROD in SCCM 2012 SP1. I am planning to use the migration tool included in 2012 as this appears to work & some very kind folks on here have confirmed that it does. My testing also shows that this is the case. So, Diolch, Danke, Merci and Thanks so far. Just a couple of questions which I have so far though: 1. Support. As is often the case we need to provide a solution that is "supported" by Microsoft. Yes, I know that Microsoft would never not support a Premier customer etc. and can justify the use of the tool but I know that I shall be asked why the tool is a 2007 to 2012 tool and whether the use in 2012 to 2012 is supported. Has anyone managed to get a support statement on this please? 2. Other Objects. A couple of things won't be migrated - the SUP categories etc. Is there a kind soul who would be prepared to share an extract / import pair of scripts for this please? Thanks very much Jason ________________________________ 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: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
