Not SCCM 2016 Configuration Manager SCCM Current Branch version Download and Install? At last, the wait is over. Microsoft released the newest version of SCCM /ConfigMgr, known as SCCM/ConfigMgr Current Branch (CB).
SCCM CB will get updated every quarter along with Windows 10. It will be called SCCM 1511.
The version of SCCM won’t be called SCCM/ConfigMgr 2016, as I mentioned in the previous blog post here (What is the Next Version of SCCM ConfigMgr As A Service). To avoid confusion, don’t get confused with SCCM 2016; we don’t know whether there would be something called SCCM 2016 or 2017.
Not SCCM 2016 Configuration Manager
This version is the current branch of SCCM, and this will get updates every 4 months.
Download SCCM/ConfigMgr 1511 (not 2016) from MSDN here, Microsoft Evaluation Center, and Volume Licensing Service Center. I installed the SCCM 1511 version in the lab, and it has a few new options enabled, which were not there in the SCCM vNext Technical Preview versions. One of them is installed SCCM/ConfigMgr CAS (Central Administration Site) server.
CAS is not required for most of our organizations as SCCM 1511 primary server can support up to 200000 clients (200K). I’m escaped from CAS now !! What a relief. More details about SCCM 1511 here ConfigMgr team blog.
I would suggest going with a single SCCM 1511 primary server if your client count is near 200k, as we have an option to add the SCCM/ConfigMgr 1511 CAS server afterward. Following is the option to add CAS into your environment afterward.
The option is called “Join the Primary Site to an existing Hierarchy”.Another important point you need to take care of during the SCCM 1511 primary/CAS server installation is “Usage Data (telemetry)”.
The telemetry (Usage Data) helps SCCM 1511 collect the data over the internet to improve the product quality and installation/upgrade experience of the SCCM application. All the usage data sent to Microsoft will be encrypted, and there won’t be anything from which Microsoft can identify the customer details.
All the data will be hashed. More details in the TechNet article are here.
Choose and Control option is there in the above Wizard, where you can select the options of usage data like 1. Basic, 2. Enhanced and 3. Full. Basic level data includes data about the SCCM hierarchy; this data will help improve the installation and upgrade experience.
Example data collected would be site data, operating system version, time zone, Site roles, site numbers, DB performance metrics, and details of SCCM features enabled on the SCCM site.
Another new feature is to keep SCCM/ConfigMgr updated/up to date by connecting the on-prem SCCM infrastructure to ConfigMgr /SCCM cloud service. As I mentioned in the previous blog post here, this will help to upgrade and update SCCM / ConfigMgr environment very easily.
One another important point I’ve noticed with SCCM/ConfigMgr 151 prerequisite checks are:- AD system management container permission related warning (known bug) in the pre-requisite check seems to be fixed in the latest version of SCCM / ConfigMgr 1511.
This is the famous progress bar of SCCM/ConfigMgr 1511 primary site installation; nothing much changes here.
Here we go! The latest System Center Configuration Manager (SCCM/ConfigMgr) 1511. The version of the SCCM/ConfigMgr console is 5.0.8325.1000.
The site version of the latest SCCM/ConfigMgr release 1511 is 5.00.8325.1000.
SCCM Related Posts Real World Experiences Of SCCM Admins (anoopcnair.com)
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…
17 thoughts on “Not SCCM 2016 Configuration Manager SCCM Current Branch version Download Install”
Excellent info Anoop. You are the man !!!. The screenshots make it soooo easy to understand. I wonder if you can test any new tabs or features in SCCM 1511 and screenshot them (with functionality discussed) in your future posting – will be great.. Thanks again.
Sure Mate. Thank you:)
So it has to be a fresh install. Time to revamp home lab once the final release is OUT.
I would try in place upgrade from SCCM 2012 to SCCM CB 🙂
Can you verify or confirm that the Windows 10 Servicing within ConfigMgr 1511 is broken as any attempt for the rules to download the updates result in a certificate error?
This is very informative…
Hi Anoop, I’m planning to setting up 860 laptops with win 8.1 using SCCM please advice.thanks.Oki
I am currently running SCCM 2012 R2 SP1 Version 8239. Can I upgrade the current infrastructure to 1511 or would this need to be a fresh Install?
Yes, you can directly go to SCCM CB 1606, As SCCM CB 1511 is not available for download. You can also refer to https://www.anoopcnair.com/sccm-configmgr-2012-to-cb-1606-unofficial-upgrade-checklist/ and https://www.anoopcnair.com/perform-sccm-configmgr-cb-production-upgrade-1702-video-tutorial/ for more details
I have the same version 8239 and I see version 1606 is not available. What I should do?
I am in need to upgrade my SCCM 2012 R2 to SCCM 1511 but could not get setup dowloaders. can you please guide me over this
I am in need to upgrade my SCCM 2012 R2 to SCCM 1511 but could not get setup Files. can you please guide me over this
where i can download the SCCM V 1511
you can not (can’t) download SCCM CB 1511 as that version is not supported anymore. You can download SCCM CB 1706 and install that version
where i can download the SCCM V1511
What happens if we have a CM 2007 and want to stand up fresh CM2016 on Windows 2016 standard, do we have to create Systems Management folder or will the Systems Management folder from CM 2007 be used for CM 2016 CB 1511?
We want to keep SCCM CM 2007 up with no disruptions and stand up CM2016 151 CB What hapens to Systems Management container in this instance, NO VLAN’s in place t separate?
Hey – No. A separate AD extension is NOT needed for SCCM CB. This is one time activity for a forest and if you already did this for SCCM 2007 then, you are fine.
Yeah you can segregate the Boundary Groups in SCCM CB that will take of migration of clients in phased manner.
So you are fine with one VLAN as well