End of Support Dates for SCCM CB Current Branch

10
SCCM Life Cycle

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 SCCM Life Cycle in this post.

However, 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

Table – SCCM Life Cycle

VersionAvailability DateSupport End Date
1810Nov?, 2018??
1806July 31, 2018January 31, 2020
1802March 22, 2018September 22, 2019
1710November 20, 2017May 20, 2019
1706July 31, 2017July 31, 2018
1702March 27, 2017March 27, 2018
1610November 18, 2016November 18, 2017
1606July 22, 2016July 22, 2017
1602March 11, 2016March 11, 2017
1511December 8, 2015December 8, 2016

SCCM_CB_EndofLife_Support_2

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   – End of Support = 8th Dec 2016  – Already out of Security and Critical Updates servicing support !
SCCM CB 1602 – End of Support  = 11th March 2017 – Already out of Security and Critical Updates servicing support !
SCCM CB 1606 – End of Support  = 22nd July 2017Fully Supported !

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:-

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.

SCCM_CB_EndofLife_Support_1

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

 

10 COMMENTS

  1. 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

  2. Hello All , Is there any Microsoft Link where we can confirmed the SCCM 2007 has end of support ,Is the maintenance & support still continew ?

  3. […] 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. […]

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.