This article lists all the SCCM build numbers, SCCM version numbers, SCCM console version numbers and SCCM client version numbers. The SCCM (aka ConfigMgr) build numbers and version numbers are updated with every new release.
I have also listed the SCCM console version number for every ConfigMgr release and the steps to find the SCCM console version.
Microsoft releases 3 current branch versions every year and around 12-13 technical preview versions. The current branch versions are meant for production use, while technical preview versions should be installed in a lab setup.
You can find details of all the SCCM technical preview releases and their build numbers are listed in the following guide – https://www.prajwaldesai.com/sccm-technical-preview-build-version-numbers/.
Every Configuration Manager current branch release has a unique build number, version number, console version number and full version number associated with it.
In addition, every major SCCM version also updates the client agent version. The hotfix update, if includes client agent fixes, will also update client agent version number.
Table of Contents
What is SCCM Version Number?
When you install SCCM or update the SCCM to the latest build, the version represents a number associated with SCCM. For example, if you upgrade from SCCM 2107 to SCCM 2111, it means the version number of SCCM is 2111.
To find the SCCM version number:
- Launch the ConfigMgr Console.
- Click About > Configuration Manager.
- On About Microsoft Endpoint Configuration Manager window, you can find the Version Number.
What is SCCM Full Version Number
The SCCM full version number includes the build number, major version, minor version and revision number.
To explain the SCCM full version number, let’s consider SCCM 2107 release as an example. The below table helps you understand the meaning of full version number.
| SCCM Full Version Number | Major Version | Minor Version | Build Number | Revision |
| SCCM 2107 5.00.9058.1012 | 5 | 00 | 9058 | 1012 |
The SCCM build number is unique for every release and gets updated with every major release. Even though the hotfixes are released for a specific version of ConfigMgr, the build number will never change.
Find SCCM Full version from Registry
Along with SCCM build numbers, you can find SCCM full version details from registry. On the SCCM server, open the Registry Editor and browse to the following path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup.
Look for the value name Full version and that shows the SCCM full version number. For example, in the below screenshot the full version of SCCM 2107 is 5.00.9058.1000.
How to find SCCM Build Number?
There are multiple methods to find SCCM build number. You can either use the registry or site server properties to determine the build number of SCCM.
To find the SCCM build number using registry, open the registry editor. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup and look for UI Version. The UI Version registry value shows the installed SCCM build number.
You can also find the SCCM build number from the site properties. In the Configuration Manager console, go to Administration\Overview\Site Configuration\sites. Right-click the SCCM site and select Properties. On the General tab, you can see the build number of SCCM.
How to Check SCCM Console Version Number?
Let’s find out the version of the SCCM console by following the below steps:
- Launch the SCCM Console.
- Click on the dropdown arrow near to Home button.
- Select “About Configuration Manager“.
- The popup windows shows SCCM Console version along with site version.
Read: How to Install SCCM Console on Windows 11
List of SCCM Build Numbers and SCCM Version Numbers
The following table lists the following details about SCCM current branch release.
- SCCM current branch versions
- SCCM full version numbers
- SCCM build numbers
- SCCM client version numbers
- SCCM console version numbers
- SCCM baseline version
| SCCM Version | SCCM Full Version Numbers | SCCM Build Numbers | SCCM Client Version Numbers | SCCM Console Version Numbers | SCCM Baseline Version |
| SCCM 2203 Hotfix KB13953025 | 5.00.9078.1007 | 9078 | 5.00.9078.1006 | 5.2203.1063.1500 | NO |
| SCCM 2203 | 5.00.9078.1000 | 9078 | 5.00.9078.1006 | 5.2203.1063.1400 | YES |
| SCCM 2111 Hotfix KB12896009 | 5.00.9068.1000 | 9068 | 5.00.9068.1026 | 5.2111.1052.2500 | NO |
| SCCM 2111 Hotfix KB12959506 | 5.00.9068.1000 | 9068 | 5.00.9068.1012 | 5.2111.1052.1700 | NO |
| SCCM 2111 Hotfix KB12709700 | 5.00.9068.1000 | 9068 | 5.00.9068.1008 | 5.2111.1052.1700 | NO |
| SCCM 2111 | 5.00.9068.1000 | 9068 | 5.00.9068.1005 | 5.2111.1052.1700 | NO |
| SCCM 2107 | 5.00.9058.1000 | 9058 | 5.00.9058.1012 | 5.2107.1059.2000 | NO |
| SCCM 2103 | 5.00.9049.1000 | 9049 | 5.00.9049.1008 | 5.2103.1059.1700 | YES |
| SCCM 2010 | 5.00.9040.1000 | 9040 | 5.00.9040.1010 | 5.2010.1093.1800 | NO |
| SCCM 2006 | 5.00.9012.1000 | 9012 | 5.00.9012.1015 | 5.2006.1026.1800 | NO |
| SCCM 2002 | 5.00.8968.1000 | 8968 | 5.00.8968.1021 | 5.2002.1083.1700 | YES |
| SCCM 1910 | 5.00.8913.1000 | 8913 | 5.00.8913.1000 | 5.1910.1067.2100 | NO |
| SCCM 1906 | 5.00.8853.1000 | 8853 | 5.00.8853.1006 | 5.1906.1096.1500 | NO |
| SCCM 1902 | 5.00.8790.1000 | 8790 | 5.00.8790.1005 | 5.1902.1085.1500 | YES |
| SCCM 1810 | 5.00.8740.1000 | 8740 | 5.00.8740.1003 | 5.1810.1075.1300 | NO |
| SCCM 1806 | 5.00.8692.1000 | 8692 | 5.00.8692.1003 | 5.1806.1074.1200 | NO |
| SCCM 1802 | 5.00.8634.1000 | 8634 | YES | ||
| SCCM 1710 | 5.00.8577.1000 | 8577 | NO | ||
| SCCM 1706 | 5.00.8540.1000 | 8540 | NO | ||
| SCCM 1702 | 5.00.8498.1000 | 8498 | YES | ||
| SCCM 1610 | 5.00.8458.1000 | 8498 | NO | ||
| SCCM 1606 | 5.00.8412.1000 | 8412 | YES | ||
| SCCM 1602 | 5.00.8355.1000 | 8355 | NO | ||
| SCCM 1511 | 5.00.8325.1000 | 8325 | YES |
Please Share step by step upgrade Version from 2010 to Latest Version without any issue or Impacts current setup.
We must be about due a 2102 release. Anyone know when it’s due? Just thinking ahead to ensure support of 21H1 once that’s released.
The ConfigMgr 2103 is the next release and it will be released soon. I mean very soon.
Thanks Prajwal!
Hi Prajwal,
My organisation are currently using console version 1802 and we are planning to upgrade it to higher version (stable one) . What is the version we should upgrade to ?
Please give your expert advise.
It will be a two step upgrade. You can install SCCM 1906 update on sites that run version SCCM 1802, SCCM 1806, SCCM 1810, or SCCM 1902. You can begin upgrading to Configuration Manager 2010 on sites that run version SCCM 1906, SCCM 1910, SCCM 2002 or ConfigMgr 2006.
1. Upgrade your Configuration Manager version 1810 to version 1906 first – https://www.prajwaldesai.com/sccm-1906-step-by-step-upgrade-guide/
2. Upgrade SCCM 1906 to SCCM 2010 – https://www.prajwaldesai.com/sccm-2010-upgrade-guide/
For my organization that runs on 1902, would the process be the same?
Hi Prajwal, Thanks for all the work that you do!
What is the best way to know when a new Config Manager version is released? My boss is adamant that we have the latest version as soon as it is available. Is there any kind of email or notification service I can sign up for that you know of?
Thanks!!
Andy
Microsoft publishes the information about the new update as when it gets released. Over Twitter you get some news about upcoming update. Apart from that I try my best to publish the new update information on my blog. You should also get a console notification about the new update available.
Thank you, Sir!
Hey Prajwal,
Awesome content!
Hi there,
Please help me, I want to upgrade SCCM Current Branch 1902 to the latest.
How can I help you ?.
After a much heated discussion, I believe my organization is moving towards SCCM. My questions are as follows:
-SCCM 2012 is being taught yet the exam has been retired-what version should I train for?
-Microsoft has integrated SCCM into Endpoint Configuration manager-what version should we be looking at for installation on Windows server 2008 R2 or Server 2012 R2?..or are we purchasing MS Endpoint Configuration Manager 2019?
Thank you for your responses.
SCCM 2012 is an expired product and you won’t be getting any updates for it. You should go with Configuration Manager current branch (latest version) if you decide to implement it across the estate. I will find out more info about exam and will update the answer.
The windows server should be atleast Windows 2012 R2 and above. I always prefer to use the latest and stable version Of Windows server. You can also check the system OS requirements for specific version of Current Branch and go with that info.
Thanks for the info. I wonder is there any absolute dates for (production versions)
I mean, there is tech preview versions 1908, 1909,1910 etc. But is it clear for new production version will be (lets say) 1911.
Is there any standard ?
There are no absolute dates for production versions. Usually they are released for fast ring customers first and then made globally available.
I am having issues with updating to 1802. Its been about a month and my SCCM server is still downloading 1802. Plz help.
Don’t forget the 1802 Hotfix (KB4132447) version too?
5.00.8634.1011
Yes that is updated now.