ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide Part 32: Migration from 2007

ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide Part 32: Migration from 2007

Back to main menu

Part 32 of my ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide describes how to carry out a side by side migration from CM07 (note that there is no in-place migration). Please follows the links to browse to the sections.


Some Design Considerations

You must have ConfigMgr 2007 SP2 before you can migrate to ConfigMgr 2012. If you have SP1 you must do an in-place upgrade to SP2 before you are eligible for a migration.
(The R2/R3 levels have nothing to do with this. It is purely dependent on SP2. ConfigMgr 2007 R2 required that SP1 or SP2 were already installed on your site server. R3 required SP2. Therefore an infrastructure could be at R2 and still not eligible for migration).

You can do an in-place upgrade of a Config Mgr 2007 secondary site to a 2012 DP only.

If you need a 2012 secondary site you will have to deploy a new one. However there are less reasons to require a secondary site in ConfigMgr 2012
1. You can now throttle bandwidth with 2012 DP and even 2012 clients
2. You typically need a 2012 secondary site only if you have more than 500 clients.

Pre-migration tasks

Source Hierarchy

Collection/Object migration

Share Distribution Points

Upgrade Clients

Upgrade Distribution Points 

Change Driver Source Location

Post-Migration Steps

Package Conversion 

Objects that can be migrated from ConfigMgr 2007 to ConfigMgr 2012.

• Boundaries  - the migration process will create each boundary and automatically create a boundary group
• Collections - the collections that are selected for migration are scanned to see if there are any software packages, advertisements, software updates, and task sequences associated with them. These can then be selected for migration with the collection. The migration of an advertisement is only an option during the collection migration.
• Software Packages - All package options and programs are maintained during migration. 
• Virtual Application Packages
• Software Update Deployment Packages - classifications and products must match the ConfigMgr 2007 environment and be successfully synchronized. If a single update is missing from an entire update package the migration of that package will fail. 
• Software Update Deployment Templates 
• Software Update Lists - The migration process will convert Software Update Lists into Software Update Groups and a Software Update Deployment will be converted into a Deployment and corresponding Update Group.
• Operating System Driver Packages
• Operating System Drivers
• Operating System Images
• Operating System Install Packages
• Task Sequences
• DCM Configuration Baselines - ConfigMgr 2007 Configuration Packs can be imported into ConfigMgr 2012. The Configuration pack is automatically converted to be compatible.
• DCM Configuration Items
• Asset Intelligence Catalog - There are no significant changes to either Asset Intelligence or Software Metering. Therefore, the migration of these two categories is basically seamless and will appear in ConfigMgr 2012 just as they did in 2007.
• Asset Intelligence Hardware Requirements
• Asset Intelligence Software List
• Software Metering Rules

What CAN'T be migrated

The following objects must be recreated at the SCCM 2012 hierarchy:

• Queries, Security rights and instances for the site and objects, SCCM reports (Web or SQL based), client inventory and history data, AMT client provisioning data, and files in the client cache.
• Software Updates: All custom updates, locally published SCUP updates, will need to be republished as they cannot be migrated.
• Update Templates will need to have the duration settings reconfigured as it does not migrate.