Tuesday, February 9, 2016

SCCM Creating Migration job step by step guide

Migration jobs is used to migrate data from source hierarchy to the destination hierarchy. Migration jobs identify the objects that you plan to migrate, and they run at the top-level site in your destination hierarchy.

Few things with Migration jobs;
- Create a migration job after completing the data gathering
- Migration jobs always runs on the top level of the hierarchy
- We can run multiple jobs at any given time
- We have 3 different types of migration jobs;
Collection Migration
- Migrates selected collections and collection members
Object Migration
- Migrates individual objects that selected
Previously migrated object migration
- Migrate objects that you previously migrated, when those objects have updated in the source hierarchy after they were last migrated.

Which objects can we migrate:
Not every object can be migrated by a specific type of migration job.
The following list identifies the type of objects that we can migrate with each type of migration job.

Advertisements using collection migration
Asset Intelligence catalog using Object migration and Previously migrated object migration
Asset Intelligence hardware requirements using Object migration and Previously migrated object  migration
Asset Intelligence software list using Object migration and Previously migrated object migration
Boundaries using Object migration and Previously migrated object migration
Configuration baselines using Collection migration, Object migration and Previously migrated object migration
Configuration items using Collection migration, Object migration and Previously migrated object migration
Maintenance windows using Collection migration
Operating system deployment boot images using Collection migration, Object migration and Previously migrated object migration
Operating system deployment driver packages using Collection migration, Object migration and Previously migrated object migration
Operating system deployment drivers using Collection migration, Object migration and Previously   migrated object migration
Operating system deployment images using Collection migration, Object migration and Previously migrated object migration
Operating system deployment packages using Collection migration, Object migration and Previously migrated object migration
Software distribution packages using Collection migration, Object migration and Previously migrated object migration
Software metering rules using Object migration, Previously migrated object migration
Software update deployment packages using Collection migration, Object migration, Previously
migrated object migration
Software update deployment templates using Collection migration, Object migration and Previously
migrated object migration
Software update deployments using Collection migration
Software update lists using Object migration, Previously migrated object migration
Task sequences using Collection migration, Object migration and Previously migrated object migration
Virtual application packages using Collection migration and Object migration

Unsupported Migration collections:
As part of the site migration we can migrate default user collections, device collections, and most custom collections from a  source hierarchy. However, we cannot migrate collections that contain users and devices in the same collection.

The following collections cannot be migrated:
•A collection that contains users and devices.
•A collection that contains a reference to a collection of a different resource type.
•A collection that contains a rule to include unknown computers. The collection migrates, but the rule to include unknown computers does not migrate.

Creating Migration Job in SCCM:
Open SCCM console in SCCB 1511 then go to Administration/ Migration then Right click on Migration Jobs then choose Create Migration Job;

On the General tab of Create Migration Job Wizard window, provide a name and select Object Migration in the Job Type from the drop down then click next; 

Select objects that you want to migrate on the Select Objects tab then click next;

On the Content Ownership tab select new site under destination site to assign all the rights to the new site then click next;

If required, add new site code (SCCB 1511) on the destination site code On the Site Code replacement tab then click next;

 On the Security Scope tab specify the security scope to apply to the migrated objects then click next;

On the Settings tab;
- Specify the Schedule to run the migration job
- Conflict resolution action for already migrated objects
- Specify additional settings for Organizational folder structure then click next;

Review all the settings on the summary page, then click next;

Click Close on the completion tab to exist the wizard;

Based on the chosen schedule, the migration job will start and job status can be view in SCCB 1511 console under Administration / Migration / Migration Jobs
As the job progresses, we can see the object will populate in SCCB 1511 console.

Click here for complete SCCM 1511 Current Branch setup step by step guide.

Click here for complete SCCM 1511 Current Branch step by step guide, step by step migration guide, step by step monitoring and health check guide and step by step SCCM Current Branch servicing guide.

No comments:

Post a Comment