Blogs

SCCM Current Branch: What’s New?

In December of 2015, Microsoft changed the servicing model for SCCM to what is now known as SCCM – Current Branch. This new servicing model is similar to servicing models in other Microsoft products such as Windows 10 where new versions and features are installed through semi-annual updates. These updates are installed via the SCCM console rather than the old method of upgrading through the installation media. Some of the features included in new versions can be designated as pre-release which gives administrators an opportunity to try out new feature sets before an official release to production.  More information can be found here:

https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/what-has-changed-from-configuration-manager-2012

Support Lifecycle:

Both SCCM 2007 and SCCM 2012 are out of mainstream support and have entered the extended support lifecycle. Current branch versions are supported for one year after general availability and consist of two phases. The Security and Critical Updates Phase for a version is available until the next version is released. Once a new version is released, the old version enters the Security Updates Phase.

 Support Lifecycle Information: https://support.microsoft.com/en-us/lifecycle/search/?p1=16222

Support for Current Branch: https://blogs.technet.microsoft.com/configurationmgr/2016/08/17/support-statement-for-microsoft-system-center-configuration-manager-current-branch-versions/

New Features:

Windows 10 Servicing: Ability to manage the Windows as a Service model for Windows 10 through the SCCM console.

 https://docs.microsoft.com/en-us/sccm/osd/deploy-use/manage-windows-as-a-service

Office 365 Updates: Management of Office 365 updates using the Software Updates feature set.

https://docs.microsoft.com/en-us/sccm/sum/deploy-use/manage-office-365-proplus-updates

Improved Software Center: New look and feel. Includes apps from the Application Catalog. Silverlight no longer required. Controlled through client settings.

https://docs.microsoft.com/en-us/sccm/apps/plan-design/plan-for-and-configure-application-management

Preferred Management Points: Ability to point clients to a specific Management Point rather than a random one.

https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/boundary-groups-for-1511-1602-and-1606

Client Cache Management: Administrators can now manage the client cache size through client settings.

https://docs.microsoft.com/en-us/sccm/core/clients/deploy/about-client-settings

Content Library Cleanup Tool: Tool that removes content from distribution points that is no longer associated with a package or application.

https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/content-library-cleanup-tool

Increased InTune Functionality: Major focus of System Center development. Ability to manage Android, iOS and Windows devices.

https://docs.microsoft.com/en-us/sccm/mdm/understand/whats-new-in-hybrid-mobile-device-management

Peer Cache (Pre-release): Peer to peer content sharing solution that can be used in locations that do not have servers available for distribution points.

https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/client-peer-cache

Cloud Management Gateway (Pre-release): New method of managing internet based clients using an Azure cloud service.

https://docs.microsoft.com/en-us/sccm/core/clients/manage/manage-clients-internet

Upgrade Path:

SCCM 2007: Re-architect and implement a new SCCM hierarchy. For most organizations, only a single site is needed with distribution points in remote offices. Install Current Branch version 1606 and then upgrade to latest version using the console.

https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/design-a-hierarchy-of-sites

SCCM 2012/SP1/R2: Upgrade to Current Branch version 1606 using the installation media. Then, use the console to upgrade to the latest version.

Site Servers on Server 2008 R2: This operating system is no longer supported for any SCCM roles except for the distribution point. Do not implement any new servers on this OS and make plans to remove any servers with this OS from your environment.

Client Upgrades: Use the automatic client upgrade feature built into the product to upgrade the client. This feature now has an option to designate a new client version as pre-production as well as exclude clients from the upgrade for the production version.

Upgrade information: https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager

Supported operating systems for site server: https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-operating-systems-for-site-system-servers

Client Upgrade information: https://docs.microsoft.com/en-s/sccm/core/clients/manage/upgrade/test-client-upgrades