In this post we will look at the System Center Configuration Manager upgrade paths. With the release of new SCCM versions, a lot of customers are looking to upgrade their configuration manager environment. When you plan to upgrade your SCCM, you need to know the available upgrade paths. There are many version of SCCM released till date. Here is a post that lists the build numbers for SCCM and Tech Preview versions. This post lists the upgrade paths for system center configuration manager. Before you upgrade it is recommended to check supported configurations for SCCM and upgrade checklist.

System Center Configuration Manager Upgrade Paths

Let’s now look at upgrade paths available for system center configuration manager.

Upgrade to Version 1511

If you are planning to upgrade your configuration manager environment to version 1511, the below table helps you. Most of all to upgrade you need version 1511 baseline media. After you install a baseline version, additional versions of SCCM are available as in-console updates.

Upgrade FromUpgrade to Version 1511
System Center Configuration Manager RC InstallSupported
System Center 2012 Configuration Manager with SP1Supported
System Center 2012 Configuration Manager with SP2Supported
System Center 2012 R2 Configuration ManagerSupported
System Center 2012 R2 Configuration Manager with SP1Supported
System Center Configuration Manager version 1511 (Eval)Supported

 

Upgrade to Version 1606

The below table lists the upgrade paths to Version 1606 of SCCM. In addition, you need baseline media for version 1606 to upgrade. There were 2 versions of baseline media released for SCCM 1606. One on December 15th, 2016 and other one prior to it. I would recommend you to download the baseline version released on December 15th, 2016. The table shows the upgrade paths assuming you have downloaded latest version of baseline media.

Upgrade FromUpgrade to Version 1606
System Center Configuration Manager RC InstallSupported
System Center 2012 Configuration Manager with SP1Supported
System Center 2012 Configuration Manager with SP2Supported
System Center 2012 R2 Configuration ManagerSupported
System Center 2012 R2 Configuration Manager with SP1Supported
System Center Configuration Manager version 1606 (Eval)Supported

 

Upgrade to Version 1702

The below table lists the upgrade paths to Version 1702 of SCCM.

Upgrade FromUpgrade to Version 1702
System Center 2012 Configuration Manager with SP1Supported
System Center 2012 Configuration Manager with SP2Supported
System Center 2012 R2 Configuration ManagerSupported
System Center 2012 R2 Configuration Manager with SP1Supported
System Center Configuration Manager version 1702 (Eval)Supported

 

10 COMMENTS

  1. If I have version 5.0.7958.1604 System Center 2012 r2 can I upgrade to version 1606 base?

    If so, how do I do it? Because in Administration / overview / cloud Services I do not see the update and servicing option

    • Did yo manage to get sorted with this, I am planning similar upgrade , but with me will be to 1702 as that’s the media now that MS have available

  2. Hi there Prajwal, always enjoy your SCCM videos and work since Ive been working with SCCM, just wondering if you can advise f it is possible t upgrade from SCCM 2012 R2 directley to 1702

      • Hi Prajwal, thanks for that , honestly have to say your SCCM knowledge is some of the most informative and practical out there, many thanks for the link

          • Prajwal, Im having some other issues around secondary server implementation, and because i inherited the environment there are issues, namely getting the following : [Failed]:The logon account for the SQL Server service cannot be a local user account, NT SERVICE or LOCAL SERVICE. You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM. and Failed]:The collation of the site database does not match the collation of the parent site’s database. All sites in a hierarchy must use the same database collation. I have seen you have postes on these,m however Im not sure why i am getting the first one , as there is a service a/c that run that is a specific sql_svc a/c running on my primary, any tips or advise would be greatly appreciated

  3. Hi Prajwal, thank you so much for all your help, my upgrade to 1702 has gone very well, and I now have secondary server instated, however the DRS replication never occurs and stays at Initializing connection, when I use the link analyzer it tells me the following Connection failure detected between NAMED PRIMARY and the SQL Server NAMED SECONDARY CONFIGMGRSEC. Check network and firewall settings between these computers. It may take several minutes for firewall changes to take effect. Connection failure message: Failed to get SQ: Connection to NAMED SECONDARYCONFIGMGRSEC.(db instance running on sql express on secondary server) In this case the sql server agent and the broker ports are open , and I have ensured the a/c using the instance has permissions on both prinary and secondary, and I have even added the computer a/c of the prinary to be allowed on the instance on the secondary. id really appreciate your thoughts on this as I try to get to grips with sccm, even if you could advise what logs I should be looking at to see f I can figure it out. Thank You again Prajwal

LEAVE A REPLY

Please enter your comment!
Please enter your name here