Sure, I'm copying the mailing list on here in case anyone else wants to chime in with their experiences.
One of the big issues we found was that running large migration jobs, it was spotty what would come over. When you're doing a collection migration from a 2007 site it is supposed to grab all the dependent items. But we found that there would be missing items such as packages referenced in a Task Sequence. Ultimately the time that the migration was supposed to save us was wasted in double checking each item. Also you'll want to pay special attention to any collection rules with a query that were limited, it will attempt to make the limiting collection on that query rule the limiting collection for the collection itself. Also beware of collections that have a mixture of query rules and direct memberships, that's just dirty anyways, but due way the limiting collections work in 2012, you could have bad results in your collections. On top of the migration tool you might be tempted to run the package conversion tool. That also has problems with inconsistencies in the checkboxes that get set such as the user interaction in the deployment types we found it setting contradictory settings that would cause it to never install, had to go back and check all those too. From: [email protected] [mailto:[email protected]] Sent: Thursday, March 27, 2014 11:46 AM To: Krueger, Jeff Subject: Tips for dealing with Packages that won't migrate >> From MyItForum <<< Hello Jeff I came across this thread on MyItForum and was intrigued. Based on Microsoft's history an "anecdotal" statement like this would normally suffice but when we were recently discussing our migration plans I mentioned this would be "yet another good time" to learn from our mistakes and start "clean". Well, with ~8500 packages, ~20,000 collections, 140,000 managed systems, etc. I am very concerned with any "migration" scenario. Anyway, if you have some time could you spell out some additional "gory details" regarding your experience with the migration tool? It would be helpful in my quest to forgo this tool and start with a clean system. Thanks for your time here. Henry E. WILSON Infrastructure Management│ Automation Center GIS - Global Infrastructure Services Office +1 908-981-3288 | Mobile +1 610.724.1169 | Home +1 215.482.1524 | Fax +1 908.635.5858 55 Corporate Drive - Building D-3 Room 3207 - Bridgewater, NJ 08807 [One IS-6] u Please consider the environment before printing this email From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Wednesday, January 08, 2014 9:57 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Tips for dealing with Packages that won't migrate Only pointer I can give is run away from the migration tool, it causes nothing but headaches. It's far cleaner to just create a new application in 2012 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Stephen Owen Sent: Wednesday, January 8, 2014 9:38 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Tips for dealing with Packages that won't migrate Hi guys, I'm trying to migrate packages over and a number of package migrations just fail with no discernible cause. Anyone have any pointers? Even the Status Messages for the Component have relatively no information. When I look at the migmctrl.log file, things are less than clear: [MigMCtrl]: WAIT 3 event(s) for 60 minute(s) and 0 second(s). [Worker]: Impersonation is about to start ... [Worker]: Impersonation succeed, current user identity is: contosoNA\sowen Connection string = Data Source=CHLTMS01;Initial Catalog=SMS_CCP;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=True;Application Name="Migration Manager". [Worker]: Impersonation is reverted. [Worker]: Detected source collation SQL_Latin1_General_CP1_CI_AS [Worker]: Detected destination collation SQL_Latin1_General_CP1_CI_AS [Worker]: ========== Start sub migration job to migrate from chltms01.ent.contoso.com<https://urldefense.proofpoint.com/v1/url?u=http://chltms01.ent.contoso.com&k=DRaZFQufJSh%2Bz2CJu01vGA%3D%3D%0A&r=G7Rp%2FyVEkz9AB1xRQWzmh1E0dbzzZxlFIY6QTWSRqzc%3D%0A&m=TWo0gdxiAOYWU58tbiAkWjSW5vd3Xv2FNppTxlOedRQ%3D%0A&s=f79267df8e199fbc868cb530fbb925ef84acafe771dbd761a5459462a8ca5d88> (CCP) ========== [Worker]: Total object weight: 80 [Worker]: Start Migrating AppV Objects [Worker]: End Migrating AppV Objects [Worker]: Start Migrating AI Objects [Worker]: End Migrating AI Objects [Worker]: Start Migrating Boundaries Per Site [Worker]: End Migrating Boundaries Per Site [Worker]: Start migrating regular objects. [Worker]: MigrateObjects.GetExecutionPlan: sorting 8 objects [Worker]: Beginning SoftwareLibrary migration [Worker]: Migrating collections ... [Worker]: Migrating other objects ... [Worker]: End migrating regular objects. [Worker]: Serialization summary for migrating from chltms01.ent.contoso.com<https://urldefense.proofpoint.com/v1/url?u=http://chltms01.ent.contoso.com&k=DRaZFQufJSh%2Bz2CJu01vGA%3D%3D%0A&r=G7Rp%2FyVEkz9AB1xRQWzmh1E0dbzzZxlFIY6QTWSRqzc%3D%0A&m=TWo0gdxiAOYWU58tbiAkWjSW5vd3Xv2FNppTxlOedRQ%3D%0A&s=f79267df8e199fbc868cb530fbb925ef84acafe771dbd761a5459462a8ca5d88> (CCP) to chltmcm1.ent.contoso.com<https://urldefense.proofpoint.com/v1/url?u=http://chltmcm1.ent.contoso.com&k=DRaZFQufJSh%2Bz2CJu01vGA%3D%3D%0A&r=G7Rp%2FyVEkz9AB1xRQWzmh1E0dbzzZxlFIY6QTWSRqzc%3D%0A&m=TWo0gdxiAOYWU58tbiAkWjSW5vd3Xv2FNppTxlOedRQ%3D%0A&s=63bffdbf866add1ba8bd53710471a5a9c805e488e2f95aa0c11f58d7267e6cb3> (CAS): [Worker]: ========== End sub migration job to migrate from chltms01.ent.contoso.com<https://urldefense.proofpoint.com/v1/url?u=http://chltms01.ent.contoso.com&k=DRaZFQufJSh%2Bz2CJu01vGA%3D%3D%0A&r=G7Rp%2FyVEkz9AB1xRQWzmh1E0dbzzZxlFIY6QTWSRqzc%3D%0A&m=TWo0gdxiAOYWU58tbiAkWjSW5vd3Xv2FNppTxlOedRQ%3D%0A&s=f79267df8e199fbc868cb530fbb925ef84acafe771dbd761a5459462a8ca5d88> (CCP) ========== [Worker]: ==================== Object Migration Job 21 Ended ==================== ERROR: [Worker]: System.ArgumentOutOfRangeException: Length cannot be less than zero. Parameter name: length at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.ConfigMgr.SMS_Program.get_DependentPackage() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.ConfigMgr.SMS_Package.<get_DependentObjects>d__0.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Services.Util.CatalogIterator.<IteratePrerequisites>d__16.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Services.Util.CatalogIterator.<Iterate>d__b.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Services.Util.Iterator`2.<get_Output>d__1.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Services.LibraryCatalog.IterateService.<get_ExecutionPlan>d__2.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Adapters.ObjectManagerBase.<GetImportPlan>d__6.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Library.<GetImportPlan>d__2.MoveNext() at Microsoft.ConfigurationManagement.Migration.MigrateObjects.<GetExecutionPlan>d__14.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachErrorHandler>d__6`1.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachErrorHandler>d__6`1.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ObjectMigrationJob.<get_ExecutionPlan>d__f.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachErrorHandler>d__6`1.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.MultiSourceSiteObjectMigrationJob.<MigrateSite>d__1e.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.MultiSourceSiteObjectMigrationJob.<MigrateSubHierarchy>d__2d.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.MultiSourceSiteObjectMigrationJob.<get_ExecutionPlan>d__e.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.Job`1.ExecuteNext() [Worker]: Start processing status changed event for MIG_Job.ID=21 [Worker]: Set the schedule item 21 end time [Worker]: Set the schedule item 21 status to Failed [Worker]: End processing status changed event for MIG_Job.ID=21 [Worker]: Disposing Job 21 [Worker]: Removing Job 21 from job manager. [Worker]: Removing the Job with Id 21. [Worker]: Disposing worker [Worker]: Disposing current site connection ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = Unknown error 0x80131502, 80131502 ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = Unknown error 0x80131502, 80131502 Connection string = Data Source=(local);Initial Catalog=CM_CAS;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager". [MigrationManager]: Start two step scheduling for MIG_SiteMapping [MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ... [MigrationManager]: Step 2. Query the first item in order of DateNextRun ... [MigrationManager]: The item MIG_SiteMapping 1 is scheduled to run at 01/08/2014 15:07:13 UTC, 01/08/2014 16:07:13 Local Time, sleep for 00:40:53.0550000. ________________________________ 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<https://urldefense.proofpoint.com/v1/url?u=http://www.henryford.com&k=DRaZFQufJSh%2Bz2CJu01vGA%3D%3D%0A&r=G7Rp%2FyVEkz9AB1xRQWzmh1E0dbzzZxlFIY6QTWSRqzc%3D%0A&m=2Fa%2Bl2SqlgZ3A2KJYtBil4Spsi95o6DMBfa2vPZXbik%3D%0A&s=09d290dd34cddc6ac5d033786925e1e5555cb943381c2ac78de888f40735ff93> 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.
<<inline: image001.jpg>>
