Tuesday, 12 January 2016

Configuration Manager - migration from previous version on another server

System Center Configuration Manager landing page

Configuration Manager supports an in-place upgrade from 2012 SP1 and later. It also provides an excellent migration path from previous versions. You can use this if you want to upgrade to the latest version but also want to move the solution to a new server. This is particularly important at the moment. Although Windows Server 2008 R2 is an officially supported platform it will no longer be useful for Configuration Manager Software Update Points. It will not support the new Updates and Servicing feature. Therefore you must migrate to a later operating system.

The following TechNet library article documents the versions that are supported for migration.


You can migrate from:
  • Configuration Manager 2007 SP2
  • Configuration Manager 2012 SP2
  • Configuration Manager 2012 R2 SP1
  • Previous Configuration Manager (same or lesser version)

The migration process is exactly the same as we used to migrate from ConfigMgr 2007 to 2012. I have documented that process here:


The high-level steps are as follows:
  • Install ADK 10 (RTM version 10.0.26624.0)
  • Install server prerequisites
  • Install supported SQL version
  • Add WSUS role
  • Install WSUS hotfix (KB3095113)
  • Install new Configuration Manager site
  • Add Software Update Point
  • Create Source Hierarchy
  • Gather data from old site
  • Migrate objects to new site
  • Share and re-assign DPs
  • Migrate clients
  • Remove Source Hierarchy
  • Change data path for apps, packages, images, drivers
  • Remove unwanted Configuration Manager objects from System Management container
  • Uninstall previous Configuration Manager site.
I hope this helps. Until next time......

No comments:

Post a Comment