No problem, I'm just trying to anticipate the amount of suck this is going to be. We were looking at doing the migration first to a sandboxed environment to validate everything and clean up first. Then bring everything over to production and then upgrade clients from our 2007 environment to our prod 2012 environment.
According to the TechNet article<http://technet.microsoft.com/en-us/library/gg712283.aspx> about client migration, the execution history is retained on the client itself, so I'm hoping that the execution history will match up with the migrated collections and packages and deployments. This could be painful if that is not the case. From: [email protected] [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Tuesday, September 24, 2013 3:32 PM To: [email protected] Subject: [mssms] RE: Collection Migration from 2012 to 2012 Sorry, I overlooked that part of your original request. Unfortunately, no...you cannot to a 2012 to 2012 Collection Migration that preserves execution history. -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Tuesday, September 24, 2013 3:25 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Collection Migration from 2012 to 2012 If we do an object migration from 2012 to 2012 will client execution history come all the way across, or do we lose that in the middle step from 2007>2012dev>2012prod ? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Tuesday, September 24, 2013 3:00 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Collection Migration from 2012 to 2012 The only supported source hierarchy for Collection Migration JOB is ConfigMgr 2007: http://technet.microsoft.com/en-us/library/gg712285.aspx#About_Collection_Migration_ That said, if you create an Object Migration job, I believe you can select Collections from the Object types box. -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]> [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Tuesday, September 24, 2013 2:44 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Collection Migration from 2012 to 2012 Looking at doing a migration from a dev 2012 enrivonment to production 2012 environment and the option to do a collection migration is not available. Is function not possible, or is there some configuration we need to be aware of to enable this. If we cannot do a collection migration and take all the associated objects this would be a huge pain for us. Jeff Krueger ________________________________ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com<http://www.henryford.com> for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us. ________________________________ 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>>
