This post is to give you high-level differences between two versions of SCCM/ ConfigMgr. These versions are latest production version SCCM CB 1710 and previous production version SCCM CB 1706. This post helps you to go through major “differences between SCCM ConfigMgr CB 1710 and 1706”.
Another difference between 1706 and 1710 is explained in the following post “WQL Query SMS Units Changes after SCCM CB 1710 Upgrade“.
Console - SCCM CB 1706 = Version 1710 Console version: 5:00.8577.1000 Site Version: 5.0.8577.1000
Subscribe my YouTube Channel here
In this SCCM comparison video, we see the improvements available in the latest production version of CM CB 1710. Most of the parts concentrating on GUI changes happened for SCCM 1710 console. Also, we see some deep dives on new features, tools and settings got introduced in SCCM CB 1710 version. This post will also give a highlight of all the major differences between SCCM ConfigMgr CB 1710 and 1706.
Quick Look at SCCM CB 1710 Features
20 Feature Release 1710, 17 Feature Release in 1706 7 Pre Release Feature in both 1710 and 1706
Following are the major differences between SCCM ConfigMgr CB 1710 and 1706 regarding features. Client Peer Cache is no more a pre-release feature. Client peer cache is moved to RELEASE feature type in SCCM CB 1710. TS content pre-caching was a pre-release feature in 1706 but in SCCM CB 1710 it’s feature type is RELEASE.
Device Health Attestation assessment for compliance, Windows Defender Application Control, and Windows defender exploit guard are NEW Pre Release feature. A pre-release feature called “Device Guard” is no more available in Features list of 1710. Device Guard policies have been renamed to Windows Defender Application Control policies.
Cloud Services Available in SCCM CB 1710
There is a new cloud service added in 1710, and that is Co-Management. I have a previous post which has more details about Windows 10 Co-Management with Intune and SCCM. Following are the topics which I covered in that post. This is differences between SCCM ConfigMgr CB 1710 and 1706 regarding Cloud Services.
Why Modern Management? How to move from Traditional Management to Modern Management? Entry Points to Co-Management? Co-Management SCCM Requirements? Sample High Level Architecture of Co-Management with SCCM & Intune
SCCM 1710 and 1706 site Server Properties details are also explained in the video tutorial here. Following are the differences between SCCM ConfigMgr CB 1710 and 1706 regarding build versions.
Build number of 1710 = 8577 Build number of 1706 = 8540
New Client Settings Options available in SCCM 1710
There is two new client settings option available in SCCM/ConfigMgr CB 1710 version. One is related to Client cache settings, and the other one is something to do with Software Center customisation. The major differences between SCCM ConfigMgr CB 1710 and 1706 in terms client settings.
Client Cache Settings – Enable HTTPS for client peer communication is NOT available in 1710. I hope the communication is more secured in 1710 and there is no option to have HTTP communication in the latest version of SCCM. More details available in the video tutorial here.
Another difference I could spot in SCCM 1710 version is customisation option for Software Center. This was available for Intune hybrid customers in the previous versions of SCCM CB. But this customisation option is available for all SCCM customers!
You can customise the software center with company logo, custom colour theme, etc. This is very helpful when you are a service provider and provides services to different customers. We can have different Software center client settings policies for each customer.
I did go through Application model and MAM (Application Management) policies. But I didn’t find any significant difference between two version of SCCM CB. More details available in the video tutorial here. There are some improvements to “Run Scripts”, and 2 MAM policies are added to 1710 production.
Nesting of Task Sequence in SCCM CB 1710
Are you missing Run Task Sequence step in General? Run Task Sequence Step is a pre-release version. This feature is NOT enabled by default. You need to agree to the consent to enable this feature and then enable it from Updates and Servicing – Features node.
To make the parent-child relationship in the Task Sequence, you need to go through following steps:-
- In the task sequence editor, click Add, select General, and click Run Task Sequence.
- Click Browse to select the child task sequence.