So, SCCM/ConfigMgr is also following the Windows servicing model (Windows As-a-Service). To support Windows 10 servicing models, the enterprise client management software like SCCM/ConfigMgr should also follow the same servicing model and that would be SCCM/ConfigMgr as-a-Service. No SCCM 2016 – SCCM as a Service.
No SCCM 2016 But It’s SCCM Current Branch
Going forward SCCM/ConfigMgr will also have servicing model, the Next Version of the SCCM product won’t be called (NO) SCCM 2016. The upcoming versions of SCCM will be branded as SCCM YYMM (e.g ConfigMgr 1510). ConfigMgr 1510 is the latest preview version released in the month OCT (MM=10) and the YEAR 2015 (YY=15).
SCCM Current Branch (CB) = YYMM = SCCM 1810
More details about the Windows servicing model are here. So the question is about SCCM 2012 and Windows 10 support? What kind of support SCCM 2012 will provide for the Windows Servicing Branches? More details about this are in Brad Anderson’s post. Also more details in Aaron Czechowski’s post here.
When you are using SCCM (NO SCCM 2016) to update Windows 10 rather than Windows Updates then you can utilize SCCM vNext servicing model to get more control over the Windows 10 upgrades in your organization. More details about this are in the post here.
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management 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. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…