Microsoft has introduced new model of versioning to System Center Configuration Manager, This is called Current Branch. It will transformed the way Configuration Manager delivered, moving from longer release cycles to regular updates designed to support the faster pace of updates for Windows 10 and Microsoft Intune. Each current branch versions will be supported for 12 months, and it can be upgraded to the next version without any hassle.
This is the Part 01 of Upgrading SCCM 2012 SP1/SP2/R2 to SCCM 1511 post. This article describe what are the new features of SCCM 1511, its supported configurations, Supported upgrade paths and Prerequisites which you have to perform before the upgrade. Part 02 of this article will contain step by step instruction on how to do a clean upgrade to 1511.
New Features
Configuration Manger 1511 released in 2015 December. That’s how the version number defined to 1511, Year and the Month of the release date. The console and looks are no more different than SCCM 2012, it is not like 2007 to 2012 jump, but there are much more exciting new functionalities added.
System Center Configuration Manager has the ability to manage Office 365 client updates by using the software update management workflow
Ability to create multiple automatic deployment rules
When a new client version is released, you can deploy them to a pre-production environment and test the behavior, if the test was successful, you can move to update the production environment.
Software center has an improved new look and the applications which resides in the application catalog is now available in the software center. It is rather convenient feature. Also Silver-light requirement removed.
Windows 7, 8, 8.1 can be upgraded to windows 10 using this task sequence, its way better than traditional OSD, faster, reliable and persists all your existing data and applications
Supported Configurations
Refer the following TechNet articles for supported configurations
Supported Upgrade Paths
If you have SCCM 2012 SP1 and above in place upgrade to 1511 is supported. Upgrade is very similar to installing a service pack. If you have a SCCM hierarchy first Central site need to be upgraded, Then Primary sites and secondary sites should be upgraded. Following are list of versions that supported on in-place upgrade.
Prerequisites Before the Upgrade
ADK 10 for 1511 had some issues with SCCM and Microsoft also does not recommend to use it. (here). The older version of ADK for Windows 10 still can be downloaded and it can be used to deploy Windows 10. (here)
You have to install the KB3095113 if you are running Windows server 2012 or 2012R2 Operating Systems
if you are downloading from the Microsoft Volume licensing site, it is named “System Center Config Mgr Client Mgmt License (current branch)” you have to click that and then it will show the version number as 1511.
Download - System Center Config Mgr Client Mgmt License (current branch)
SCCM 1511 is available in MSDN and Evaluation Center
Perform Test Database Upgrade
Testing the database upgrade is a prerequisite that can be performed before the production upgrade. It will minimize the risk of a failure of production environment upgrade. This will require a VM with the same version of SQL installed. Then backup of the primary site database will be restored to this VM and the test upgrade can be performed.
Follow the Part 02 of this post which will contain step by step instruction on how to perform an In-place upgrade to SCCM 1511.
Cheers
Asitha De Silva