Stephen,
I would tend to agree with Jeff's analysis. Just create new Application object definitions, along with the appropriate Deployment Type(s). Automate the process, and it won't be a big hassle. You might have to go back in and tweak some things, like Global Conditions and Detection Methods, but the initial automation will save you lots of time, and provide a future process for importing new Applications. After all, those tweaks are things you'd have to do anyway, since you're migrating from ConfigMgr 2007. In PowerShell, you'd use these commands, in the built-in ConfigurationManager PowerShell module: * New-CMApplication * Add-CMDeploymentType ps. I asked Phil to jump in, because he has had extensive experience migrating packages from ConfigMgr 2007. If you ask him, I bet he'd even tell you that he enjoyed it! *duck and cover* Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Wednesday, January 8, 2014 9:08 AM To: [email protected] Subject: RE: [mssms] Tips for dealing with Packages that won't migrate What does the migration job status console identify as migrated/failed? What specifically are you trying to migrate? I will usually break it up into multiple migration jobs based on the type of content being migrated. See if you can narrow it down a bit and go from there. -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 <http://www.projectleadership.net/> www.projectleadership.net Lead with Strategy. Leverage Technology. Deliver Results. <http://www.linkedin.com/in/philschwan> <https://twitter.com/philschwan> <http://myitforum.com/myitforumwp/author/philschwan> 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 <http://chltms01.ent.contoso.com> (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 <http://chltms01.ent.contoso.com> (CCP) to chltmcm1.ent.contoso.com <http://chltmcm1.ent.contoso.com> (CAS): [Worker]: ========== End sub migration job to migrate from chltms01.ent.contoso.com <http://chltms01.ent.contoso.com> (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.Config Mgr.SMS_Program.get_DependentPackage() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Config Mgr.SMS_Package.<get_DependentObjects>d__0.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Servic es.Util.CatalogIterator.<IteratePrerequisites>d__16.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Servic es.Util.CatalogIterator.<Iterate>d__b.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Servic es.Util.Iterator`2.<get_Output>d__1.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Servic es.LibraryCatalog.IterateService.<get_ExecutionPlan>d__2.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Adapte rs.ObjectManagerBase.<GetImportPlan>d__6.MoveNext() at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Librar y.<GetImportPlan>d__2.MoveNext() at Microsoft.ConfigurationManagement.Migration.MigrateObjects.<GetExecutionPlan >d__14.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachE rrorHandler>d__6`1.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachE rrorHandler>d__6`1.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ObjectMigrationJob.<get_E xecutionPlan>d__f.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachE rrorHandler>d__6`1.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.MultiSourceSiteObjectMigr ationJob.<MigrateSite>d__1e.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.MultiSourceSiteObjectMigr ationJob.<MigrateSubHierarchy>d__2d.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.MultiSourceSiteObjectMigr ationJob.<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. _____ 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.
<<image001.jpg>>
<<image002.jpg>>
<<image003.jpg>>
<<image004.jpg>>
