• Article

Determine Whether to Migrate Configuration Manager 2007 to System Center 2012 Configuration Manager

 

Updated: May 14, 2015

Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1

In Microsoft System Center 2012 Configuration Manager and System Center 2012 R2 Configuration Manager, the built-in migration functionality replaces in-place upgrades from previous versions of Configuration Manager by providing a process that transfers data from supported versions of Configuration Manager to a new hierarchy.

With the exception of the distribution point site system role and the computers that host distribution points, no infrastructure (which includes sites, site system roles, or computers that host a site system role), migrates, transfers, or can be shared between hierarchies.

Although you cannot migrate server infrastructure, you can migrate Configuration Manager clients between hierarchies. Client migration involves migrating the data that clients use from the source hierarchy to the destination hierarchy, and then installing or reassigning the client software so that the client then reports to the new hierarchy. After you install a client to the new hierarchy and the client submits its data, its unique Configuration Manager ID helps Configuration Manager associate that data that you previously migrated with each client computer.

The functionality provided by migration helps you maintain investments that you have made in configurations and deployments while you can take full advantage of core changes in the product introduced in System Center 2012 Configuration Manager. These changes include a simplified Configuration Manager hierarchy that uses fewer sites and resources, and the improved processing by using native 64-bit code that runs on 64-bit hardware.

For information about the versions of Configuration Manager that migration supports, see Prerequisites for Migration in System Center 2012 Configuration Manager.

Use the following sections to help you plan for data that you can or cannot migrate:

  • Data That You Can Migrate with System Center 2012 Configuration Manager

  • Data That You Cannot Migrate with System Center 2012 Configuration Manager

Data That You Can Migrate with System Center 2012 Configuration Manager

Migration can migrate most objects from between supported Configuration Manager hierarchies. The migrated instances of some objects from a supported version of Configuration Manager 2007 must be modified to conform to the System Center 2012 Configuration Manager schema and object format. These modifications do not affect the data in the Configuration Manager 2007 database. Objects migrated from a supported version of System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager do not require modification.

The following table lists the objects that can migrate based on the version of Configuration Manager in the source hierarchy. Some objects do not migrate, which includes queries. If you want to continue to use these objects you must recreate them in the new hierarchy. Other objects, which includes some client data, are automatically recreated in the new hierarchy when you manage clients in that hierarchy.

Object

Migrate from Configuration Manager 2007 SP2

Migrate from System Center 2012 Configuration Manager SP1 or System Center 2012 R2 Configuration Manager

Advertisements

Yes

Yes

Applications for System Center 2012 Configuration Manager 

Not applicable

Yes

App-V Virtual Environment from System Center 2012 Configuration Manager 

Not applicable

Yes

Asset Intelligence customizations

Yes

Yes

Boundaries

Yes

Yes

Collections1

Yes

Yes

Compliance settings (referred to as desired configuration management in Configuration Manager 2007)

  • Configuration baselines

  • Configuration items

Yes

Yes

Operating system deployment:

  • Boot images

  • Driver packages

  • Drivers

  • Images

  • Packages

  • Task sequences

Yes

Yes

Search results

Yes (Search folders)

Yes (Saved search criteria)

Software updates:

  • Deployments

  • Deployment packages

  • Templates

  • Software update lists

Yes

Yes

Software distribution packages

Yes

Yes

Software metering rules

Yes

Yes

Virtual application packages

Yes

Yes

1 You migrate collections from a supported version of Configuration Manager 2007 by using a collection migration job. However, to migrate collections from a supported version of System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager, you use an object migration job.

Data That You Cannot Migrate with System Center 2012 Configuration Manager

You cannot migrate the following types of objects:

  • AMT client provisioning information

  • Files on clients, which includes:

    • Client inventory and history data

    • Files in the client cache

  • Queries

  • Configuration Manager 2007 security rights and instances for the site and objects

  • Configuration Manager 2007 reports from SQL Server Reporting Services

  • Configuration Manager 2007 web reports

  • System Center 2012 Configuration Manager reports

  • System Center 2012 Configuration Manager role-based administration:

    • Security roles

    • Security scopes