SCCM 2007 to SCCM 2012 migration

Some high level important points when migrating SCCM 2007 to SCCM 2012.

Migration from Config Manager 2007 to Configuration Manager 2012 is a side-by-side migration which means we need to build a new Configuration Manager 2012 hierarchy next to the current Configuration Manager 2007 hierarchy.

Terminology:

Source site: SCCM 2007 (The site you are migrating from)

Destination site: SCCM 2012 (The site you are migrating to)

The key steps and notes in migration process;

• Review the supported SCCM migration hierarchy from source to destination migration (Minimum source is SCCM 2007 SP2)
• Configure the migration (Linking the source and destination SCCM environments)
• Plan for a staged approach
• The source and destination sites must have unique site codes
• Set appropriate permissions (destination site need access to the source site objects and SMS provider read access)
• Review the firewall rules (To avoid any *unknowns*)
• Make sure that the data gathering completes successfully before starting migration jobs
• The migration of objects will be performed through three types of migration jobs;
• Collection Migration (Collections and related objects)
• Object Migration
• Previously migrated object migration (Migration Objects modified after migration job)
• Monitor all the data gathering or migration jobs under \Administration\Overview\Migration\Migration Jobs
• Detailed migration process can be viewed on SMS_MIGRATION_MANAGER component status
• Review migmctrl.log for migration status
• Migration may take few months based on the complexity of the environment
• Do not migrate packages which is not in use

Important Migration Rule:

• Don't break the existing source (SCCM 2007) environment
• Use unique site codes for source and destination

Objects not migrated using Microsoft Migration Utility:

- Queries

- Security rights and instances for the site and objects

- SCCM 2007 reports from SQL Server Reporting Services (SSRS)

- SCCM 2007 web reports

- Client inventory and history data

- AMT client provisioning information

- Files in the client cache

Migrating the DP:

Migrate the 2007/source distribution points after migrating all the objects and clients from 2007 environment. We can migrate the distribution point manually or automatically.

Before start migrating the distribution point review the requirements (Space, Roles etc…)

Client Migration:

• Clients should be migrated only after all objects required by the clients have been migration
• Client migration step is the last step of the migration process
• Uninstall SCCM 2007 client and install SCCM 2012 based on the chosen method (Recommended - use SCCM 2007 to deploy SCCM 2012 client)
• Use the site code in the installation command line to assign the site rather using boundary group

Rollback from SCCM 2012 to 2007:

• Copy the SCCM 2007 Client source files to the package source
• Create a package for SCCM 2007 in SCCM 2012 console
• Deploy this package to the applicable devices / collection

Cleanup Process:

• Delete all the migrated client from the source site
• Delete the migration history for the source hierarchy
• Decommission the source SCCM sites starting from the child sites in the hierarchy to the parent (From bottom to top)

Configuration Manager migration tools:

• Microsoft Migration utility (Within SCCM 2012 console)
• ReportSync (To sync the source reports to the destination SSRS)
• Package Source Changer (T change the patch of the source)