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

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

SCCM CB support scenarios differ from previous versions of the products, such as SCCM 2007 and SCCM 2012. In SCCM 2007 and 2012, we supported scenarios like “Mainstream Support” and “Extended Support.” This post will provide more details about the SCCM Life Cycle and support scenarios.

To build SCCM technical skills from the basics, refer to free SCCM training from the HTMD community. For more details, see Free SCCM Training 37 Hours Of Latest Technical Content Lab Setup HTMD Blog (anoopcnair.com).

We also have 63 Episodes of Free Intune Training for Device Management Admins. These trainings will help you understand modern management technologies such as Intune.

Sign up to get the best of How To Manage Devices straight to your inbox!

• SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr
• Free SCCM Training 37 Hours of Latest Technical Content Lab Setup
• Top 50+ Latest SCCM Interview Questions and Answers
• Top 75 Latest Intune Interview Questions and Answers

SCCM Life Cycle – Table Format – End of Support Dates for SCCM CB Current Branch ConfigMgr SCCM End of Life

You can find more details about supported versions of SCCM here. What are the end-of-support dates for SCCM CB’s current branch?

SCCM Mainstream Vs. Extended? – End of Support Dates for SCCM CB Current Branch ConfigMgr SCCM End of Life

The support scenarios for SCCM/ConfigMgr CB (Current Branch) do not fall into Mainstream and Extended. Instead, the SCCM CB support lifecycle is divided into two categories: “Security and Critical Updates servicing phase” and “Security Updates (Only) servicing phase.” The table below details the end Support Dates for the SCCM CB Current Branch.

Update:-

• SCCM CB 1710 and later, all support ends after the 18-month lifecycle for a current branch version has expired.
• SCCM CB versions before 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 that the SCCM CB product is released “few times” in a year. For example, in 2016, we already had SCCM CB 1602 and 1606 (and will we have 1610 ?). So, it isn’t easy to follow the old support life cycle.

The latest update is available here.

SCCM CB update versions (e.g., 1511, 1602, 1606, etc.) will be supported for twelve (12) months—one year—from their general availability (GA) release date. For example, SCCM CB 1511’s GA release date was 8 December 2015 (12/8/2015), and the support end date for SCCM CB 1511 is 8 December 2016 (12/8/2016). SCCM Life Cycle.

So, each SCCM/ConfigMgr CB version will end support precisely 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 they have 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 “Security and Critical Updates servicing phase” and 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 the SCCM Life Cycle:-

Security and Critical Updates Servicing Support

When running the latest current branch version of SCCM, 1606, you will receive both Security and Critical updates. End of Support Dates for SCCM CB Current Branch | ConfigMgr | Configuration Manager Endpoint Manager.

So, the 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 has already ended for SCCM CB 1511 and 1602.

Security Updates (Only) Servicing Support

After a new SCCM CB version (e.g., 1606) is released, support for older SCCM CB versions (e.g., 1511 and 1602) will be 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 for code defects requiring a critical update.

So, SCCM CB 1511 and 1606 will release only security updates and 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

Let’s discuss the END of Support Date details of earlier versions of SCCM. The screenshot below helps you show more information on SCCM versions.

• 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

We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.

Author

Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a 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.