• Article

Prerequisites for Migration in 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

To migrate from a supported source hierarchy, you must have access to each applicable Configuration Manager source site, and permissions within the Configuration Manager destination site to configure and run migration operations.

Use the information in the following sections to help you understand the versions of Configuration Manager that are supported for migration, and the required configurations.

  • Versions of Configuration Manager That Are Supported for Migration

  • Source Site Languages That Are Supported for Migration

  • Required Configurations for Migration

Versions of Configuration Manager That Are Supported for Migration

The following table lists the versions of Configuration Manager 2007 and System Center 2012 Configuration Manager that are supported for migration to a destination hierarchy of each version of System Center 2012 Configuration Manager.

Destination hierarchy

Source hierarchy

System Center 2012 Configuration Manager with no service pack

Configuration Manager 2007 SP21

System Center 2012 Configuration Manager SP1

Configuration Manager 2007 SP21

System Center 2012 Configuration Manager SP1

System Center 2012 Configuration Manager SP2

Configuration Manager 2007 SP21

System Center 2012 Configuration Manager SP22

System Center 2012 R2 Configuration Manager SP12

System Center 2012 R2 Configuration Manager

Configuration Manager 2007 SP21

System Center 2012 R2 Configuration Manager

System Center 2012 R2 Configuration Manager SP1

Configuration Manager 2007 SP21

System Center 2012 R2 Configuration Manager SP12

System Center 2012 Configuration Manager SP22

1 For the purpose of migration, Configuration Manager 2007 R2 or R3 on the source site are not a consideration. So long as the source site runs SP2, sites with either the R2 or R3 add-on installed are supported for migration to System Center 2012 Configuration Manager.

2 System Center 2012 Configuration Manager SP2 and System Center 2012 R2 Configuration Manager SP1 are treated the same for the purpose of migration, and you can migrate data between sites that run either of these two license options.

Source Site Languages That Are Supported for Migration

When you migrate data between Configuration Manager hierarchies, the data is stored in the destination hierarchy in the language neutral format for System Center 2012 Configuration Manager. Because Configuration Manager 2007 does not store data in a language neutral format, the migration process must convert objects to this format during migration from Configuration Manager 2007. Therefore, only Configuration Manager 2007 source sites that are installed with the following languages are supported for migration:

  • English

  • French

  • German

  • Japanese

  • Korean

  • Russian

  • Simplified Chinese

  • Traditional Chinese

When you migrate data from a System Center 2012 Configuration Manager hierarchy, there are no source site language limitations. Objects in the source site database are already in a language neutral format.

Required Configurations for Migration

The following table lists the required configurations for using migration and migration operations.

Migration operation

Details

To configure, run, and monitor migration in the Configuration Manager console

In the destination site, your account must be assigned the role-based administration security role of Infrastructure Administrator. This security role grants permissions to manage all migration operations, which includes the creation of migration jobs, clean up, monitoring, and the action to share and upgrade distribution points.

Data Gathering

To enable the destination site to gather data, you must configure the following two source site access accounts for use with each source site:

  • Source Site Account: This account is used to access the SMS Provider of the source site.

    • For a Configuration Manager 2007 SP2 source site, this account requires Read permission to all source site objects.

    • For a System Center 2012 Configuration Manager source site, this account requires Read permission to all source site objects, You grant this permission to the account by using role-based administration. For information about how to use role-based administration, see the Planning for Role-Based Administration section in the Planning for Security in Configuration Manager topic.

  • Source Site Database Account: This account is used to access the SQL Server database of the source site and requires Connect, Execute, and Select permissions to the source site database.

You can configure these accounts when you configure a new source hierarchy, data gathering for an additional source site, or when you reconfigure the credentials for a source site. These accounts can use a domain user account, or you can specify the computer account of the top-level site of the destination hierarchy.

System_CAPS_security Security Note

If you use the Configuration Manager computer account for either access account, ensure that this account is a member of the security group Distributed COM Users in the domain where the source site resides.

When gathering data, the following network protocols and ports are used:

  • NetBIOS/SMB – 445 (TCP)

  • RPC (WMI) - 135 (TCP)

  • SQL Server - The TCP ports in use by both the source and destination site databases.

Migrate Software Updates

Before you migrate software updates, you must configure the destination hierarchy with a software update point. For more information, see Planning to Migrate Software Updates

Share distribution points

To successfully share any distribution points from a source site, at least one primary site or the central administration site in the destination hierarchy must use the same port numbers for client requests as the source site. For information about client request ports, see How to Configure Client Communication Port Numbers in Configuration Manager topic in the Deploying Clients for System Center 2012 Configuration Manager guide.

For each source site, only the distribution points that are installed on site system servers that are configured with a FQDN are shared.

In addition, to share a distribution point from a System Center 2012 Configuration Manager source site, the Source Site Account (which accesses the SMS Provider for the source site server), must have Modify permissions to the Site object on the source site. You grant this permission to the account by using role-based administration. For information about how to use role-based administration, see the Planning for Role-Based Administration section in the Planning for Security in Configuration Manager topic.

Upgrade or reassign distribution points

The Source Site Access Account configured to gather data from the SMS Provider of the source site must have the following permissions:

  • To upgrade a Configuration Manager 2007 distribution point, the account requires Read, Execute, and Delete permissions to the Site class on the Configuration Manager 2007 site server to successfully remove the distribution point from the Configuration Manager 2007 source site

  • To reassign a System Center 2012 Configuration Manager distribution point, the account must have Modify permission to the Site object on the source site. You grant this permission to the account by using role-based administration. For information about how to use role-based administration, see the Planning for Role-Based Administration section in the Planning for Security in Configuration Manager topic.

To successfully upgrade or reassign a distribution point to a new hierarchy, the ports that are configured for client requests at the site that manages the distribution point in the source hierarchy must match the ports that are configured for client requests at the destination site that will manage the distribution point. For information about client request ports, see How to Configure Client Communication Port Numbers in Configuration Manager topic in the Deploying Clients for System Center 2012 Configuration Manager guide.