SCCM Upgrade Paths (In-Place Upgrade paths)
In this post, I will list SCCM upgrade paths for every major release of ConfigMgr. Using the SCCM In-place upgrade paths info you can find out if you can upgrade your SCCM to the current branch release.
With the release of new SCCM current branch versions, many customers are looking to upgrade their configuration manager environment. Especially upgrade SCCM 2012 R2 to current branch releases.
The SCCM 2012 R2 is outdated and will not receive any further updates from Microsoft. If you are still running SCCM 2012 R2 in your setup, you must upgrade to the supported current branch version.
When you plan to upgrade Configuration Manager, you must know the available SCCM upgrade paths. There are many versions of SCCM released till date. Here is a post that lists the build numbers for SCCM and Tech Preview versions. Refer the following post for current branch build numbers.
This post lists the upgrade paths for configuration manager. Before you upgrade it is recommended to check supported configurations for SCCM and upgrade checklist.
Table of Contents
SCCM Upgrade Paths (In-place Upgrade Paths)
Let’s now look at in-place SCCM upgrade paths available for different versions of Configuration Manager. To perform in-place upgrade, you must always download the baseline version first.
Upgrade paths to SCCM Version 1511
If you are planning to upgrade your configuration manager environment to version 1511, the below table helps you with SCCM upgrade paths. 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 From | In-place Upgrade to Version 1511 |
| System Center Configuration Manager RC Install | Supported |
| System Center 2012 Configuration Manager with SP1 | Supported |
| System Center 2012 Configuration Manager with SP2 | Supported |
| System Center 2012 R2 Configuration Manager | Supported |
| System Center 2012 R2 Configuration Manager with SP1 | Supported |
| System Center Configuration Manager version 1511 (Eval) | Supported |
Upgrade paths to SCCM Version 1606
The below table lists the In-place upgrade paths to Version 1606 of Configuration Manager. In addition, you need baseline media for version 1606 to upgrade.
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 SCCM upgrade paths from SCCM 2012/2012 R2 to current branch release assuming you have downloaded latest version of baseline media.
| Upgrade From | In-place Upgrade to Version 1606 |
| System Center Configuration Manager RC Install | Supported |
| System Center 2012 Configuration Manager with SP1 | Supported |
| System Center 2012 Configuration Manager with SP2 | Supported |
| System Center 2012 R2 Configuration Manager | Supported |
| System Center 2012 R2 Configuration Manager with SP1 | Supported |
| System Center Configuration Manager version 1606 (Eval) | Supported |
Upgrade paths to SCCM Version 1702
The below table lists the upgrade paths to version 1702 of SCCM.
| Upgrade From | In-place Upgrade to Version 1702 |
| System Center 2012 Configuration Manager with SP1 | Supported |
| System Center 2012 Configuration Manager with SP2 | Supported |
| System Center 2012 R2 Configuration Manager | Supported |
| System Center 2012 R2 Configuration Manager with SP1 | Supported |
| System Center Configuration Manager version 1702 (Eval) | Supported |
Upgrade paths to SCCM Version 1802
The below table lists the upgrade paths to version 1802 of SCCM.
| Upgrade From | In-place Upgrade to Version 1802 |
| System Center 2012 Configuration Manager with SP1 | Supported |
| System Center 2012 Configuration Manager with SP2 | Supported |
| System Center 2012 R2 Configuration Manager | Supported |
| System Center 2012 R2 Configuration Manager with SP1 | Supported |
| System Center Configuration Manager version 1802 (Eval) | Supported |
Upgrade paths to SCCM Version 1902
The below table lists the upgrade paths to version 1902 of SCCM.
| Upgrade From | In-place Upgrade to Version 1902 |
| System Center 2012 Configuration Manager with SP1 | Supported |
| System Center 2012 Configuration Manager with SP2 | Supported |
| System Center 2012 R2 Configuration Manager | Supported |
| System Center 2012 R2 Configuration Manager with SP1 | Supported |
| System Center Configuration Manager version 1902 (Eval) | Supported |
Upgrade paths to SCCM Version 2002
The below table lists the upgrade paths to version 2002 of SCCM.
| Upgrade From | In-place Upgrade to Version 2002 |
| System Center 2012 Configuration Manager with SP1 | Supported |
| System Center 2012 Configuration Manager with SP2 | Supported |
| System Center 2012 R2 Configuration Manager | Supported |
| System Center 2012 R2 Configuration Manager with SP1 | Supported |
| System Center Configuration Manager version 2002 (Eval) | Supported |
Upgrade Paths to SCCM Version 2103
The below table lists the SCCM in-place upgrade paths to version 2103. To upgrade to 2103, you must download the ConfigMgr 2103 baseline version.
| Upgrade From | In-place Upgrade to Version 2103 |
| System Center 2012 Configuration Manager with SP1 | Supported |
| System Center 2012 Configuration Manager with SP2 | Supported |
| System Center 2012 R2 Configuration Manager | Supported |
| System Center 2012 R2 Configuration Manager with SP1 | Supported |
| System Center Configuration Manager version 2002 (Eval) | Supported |
Upgrade Paths to SCCM Version 2203
The below table lists the SCCM in-place upgrade paths to version 2203. To upgrade to 2203, you must download the ConfigMgr 2203 baseline version.
| Upgrade From | In-place Upgrade to Version 2203 |
| System Center 2012 Configuration Manager with SP1 | Supported |
| System Center 2012 Configuration Manager with SP2 | Supported |
| System Center 2012 R2 Configuration Manager | Supported |
| System Center 2012 R2 Configuration Manager with SP1 | Supported |
| System Center Configuration Manager version 2002 (Eval) | Supported |
Note: Starting in April 2022, this feature of Configuration Manager is deprecated. The baseline media for version 2203 is the last version of Configuration Manager current branch version that will support upgrade from any version of System Center 2012 Configuration Manager. Current branch version 2303 media will only support new installs of current branch.
Hi Prajwal,
We have SCCM server version 2202 that we like to upgrade to latest version. Server is hosted on 2012 R2.
Issue is out hosted VM has some ongoing issues that may get cause problems in long run if we perform in-place upgrade.
We have lot of custom images and task sequence which are very time consuming if we build new sccm servers. Would you recommend any easier way to build SCCM on new VM’s but than move all work load to new SCCM server?
Thanks
Randy
Is in-place upgrade from SCCM 2019 2107 version supported to SCCM 2022 now?
Hi Prajwal,
I’m about to upgrade our environment from 1910 to 2111 by first upgrading to 2103, are there are suggestions you have before I start this process?
For example, should I upgrade to 2103 and update all the clients before upgrading to 2111?
I’ve never had to do a double step before so this is new for me.
Regards, Todd
You can upgrade to version 2111 and then upgrade the clients directly to latest version (2111).
Thank you, that’s very helpful.
Hi Prajwal Desai,
We are currently on 1610 version of SCCM. Can you let me know what is the upgrade path from 1610 to 2111 and any caveats and risks involved?
I haven’t tested the upgrade from 1610 to 2111. What updates are available currently in updates and servicing node?
It has Configuration Manager 1702, 1706 and 1710. The admins have tried running the pre-requisites and it looks like it failed. So, I have been asked to build a new system and migrate this version. What would you suggest?
Thanks in advance
Hi Prajwal,
We are Still running SCCM 2007R2 version in AD environment. Most of our clients are Windows 7 and windows 8 and now gradually want to upgrade to windows 10. I am planning to install Configuration manager (Current Base Branch-2002) on a new different server. Can you advice what are the first few steps should be taken .Shall i need to first uninstall all client software from all PC and then SCCM software from existing server before introducing new Configuration manager in our infrastructure. or what broad steps should be taken first.
Please advice.
You can install Configuration Manager current branch with a different site code and then migrate all the clients to new site.
Thank you so much of quick reply. is there any process reference is there for this kind of environment to take help with in terms of effect of introducing new ConfigMgr in current AD schema, and automated removal and migration of old client with new one,. One more question , will the new current branch supports clients on the (out of support ) Windows 7 in terms of pushing any application or taking inventory etc.
Referring to any of your old article for my case will be a great help either. š
Hi Prajwal, If you could tell if the existing windows 7 PC sccm existing clients can be moved automatically to new Site. and ifs Windows 7 PC is supported in configmanager current branch.
And Am i right to think that no need for any schema extension now since SCCM 2007 R2 is already existing.
Hi,
Can I upgrade SCCM version 1606 to 2002 ?
HI , Sir
I want to update my sccm version 1802 to 1910.
it is possible and possible to how to upgrade .
please give me a help for the same.
Hi Prajwal,
I am planning to upgradeĀ the SCCM server to the latest version, Could you please help me, what are the steps we have to follow the time we upgrade to 1906 version.
Server Operating System: 2012 R2 STD
SCCM Server: System Center 2012 Configuration Manager with SP2
Database: SQL server 2012
CurrentĀ Version:
The current site version is 5.00.8239.1000 and the console version is 5.0.8239.1502.
Hi Prajwal,
Is it possible to upgrade from SCCM 2012 R2 directly to 2002.Please advise
Yes you can do that.
Hi,
How do I upgrade 2012 R2 to 1902. I tried 1902 manual upgrade however the prereq fails with error LinkID 722800.
I do not see any option to download versions prior to 1902 in Volume Center or Evaluation sites. Please advise.
Can you send a screenshot of the error and log files ?.
Hi Prajwal,
thanks for all the material You have on internet about SCCM , sharing Your knowledge, make SCCM administrators very confident on that complicated Microsoft product! A question about the upgrade to CB 1802… My supported scenario is SCCM2012R2 Sp1 -> SCCM CB 1802 . Talking with customers , everytime I suggest a Side-by-Side migration … May I ask Your point of view?
Thanks
Davide
You can perform a direct upgrade to 1802.
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
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
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