Determine whether to migrate data to System Center Configuration Manager

 

Aplica-se A: System Center Configuration Manager (current branch)

In O System Center Configuration Manager migration provides a process to transfer data and configurations you have made from supported versions of Gestor de configuração to your new hierarchy. You can use this to:

  • Combine multiple hierarchies into one

  • Move data and configurations from a lab deployment into your production deployment

  • Move data and configuration from a prior version of Gestor de configuração, like Gestor de configuração 2007 which has no upgrade path to O System Center Configuration Manager, or from System Center 2012 Configuration Manager (which does support an upgrade path to O System Center Configuration Manager).

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 Gestor de configuração 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 Gestor de configuração ID helps Gestor de configuração 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 first introduced in System Center 2012 Configuration Manager and continued in O System Center Configuration Manager. These changes include a simplified Gestor de configuração 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 Gestor de configuração that migration supports, see Prerequisites for migration in System Center Configuration Manager.

The following sections can help you plan for data that you can or cannot migrate:

Migration can migrate most objects from between supported Gestor de configuração hierarchies. The migrated instances of some objects from a supported version of Gestor de configuração 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 source site database. Objects migrated from a supported version of System Center 2012 Configuration Manager or O System Center Configuration Manager do not require modification.

The following are objects that can migrate based on the version of Gestor de configuração in the source hierarchy. Some objects, like queries, do not migrate. If you want to continue to use these objects that do not migrate 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.

Objects you can migrate from System Center 2012 Configuration Manager or System Center Configuration Manager current branch:

  • Advertisements

  • Applications for System Center 2012 Configuration Manager and later versions

  • App-V Virtual Environment from System Center 2012 Configuration Manager and later versions

  • Asset Intelligence customizations

  • Boundaries

  • Collections - To migrate collections from a supported version of System Center 2012 Configuration Manager or System Center Configuration Manager, you use an object migration job.

  • Compliance settings:

    • Configuration baselines

    • Configuration items

  • Operating system deployment:

    • Boot images

    • Driver packages

    • Drivers

    • Images

    • Packages

    • Task sequences

  • Search results - Saved search criteria

  • Software updates:

    • Deployments

    • Deployment packages

    • Templates

    • Software update lists

  • Software distribution packages

  • Software metering rules

  • Virtual application packages

Objects you can migrate from Configuration Manager 2007 SP2:

  • Advertisements

  • Applications for System Center 2012 Configuration Manager and later versions

  • App-V Virtual Environment from System Center 2012 Configuration Manager and later versions

  • Asset Intelligence customizations

  • Boundaries

  • Collections - You migrate collections from a supported version of Configuration Manager 2007 by using a collection migration job.

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

    • Configuration baselines

    • Configuration items

  • Operating system deployment:

    • Boot images

    • Driver packages

    • Drivers

    • Images

    • Packages

    • Task sequences

  • Search results - Search folders

  • Software updates:

    • Deployments

    • Deployment packages

    • Templates

    • Software update lists

  • Software distribution packages

  • Software metering rules

  • Virtual application packages

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

  • Gestor de configuração 2007 security rights and instances for the site and objects

  • Gestor de configuração 2007 reports from SQL Server Reporting Services

  • Gestor de configuração 2007 web reports

  • System Center 2012 Configuration Manager and O System Center Configuration Manager reports

  • System Center 2012 Configuration Manager and O System Center Configuration Manager role-based administration:

    • Security roles

    • Security scopes

Planning for migration to System Center Configuration Manager

Mostrar: