Operations for migrating to Configuration Manager current branch
Applies to: Configuration Manager (current branch)
For migration in Configuration Manager, you can migrate data and clients after you successfully gather data from a source site in a supported source hierarchy. Use the information in the following sections to create and run migration jobs to migrate data and clients, and then finish the migration process.
Create and edit migration jobs
Use the following procedures to create data migration jobs, edit the exclusion list for collection-based migration jobs, set up shared distribution points, and edit migration job schedules.
Note
The following procedure for creating a migrating job that migrates by collections applies only to source hierarchies that run a supported version of Configuration Manager 2007. The collection-based migration job type is not available when you migrate from a System Center 2012 Configuration Manager or Configuration Manager current branch source hierarchy.
Create a migration job to migrate by collections
In the Configuration Manager console, choose Administration.
In the Administration workspace, expand Migration, and then choose Migration Jobs.
On the Home tab, in the Create group, choose Create Migration Job.
On the General page of the Create Migration Job wizard, set up the following and then choose OK:
Specify a name for the migration job.
In the Job type drop-down list, select Collection migration.
On the Select Collections page, set up the following and then choose Next:
Select the collections that you want to migrate.
If you want to migrate only collections and not the objects that are associated with those collections, uncheck Migrate objects that are associated with the specified collections. If you uncheck this option, no associated objects are migrated in this job, and you can skip steps 6 and 7.
On the Select Objects page, uncheck any object types or specific available objects that you do not want to migrate. By default, all associated object types and available objects are selected. Choose Next.
On the Content Ownership page, assign the ownership of content from each listed source site to a site in the destination hierarchy, and then choose Next.
On the Security Scope page, select one or more role-based administration security scopes to assign to the objects to migrate in this migration job, and then choose Next.
On the Collection Limiting page, set up a collection from the destination hierarchy to limit the scope of each listed collection, and then choose Next. If no collections are listed, choose Next.
On the Site Code Replacement page, assign a site code from the destination hierarchy to replace the Configuration Manager 2007 site code for each listed collection, and then choose Next. If no collections are listed, choose Next.
On the Review Information page, choose Save To File to save the displayed information for later viewing. When you are ready to continue, choose Next.
On the Settings page, set up when the migration job will run, choose any additional settings that you need for this migration job, and then choose Next.
Confirm the settings and finish the wizard.
Create a migration Job to migrate by objects
In the Configuration Manager console, choose Administration.
In the Administration workspace, expand Migration, and then choose Migration Jobs.
On the Home tab, in the Create group, choose Create Migration Job.
On the General page of the Create Migration Job wizard, set up the following, and then choose Next:
Specify a name for the migration job.
In the Job type drop-down list, select Object migration.
On the Select Objects page, select the object types that you want to migrate. By default, all available objects are selected for each object type that you select.
On the Content Ownership page, assign the ownership of content from each listed source site to a site in the destination hierarchy, and then choose Next. If no source sites are listed, choose Next.
On the Security Scope page, select one or more role-based administration security scopes to assign to the objects in this migration job, and then choose Next.
On the Review Information page, choose Save To File to save the displayed information for later viewing. When you are ready to continue, choose Next.
On the Settings page, set up when the migration job will run and choose any additional settings that you need for this migration job. Then choose Next.
Confirm the settings and finish the wizard.
Create a migration job to migrate changed objects
In the Configuration Manager console, choose Administration.
In the Administration workspace, expand Migration, and then choose Migration Jobs.
On the Home tab, in the Create group, choose Create Migration Job.
On the General page of the Create Migration Job wizard, set up the following and then choose Next:
Specify a name for the migration job.
In the Job type drop-down list, select Objects modified after migration.
On the Select Objects page, select the object types that you want to migrate. By default, all available objects are selected for each object type that you select.
On the Content Ownership page, assign the ownership of content from each listed source site to a site in the destination hierarchy, and then choose Next. If no source sites are listed, choose Next.
On the Security Scope page, select one or more role-based administration security scopes to assign to the objects in this migration job, and then choose Next.
On the Review Information page, choose Save To File to save the displayed information for later viewing. When you are ready to continue, choose Next.
On the Settings page, set up when the migration job will run and choose any additional settings that you require for this migration job. Unlike the other migration job types, this migration job must overwrite the previously migrated objects in the Configuration Manager database. Choose Next.
Confirm the settings and then finish the wizard.
Modify the exclusion list for migration
In the Configuration Manager console, choose Administration.
In the Administration workspace, choose Migration to gain access to the exclusion list. You can also access the exclusion list from the Source Hierarchy or Migration Jobs node.
On the Home tab, in the Migration group, choose Edit Exclusion List.
In the Edit Exclusion List dialog box, select the excluded object that you want to remove from the exclusion list, and then choose Remove.
Choose OK to save the changes and finish the edit. To cancel current changes and restore all the objects that you have removed, choose Cancel, and then choose No. This will cancel the removal of the objects, and close the Edit Exclusion List dialog box.
Share distribution points from the source hierarchy
In the Configuration Manager console, choose Administration.
In the Administration workspace, expand Migration, choose Source Hierarchy, and then select the source site that you want to set up.
On the Home tab, in the Source Site group, choose Configure.
On the Source Site Credentials dialog box, select Enable distribution point sharing for the source site server, and then choose OK.
When data gathering finishes, choose Close.
Change the schedule of a migration job
In the Configuration Manager console, choose Administration.
In the Administration workspace, expand Migration, and then choose Migration Jobs.
Choose the migration job that you want to change. On the Home tab, in the Properties group, choose Properties.
In the properties of the migration job, select the Settings tab, change the run time for the migration job, and then choose OK.
Run migration jobs
Use the following procedure to run a migration job that has not yet started.
In the Configuration Manager console, choose Administration.
In the Administration workspace, expand Migration, and then choose Migration Jobs.
Choose the migration job that you want to run. On the Home tab, in the Migration Job group, choose Start.
Choose Yes to start the migration job.
Upgrade or reassign a shared distribution point
You can upgrade a supported distribution point that is shared from a Configuration Manager 2007 source site (or reassign a supported distribution point that is shared from a Configuration Manager source site) to be a distribution point in the destination hierarchy.
Important
Before you upgrade a Configuration Manager 2007 branch distribution point, you must uninstall the Configuration Manager 2007 client software from the branch distribution point computer. If the Configuration Manager 2007 client software is installed when you attempt to upgrade the distribution point, the upgrade fails and content that was previously deployed to the branch distribution point is removed from the computer.
Caution
When you upgrade or reassign a shared distribution point, the distribution point site system role and site system computer are removed from the source site and added as a distribution point to the site in the destination hierarchy that you select.
Upgrade or reassign a shared distribution point
In the Configuration Manager console, choose Administration.
In the Administration workspace, expand Migration, and then choose Source Hierarchy.
Select the site that owns the distribution point you want to upgrade, choose the Shared Distribution Points tab, and select the eligible distribution point that you want to upgrade or reassign.
On the Distribution Point tab, in the Distribution Point group, choose Reassign.
Specify settings in the Reassign Shared Distribution Point wizard like you are installing a new distribution point for the destination hierarchy, with the following addition:
- On the Content Conversion page, review the guidance about the space required to convert the existing content. Then, on the Drive Settings page of the wizard, ensure that the drive of the distribution point computer that is selected has the required amount of free disk space.
Confirm the settings and then finish the wizard.
Monitor migration activity in the Migration workspace
Use the Configuration Manager console to monitor migration.
In the Configuration Manager console, choose Administration.
In the Administration workspace, expand Migration, and then choose Migration Jobs.
Choose the migration job that you want to monitor.
View details and status about the selected migration job on the tabs for Summary and Objects in Job.
Migrate clients
After you migrate data for clients between hierarchies but before you finish migration, plan to migrate clients to the destination hierarchy. The migration of clients between hierarchies involves uninstalling the Configuration Manager client software from computers that are assigned to the source hierarchy, and then installing the Configuration Manager client software from the destination hierarchy. When you install the client from the destination hierarchy you also assign the client to a primary site in that hierarchy. For more about migrating clients, see Planning a client migration strategy.
Finish migration
Use this procedure to finish migration from the source hierarchy.
In the Configuration Manager console, choose Administration.
In the Administration workspace, expand Migration, and then choose Source Hierarchy.
For a Configuration Manager 2007 source hierarchy, select a source site that is at the bottom level of the source hierarchy. For a System Center 2012 Configuration Manager or Configuration Manager current branch source hierarchy, select the available source site.
On the Home tab, in the Clean Up group, choose Stop Gathering Data.
Choose Yes to confirm the action.
For a Configuration Manager 2007 source hierarchy, before you continue to the next step, repeat steps 3, 4, and 5. Go through these steps at each site in the hierarchy, from the bottom of the hierarchy to the top. For a System Center 2012 Configuration Manager or Configuration Manager current branch source hierarchy, continue to the next step.
On the Home tab, in the Clean Up group, choose Clean Up Migration Data.
On the Clean Up Migration Data dialog box, from the Source hierarchy drop-down list, select the site code and site server of the top-level site of the source hierarchy, and then choose OK.
Choose Yes to finish the migration process for the source hierarchy.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for