Before you can configure a migration job, you must configure an active source hierarchy and gather data from at least one source site in the active source hierarchy. Use the following sections to help you plan the source hierarchies, source sites, and the way in which Configuration Manager 2012 gathers information from source sites in the source hierarchy so that this information can be included in a migration job.
- Migration
Source Hierarchies for Configuration Manager 2012
- Migration Source
Sites for Configuration Manager 2012
- Migration Data
Gathering for Configuration Manager 2012
Migration Source Hierarchies for Configuration Manager 2012
Source hierarchies are Configuration Manager 2007 hierarchies that contain data that you want to migrate to Configuration Manager 2012. Each source hierarchy that you configure contains one or more source sites that are the individual sites in the Configuration Manager 2007 hierarchy. Before you can configure migration jobs, you must designate one source hierarchy as the active source hierarchy and Configuration Manager 2012 must successfully gather data from a source site in that source hierarchy.
When you configure a new source hierarchy, it automatically becomes the active source hierarchy. You must specify the top-level site of the source hierarchy, which becomes the first source site of that source hierarchy. Then specify the credentials for Configuration Manager 2012 to connect to the SMS Provider and site database in the source site. Configuration Manager 2012 uses these credentials to retrieve information about objects and distribution points from the source site. As part of the data gathering process, child sites in the Configuration Manager 2007 hierarchy are identified, which you can then configure as source sites.
If you configure an additional source hierarchy before you complete migration from the active source hierarchy, it cancels any active migration jobs and postpones any scheduled migration jobs. The newly configured source hierarchy becomes the active source hierarchy, and you can then configure connection credentials, source sites, and migration jobs for the current active source hierarchy.
If you restore the original active source hierarchy, and you have not used the Cleanup Migration Data action, you can see previously configured migration jobs. However, you must reconfigure the credentials to connect to each source site and reschedule any migration jobs that did not finish.
.gif) Caution |
|---|
| If you migrate data from more than a single Configuration Manager 2007 hierarchy, each hierarchy must contain a unique set of site codes to avoid data corruption in the Configuration Manager 2012 database. |
Migration Source Sites for Configuration Manager 2012
Source sites are sites in the active source hierarchy that have data that you will migrate to Configuration Manager 2012.
When you configure a source hierarchy, you must specify the top-level site of that hierarchy first. This site becomes the first source site for that source hierarchy. After the initial data is gathered for the top-level site of the source hierarchy, any child sites of that site are visible in the Configuration Manager console.
Before you can use each additional source site for migration, you must specify credentials for Configuration Manager 2012 to connect to the SMS Provider and site database in the source site. After you configure the credentials for a source site, the data gathering process begins.
When you configure additional source sites, you must configure source sites from the top down, and configure the bottom-tier sites last. You can configure each branch of the hierarchy, but you must configure a site as a source site before you configure any of its child sites as a source sites.
You do not have to configure additional source sites before creating migration jobs. However, you can only migrate data from source sites that you have configured, and these sites must have successfully gathered data.
After you use the Stop Gathering Data option for a source site, you must reconfigure credentials for the site before you can gather data from the site again. Until you reconfigure the source site, Configuration Manager 2012 cannot identify new objects or changes to previously migrated objects.
Migration Data Gathering for Configuration Manager 2012
Immediately after you specify an active source hierarchy, configure credentials for an additional source site in an active source hierarchy, or share the distribution points for a source site with Configuration Manager 2012, a data gathering process begins.
The data gathering process then repeats on a simple schedule to maintain synchronization with any changes to data in the source site. By default, the process repeats every four hours. You can modify the schedule for this cycle by editing the Properties of the source site. The initial data gathering process must review all objects in the Configuration Manager 2007 database and can take time to finish. Subsequent data gathering processes identify only changes to the data and require less time to finish.
To gather data, the Configuration Manager 2012 top-level site connects to the SMS Provider and the site database of the source site to retrieve a list of objects and distribution points. You can configure data gathering to use user accounts or the computer account of the Configuration Manager 2012 site. You can use the same account or configure separate accounts to access the SMS Provider and the site database. To gather data from the SMS Provider, the account in use must have Read permissions to all source sites objects. The account in use to access the Microsoft SQL Server requires Read and Execute permissions to the source site database. If you use the Configuration Manager 2012 computer account, ensure this account is a member of the security group Distributed COM Users in the domain where Configuration Manager 2007 site resides.
When Configuration Manager 2012 gathers data, the following network protocols and ports are used:
- NetBIOS/SMB – 445 (TCP)
- RPC (WMI) - 135 (TCP)
- SQL Server - 1433 (TCP)
You can start and stop the data gathering process by using the Gather Data Now, and Stop Gathering Data actions in the Configuration Manager console.
Gather Data Now
After the initial data gathering process runs for a site, this process repeats to identify objects that have updated since the last data gathering cycle. You can also use the Gather Data Now action in the Configuration Manager console to immediately start the process and to reset the start time of the next cycle.
After a data gathering process successfully finishes for a Configuration Manager 2007 site, you can share the distribution points from the Configuration Manager 2007 site and configure migration jobs to migrate data from the site. Data gathering is a repeating process for migration and continues until you change the active source hierarchy, or use the Stop Gathering Data action to end the data gathering process for that site.
Stop Gathering Data
You can use the Stop Gathering Data action to end the data gathering process for a source site when you no longer want Configuration Manager 2012 to identify new or changed objects from that site. This action also prevents Configuration Manager 2012 from offering clients any shared Configuration Manager 2007 distribution points for that site as content locations for the content that you have migrated.
To stop gathering data from each source site, you must perform the Stop Gathering Data action on the bottom-tier source sites, and then repeat the process at each parent site. The top-level site must be the last site on which you stop gathering data. You must stop data gathering at each child site before performing this action at a parent site. Typically, you only stop gathering data when you are ready to complete the migration process.
After you stop gathering data for a source site, information previously gathered about object and collections from that site remain available to use when you configure new migration jobs. However, you do not see any new objects or collections, or see changes that were made to existing objects. If you reconfigure the source site and begin gathering data again, you will see information and status about previously migrated objects.