SCCM CB support scenarios are different from the previous versions of the products like SCCM 2007 and SCCM 2012. In SCCM 2007 and 2012, we had support scenarios like “Mainstream Support” and “Extended Support”. You will be able to see more details about SCCM Life Cycle and support scenarios in this post.
SCCM Life Cycle – Table format
You can find more details about supported versions of SCCM from here.
| Version | Availability Date | Support End Date |
| 1910 | Nov 27, 2019 | |
| 1906 | July 10/17/24, 2019? | |
| 1902 | March 27, 2019 | September 27, 2020 |
| 1810 | Nov 27, 2018 | May 27, 2020 |
| 1806 | July 31, 2018 | January 31, 2020 |
| 1802 | March 22, 2018 | September 22, 2019 |
| 1710 | Nov 20, 2017 | May 20, 2019 |
| 1706 | July 31, 2017 | July 31, 2018 |
| 1702 | March 27, 2017 | March 27, 2018 |
| 1610 | Nov 18, 2016 | November 18, 2017 |
| 1606 | July 22, 2016 | July 22, 2017 |
| 1602 | March 11, 2016 | March 11, 2017 |
| 1511 | Dec 8, 2015 | December 8, 2016 |
SCCM Mainstream Vs. Extended?
The support scenarios for SCCM/ConfigMgr CB (Current Branch) does not fall in to Mainstream and Extended. Rather SCCM CB support lifecycle is divided into two categories called “Security and Critical Updates servicing phase“ and “Security Updates (Only) servicing phase“. More details about End of Support Dates for SCCM CB Current Branch in the below table.
Update:-
- SCCM CB 1710 and later, all support ends after the 18-month lifecycle for a current branch version has expired.
- SCCM CB versions prior to 1710, support ends after the 12-month lifecycle expires.
You will get more detailed explanation of these two new categories at the end of this post. The main reason for this change is because SCCM CB product is released “few times” in a year. For example, in the year 2016, we already have SCCM CB 1602 and 1606 (and will have 1610 ?). So it’s difficult follow the old support life cycle.
Latest update available here
SCCM CB update versions (example 1511, 1602, 1606 etc..) will be supported for twelve (12) months – 1 year – from its general availability (GA) release date. For example :- SCCM CB 1511 is GA release date was 8th Dec 2015 (12/8/2015) and the support end date for SCCM CB 1511 is 8th Dec 2016 (12/8/2016). SCCM Life Cycle
So each SCCM/ConfigMgr CB version will go end of support exactly after a year of GA. So the question is whether all the SCCM CB versions (e.g. 1511, 1602 and 1606) will be fully supported if it’s not reached the end of support date? the answer is NO. Read on to get more details 😉 SCCM Life Cycle Details above?
END of Support Date details of SCCM CB Versions
SCCM CB 1511, 1602, 1606, 1610, 1702, and 1706 – End of Support – Already out of Security and Critical Updates servicing support !
There are two kinds of support for new SCCM/ConfigMgr Current Branch versions. First one is “Security and Critical Updates servicing phase” and the second one is “Security Updates (Only) servicing phase”. So what is the different between these two support scenarios? Are these similar to SCCM 2012/2007 “Mainstream Support” and “Extended Support” which I explained in the previous post here? I would say it’s similar approach. More details about SCCM Life Cycle:-
Security and Critical Updates servicing support
When running the latest current branch version of SCCM, at the moment it’s 1606, you will receive both Security and Critical updates. So, SCCM CB 1606 version will be fully supported and Microsoft will release Security and Critical updates until the next version of SCCM CB (probably 1610 version GA). Security and Critical Updates servicing support phase is already ended for SCCM CB 1511 and 1602
Security Updates (Only) servicing support
After a new SCCM CB version (e.g. 1606) release, support for older SCCM CB versions (e.g. 1511 and 1602) will get reduced to Security updates only for the remaining support span of months. For example:- Now, SCCM CB 1511 and 1602 are supported only for security updates and NOT supported for code defect that requires a critical update. So, SCCM CB 1511 and 1606 will release only security updates and they are not allowed to get any CRITICAL updates. That does mean (to me) that SCCM CB 1511 and 1602 infra may at risk up to an extend as it is already in LIMITED support scenario.
END of Support Date details of previous versions of SCCM
SCCM 2007 - Already Out of Mainstream Support SCCM 2007 - Extended support END date ==> 7th July 2019 SCCM 2012 - Mainstream support END date ==> 11th July 2017 SCCM 2012 - Extended Support END date ==> 12th July 2022
References SCCM Life Cycle?
SCCM 2012 and 2007 end of support details here SCCM CB 1511, 1602, 1606, 1610 end of support details here
Thank you!
I am planning to do sccm certification.Completion date with in next 6 months.Which version you suggest?
Go for 2016 version its pretty soon out
nice blog
Hi Anoop,
thank you for this great article! But I noticed the SCCM 2007 R3 Extended Support Date in this Article is wrong. According to Microsoft it is 9TH July 2019: https://support.microsoft.com/en-us/lifecycle/search?alpha=Microsoft%20System%20Center%20Configuration%20Manager%202007%20R3
kind regards
HI Anoop,
I missed the boat a bit here and cannot find the 1511 download. anyone know where I can find it now that its not supported? LOL
Hi Bryan ! – Yes, expected because SCCM CB 1511 is out of support and the baseline version which you should use in SCCM CB is 1606. Here is the link where you can get all the requirements https://www.anoopcnair.com/sccm-configmgr-2012-to-cb-1606-unofficial-upgrade-checklist/
Hello All , Is there any Microsoft Link where we can confirmed the SCCM 2007 has end of support ,Is the maintenance & support still continew ?
[…] More Details – End of Support Dates for SCCM CB […]
[…] As of writing this post, SQL 2017 is the latest version and ConfigMgr Current Branch 1702 is the baseline version and Windows Server 2008 R2 is not supported for site servers or most site system roles but does remain supported for the distribution point site system role (including pull-distribution points, and for PXE and multicast). You can check more on the depreciated OS for site system roles here and Current Branch support lifecycle here. […]