In my previous post we have talked about the migration concept and how you establish a connection between a SCCM 2007 hierarchy and a SCCM 2012 hierarchy.
In this post we will talk about the actual Migration Jobs that can be created.
The migration wizard you can start by selecting “Create Migration Job”. I will highlight the most important windows.
In the wizard you can select the different objects you want to migrate. Nice, but the option to execute Collection Migration is even nicer! Because everything what is associated with these collections (Advertisements, Packages, Task Sequences,…) can be migrated as well.
You select the collections you want:
The wizard will list the associated objects and you can select which ones you want to migrate.
A Security Scope can be set (RBAC).
Role Based Access Control, I’ll blog about that in the future.
In one of my next blogs I will talk about the new replication model that is introduced with SCCM 2012. It might be possible that the next item is not really clear right now but please be patient.
With the new replication model collections become “Global Data” which means that collections will be replicated all over the hierarchy, so it might be possible that the collection scope will increase. To avoid this, the migration tool will inform you and you will be able to limit the particular collections to another collection.
In this example I don’t have such a collection as this is a single server installation. But in a scenario where you have Central – Primary relations this will be common. For instance a collection created on a child primary site will now be migrated and replicated all over the hierarchy so the scope might increase.
If it’s not 100% clear it will hopefully be in my future post regarding the replication model. But now you know at least that the migration tool can deal with it.
The migration tool will also evaluate all the queries on the collections. When a query is detected that is using an old Site Code you will be aware of that and you can change it on-the-fly.
The tool will track as well collections that can’t be migrated like mixed collections (users and computers). Since UDA in SCCM 2012 does not like that anymore.
Collections which are limited to muliple collections in SCCM 2007 will not be migrated as well. The tool will identify them so you are aware of these collections.
During the wizard specific info can be saved to a file for review afterwards.
You can select the required run time of the migration job, if objects can be overwritten, whether advertisements needs to be enabled,…
In the console you can see an overview of the migration jobs.
Detailled log info can be found in the Migmctrl.log.
Next time, in the last part, we talk about how the migraton tool will handle subcollections and the principal of Shared Distribution Points.
You can also watch my presentation at the Best of MMS event in Belgium:
Till next time!