If you are running SCCM 2007 today you will probably migrate in the future to the latest SCCM release. The bad news is that you cannot upgrade in-place, the good news is that Microsoft created an excellent migration tool inside SCCM 2012 to migrate side-by-side.
Before we start:
1. A prerequiste to use the migration tool is that your SCCM 2007 servers are SP2 at least.
2. SCCM 2012 likes UNC very much, in case of Applications you HAVE to use UNC paths to browse to your data source. If you want to start following the best practices and you have packages in SCCM 2007 that are pointing to a local drive, you can use Kent Agerlund his tool to change all these local data source paths into UNC.
3. Install your new corresponding SCCM 2012 server, install all the required roles and configure SUP.
The reason why SUP needs to be configured is to make sure that update lists gets converted to Update Groups and Update Deployments are migrated to Deployments and Update Groups.
During the migration updates don’t get migrated, only the metadata. For that it’s also important that the catalog is identical.
You can use wsusutil.exe export/import for this or make sure if you sync with Microsoft Update that you select the same classifications.
So let’s look into the tool.
Active Source Hierarchy:
With this wizard we will connect the SCCM 2012 site to SCCM 2007 site.
Add the necessary credentials to get access to the SCCM 2007 site.
Start the gathering process…
In a complex hierarchy you will install your top SCCM 2012 server (CAS) and connect that one to the SCCM 2007 Central server to gather all necessary hierarchy info.
If you have multiple primary sites you will create an active Source Hierarchy for each SCCM 2007 site to the SCCM 2012 CAS to gather all objects metadata.
By default SCCM 2012 will check each 4 hours to keep the gathered data up-to-date.
Secondary sites need to uninstalled manually from the SCCM 2007 site. If you reinstall a secondary site on the SCCM 2012 consider if it’s still required –> Simplify hierarchy! Maybe a DP role is enough as we can now throttle DPs with SCCM 2012.
So what will be migrated?
Well everything, except:
Data Source content (see next post for more info)
OSD: boot images, because of the new WAIK in SCCM 2012
SubCollections, I talk about that in a next post.
Some things you need to know.
- Classic Packages and Programs get migrated as-is, so no conversion to Applications. Microsoft will release later on a tool for doing the conversion to the new Application Model later on this year.
- Clients retain execution history so they will not re-rerun advertisements if they don’t need to. You can upgrade them via your prefered deployment method (GPO, Push, OSD,…). Once upgraded a Full inventory data will be send once upgraded –> phased approach is advisable.
- Keep Site Codes unique
- Don’t use SMSSITECODE=AUTO
- SCCM 2007 Hardware Inventory can be imported into SCCM 2012 on Client Settings level.
- 5 new reports are available to get more detailled info about the migration jobs.
So, we have talked about the existence of the built-in tool, how you connect sites and what things you have to take into account.
Next time, we will talk about the Migration jobs, shared SCCM 2007 DPs and many more.
You can also watch my presentation at the Best of MMS event in Belgium:
Till next Time!