End of Support Dates for SCCM CB Current Branch | ConfigMgr | SCCM End of Life

End of Support Dates for SCCM CB Current Branch | ConfigMgr (SCCM End of Life)? Let’s find out the end of support dates for SCCM Current Branch? In this post, you can find the ConfigMgr life cycle management in the table format.

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 supported 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 – End of Support Dates for SCCM CB Current Branch?

You can find more details about supported versions of SCCM here. End of Support Dates for SCCM CB Current Branch?

SCCM Version	Availability Date	Support End Date
2203	8th April 2021	October 6, 2023
2111	December 1, 2021	June 1, 2023
2107	August 2, 2021	February 2, 2023
2103	April 5, 2021	October 5, 2022
2010	Nov 30, 2020	May 30, 2022
2006	August 11, 2020	February 11, 2022
2002	April 1, 2020	October 1, 2021
1910	Nov 27, 2019	May 29, 2021
1906	July 26, 2019	January 26, 2021
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) do not fall into 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 the SCCM CB Current Branch are 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 a more detailed explanation of these two new categories at the end of this post. The main reason for this change is because the 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 to follow the old support life cycle.

The latest update is 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 the 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 End of Life

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. The first one is the “Security and Critical Updates servicing phase” and the second one is the “Security Updates (Only) servicing phase”.

So what is the difference 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 a 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, and you will receive both Security and Critical updates. End of Support Dates for SCCM CB Current Branch | ConfigMgr | Configuration Manager Endpoint Manager.

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). The 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, SCCM CB 1511 and 1602 are supported only for security updates and NOT supported for code defects requiring 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 be at risk up to an extent as it is already in a 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

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with over 17 years of experience (calculation done in 2018). He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc….…