differences between SCCM ConfigMgr CB 1710 and 1706

Differences Between SCCM ConfigMgr CB 1710 and 1706

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

Differences Between SCCM ConfigMgr CB 1710 and 1706

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

Differences Between SCCM ConfigMgr CB 1710 and 1706

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.

Differences Between SCCM ConfigMgr CB 1710 and 1706

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.

Differences Between SCCM ConfigMgr CB 1710 and 1706

To make the parent-child relationship in the Task Sequence, you need to go through following steps:-

  1. In the task sequence editor, click Add, select General, and click Run Task Sequence.
  2. Click Browse to select the child task sequence.

More details about the nesting of task sequence here. More details available in the video tutorial here.


  • What’s new in version 1710 of SCCM – here
  • ConfigMgr Build 1710 –Run Task Sequence (Preview Feature) – here
  • Video Tutorial SCCM 1710 New Features Overview Plus Upgrade Guide – here
Install Dynamic Applications using SCCM CB Full Standalone Media 1

Install Dynamic Applications using SCCM CB Full Standalone Media

The SCCM CB standalone media wizard helps admin to create ISO file (.iso). This ISO file helps to build machines which are not connected to the network. Standalone media in SCCM contains everything that is required to deploy the operating system on a computer. The machine should not be connected to an SCCM CB site or the network. In this post, we will see whether we would be able to “Install Dynamic Applications using SCCM CB Full Standalone Media.”

In this post, we will also discuss about how to create SCCM CB offline standalone media with applications, collection variables, etc..

Check out the Offline Build Standalone Media Video here

SCCM Standalone media contains everything required for building an operating system on a machine. The applications and packages referenced in the Task Sequence will not get installed automatically as part of this offline media process.

Is this true for all the SCCM CB builds? Yes, it’s true that the dynamic apps or packages won’t get installed automatically. But, we have a user voice item to include these features into offline standalone media. You can check out the User Voice item from here.

Install Dynamic Applications using SCCM CB Full Standalone Media

As you can see in the above picture, the development work is already started on this User Voice item. The installation of dynamic applications and packages are not included in the latest version of SCCM CB 1709. But, the SCCM CB standalone media wizard has an option to include the content of dynamic applications referenced in the Task Sequence.

We can use SCCM SDK to build offline standalone media solution and include dynamic application installation feature as part of SCCM standalone media. But, it would be great if  we can include this option as a native feature of SCCM.

I think, the apps/packages which are referenced in original task sequence will get installed automatically.

How to Create SCCM CB Standalone Media?

Navigate via SCCM Console Software Library work-space – Operating Systems – Task Sequences.  Click on “Create Task Sequence Media” button from the ribbon menu of SCCM CB console.

Create Task Sequence Wizard has four media creation options. In this post, we are going to see how to create standalone media for SCCM CB.

  • Standalone Media – Creates media used to deploy operating systems without network access.
  • Bootable media – Creates media used to deploy operating systems using SCCM infra connectivity. This media won’t have the content of OS image and applications.
  • Capture media – Creates media used to capture operating system deployment image from a reference computer.
  • Prestaged media – Creates a file to be prestaged on a new hard drive that includes an operating system image

More details available in the video tutorial here

Install Dynamic Applications using SCCM CB Full Standalone MediaSpecify the media type – The media type page has two options. One for removal media like USB drive. Another option is CD/DVD set. You can also specify the media size – 4 GB, Unlimited, etc… You can specify the path where you want to save the ISO file of standalone media.

Select security settings for the media – We can set a password for standalone media to have more safety and avoid accidental OS re-imaging. Also, there is an option to set an expiry date for standalone media.

Select the Task Sequence which will help to rebuild the machine. This page will show you the details Task Sequence content. On the next page – Select application content to add, you can select the apps you want to have the part of Offline standalone media. The content of the selected apps and packages will be available for manual installation on the device.

On the Distribution Points page, specify the distribution points that contain the content required by the task sequence, and then click Next. You must have Read access rights to the content library on the distribution points. Make sure these contents are distributed to the DP. Otherwise, you won’t be able to create SCCM CB Standalone media.

More details available in the video tutorial here

Specify the variables that the task sequence uses to deploy the operating system. This will help to customize the Operating systems during the build. This could help to the installation of language pack, setting up timezone, regional settings, etc..

You will also have the option to specify any prestart commands that you want to run before the task sequence to SCCM standalone media.

Install Dynamic Applications using SCCM CB Full Standalone Media

How to Troubleshoot SCCM Standalone Media Creation Issues?

Most of the offline media issues are because of WMI or memory related. If you don’t have enough memory available on the machine where you are trying to create offline media then, you could get errors.

I have explained about another offline standalone media creation issue in the previous post “SCCM ConfigMgr 2012 R2 SP1 Create TsMedia failed with error 0x800b0108.”

Also, we can have a look at the log file CreateTsMedia.log . This log file will be located in the same location where your SCCM console is installed. C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog.

SCCM CB Full Standalone Media with Applications


Installation of  Dynamic Applications using standalone offline media is not supported with SCCM CB 1709. The content of these apps is part of standalone media. This helps to install the apps manually on the machine.I hope, SCCM PG will include this feature to have a better experience for SCCM admins/operation teams.

Sample SCCM CB Standalone :-

  Success: Task sequence media information  Success: Task sequence media information• Media type: CD/DVD set• Media size: Unlimited• Output path: \\SCCMTP1\Sources\Windows 10\Offline Media\Win10 Offline Media 1709 Copy1.iso• Allow unattended operating system deployment: No• Protect media with password: No• Task sequence: TP10001B-Windows 10 CYOD• Prestart command: No• Distribution point(s): SCCMTP1.INTUNE.COM• Total size of media content, MB:  4631• SHA256 checksums:  \\SCCMTP1\Sources\Windows 10\Offline Media\Win10 Offline Media 1709 Copy1.iso403CB70C4620245E85ACFA735D0C2B64C90DC3AAEC3792A55D8E523039377EC0   Success: Applications:• Mozilla Firefox (ach)   Success: Packages:• Microsoft Corporation User State Migration Tool for Windows 10.0.15063.0• Configuration Manager Client Package


  • Create stand-alone media with ConfigMgr – here
  • Support installation of packages/apps via dynamic variables in Standalone Media – here
Windows 10 Quality and Feature Update Policies for Intune 2

Windows 10 Quality and Feature Update Policies for Intune

Microsoft released Windows 10 1709 fall creators update. And the devices which are part of current branch (Semi-Annual Targeted) should get the Windows 10 1709 update in Settings – update and security  – Windows Update. Intune Windows 10 Quality Update Policies.

Microsoft Intune manages this Windows 10 device. In this post, we will see “Windows 10 1709 Fall Creators Update Upgrade with Intune Update Rings.”

Video Tutorial to Upgrade Windows 10 here

There are many methods to upgrade existing Windows 10 version to the latest version 1709. You can upgrade windows 10 with ISO file which is available in Visual Studio Subscriptions (previously known as MSDN) or VLSC (Volume Licensing Service Center). If Microsoft Intune manages your devices then, there would be a software update policy ring to manage Windows 10 feature updates.

Another related posts on Windows 10 Update Rings

FIX CBB Ring Devices are Getting CB Updates Intune Windows 10 Update Rings

Windows 10 1709 Fall Creators Update Upgrade with Intune Update Rings

Windows 10 Quality and Feature Update Policies for Intune 3

Navigate via Microsoft Azure – Microsoft Intune – Software Updates to get to “Windows 10 Update Rings.” This is the place where you can create Windows 10 Semi-Annual Targeted and Semi-Annual update rings. These two update rings in Intune would be able to control the Windows 10 upgrade behaviour for your organization. Intune Windows 10 Quality Update Policies.

Windows 10 Semi-Annual Targeted Update Ring – All the devices in Current Branch
Windows 10 Semi-Annual Update Ring – All the device in Current Branch for Business

Create Windows 10 Update Rings in Intune?

How to create Windows 10 update rings within Intune console? These Intune policy details are explained in one of my previous posts “How to Setup Windows 10 Software Update Policy Rings in Intune Azure Portal.”

Navigate via Intune console to get to Windows 10 Update Rings – Create Update RingSettings. We need to select “Servicing Branch” options according to your requirements. Feature update deferral period (days) is another setting which we want to setup as part of Create Update Ring policy.

For example:- If we set Service Branch = CB and Feature update deferral period (days) = 0 days then, the device will get the Windows 10 1709 updates on the 0 days of the release.

There are two types of Servicing Branches for Windows 10 as I mentioned in the above paragraph. Those servicing branches are Semi-Annual Targeted and Semi-Annual.

Select CB servicing branch (Semi-Annual Targeted) to set the devices for the first wave of deployment of Windows 10 features upgrades. The latest Windows 10 1709 Fall creators update is released only for Semi-Annual Targeted branch.

Windows 10 1709 Fall Creators Update with Intune Update RingsHow Does Windows 10 Update Rings Work?

Windows 10 update rings work flawlessly under the hood. I have not uploaded Windows 10 1709 ISO or files to Intune to deliver the updates to the devices. Intune helps to setup 2 MDM policies in Windows 10 1607 or later devices.

So, Devices are getting the Windows 10 feature updates binaries from any other Microsoft cloud service? Windows 10 devices are getting these feature update content/binaries from Windows Update for Business (WUfB).

Another important feature of Windows 10 is Delivery Optimization. Delivery optimization helps to find the binaries from the peer devices. These peer devices could be either from the same network or the internet.

Windows 10 Update Ring MDM policies?

Yes, the following are the two MDM policies which Intune set on Windows 10 devices. Intune Windows 10 Quality Update Policies.

CB/CBB Options :- MDM for version 1607 and above: MDM for version 1607 and above: ../Vendor/MSFT/Policy/Config/Update/BranchReadinessLevel \Microsoft\PolicyManager\default\Update\BranchReadinessLevel

Deferral Period Days:- MDM for version 1607 and above: ../Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatesPeriodInDays \Microsoft\PolicyManager\default\Update\DeferFeatureUpdatesPeriodInDays

Windows 10 Upgrade End User Experience

Windows 10 1709 fall creator update is getting delivered through Windows Update for Business in the following video. The following video will give you an end to end experience for Windows 10 1709 fall creators update upgrade process via Software Update for Business (WUfB).

As you can see in the video, the Windows 10 device is in CB (Semi-Annual Target) channel and differed period policy is set to Zero days. Intune Windows 10 Quality Update Policies.


  • What’s new for IT pros in Windows 10, version 1709 – Here
  • How to Setup Windows 10 Software Update Policy Rings in Intune Azure Portal – Here
  • Configure Windows Update for Business – Here
SCCM Guide - Learn How to Deploy Install Office 365 ProPlus Applications 4

SCCM Guide – Learn How to Deploy Install Office 365 ProPlus Applications

We can deploy Office 365 ProPlus apps (Word, Excel, PowerPoint, Outlook, etc..) to clients using SCCM CB. Beginning from SCCM version 1702, from Office 365 ProPlus Client Management dashboard, you can start the Office 365 ProPlus application Installer.


The new feature will let us configure Office 365 ProPlus installation settings, download files from Office Content Delivery Networks (CDNs), and deploy the files as an application. More details in the video tutorial here.

In this post, we will see the green field approach to deploy and install O365 ProPlus applications. I have another post which explain about “How to Deploy and Install Office 365 ProPlus Software Updates (patches) with SCCM CB ADR“.

What is Office 365 ProPlus Client Installer?

Office 365 client installer is nothing but Office 365 client applications installer. Is that bit clearer? So, which are those Office 365 Client applications? Word, Excel, PowerPoint, OneDrive, Outlook, etc.. Basically, OFFICE 365 ProPlus Client installer will help to install all these applications to end user devices like Windows 10, Windows 8 and Windows 7.

How to start the Office 365 ProPlus Client Installation Wizard?

You can start the Office 365 client installation wizard from SCCM console – \Software Library\Overview\Office 365 Client Management dashboard. Click on the + Office 365 Installer to launch the office 365 installer from SCCM CB console.

Office 365 client installation files will be downloaded to this location if they do not already exist. Without internet you can’t proceed to 2nd page of this wizard. This is incase if the you have not downloaded the Office 365 configuration files.

How to Deploy and Install Office 365 Applications via SCCM CB

You can set up all the client settings using “Import Client settings” option in Office 365 Client Installation Wizard. You can import the configuration.xml file to automatically configure all the settings of Word, Excel, PowerPoint, Outlook, etc.

Otherwise, you can select the option to manually configure all the settings via office 365 app installation wizard.

Select the list of Office 365 applications you want to Install

Select the Office Suite as part of the O365 apps installation wizard. There are two office suites available as part of the installation wizard.

Office 365 ProPlus
Office 365 Business

You will also get an option to select the Office 365 ProPlus Applications to include installation. I don’t want to install OneDrive for Business (Groove) application as it’s the old sync client. Rest of all apps will be installed on the Windows device as per your selection of the application from the wizard.

OneDrive for Business
Skype for Business

You have an option to select additional office products like Visio and Project. For those two products, there is a special licensing option. Those license options are also available Office 365 Subscription Standard Edition – Volume License. Professional Edition – Volume License. More details in the video tutorial here.

How to Deploy and Install Office 365 Applications via SCCM CB

Specify Client settings for Office 365 ProPlus Applications (Word, Excel, Outlook PowerPoint etc.)

Select the Architecture for Office 365 applications like Word, Excel, PowerPoint, etc..There are two versions 32bit Vs. 64bit. There are 4 update channels are available in SCCM Office 365 client install wizard.

But, recently these update models are changed. Following are the latest Office365 update models Monthly Channel (formerly Current Channel), Monthly Channel (Targeted), Semi-Annual Channel (Differed Channel) and Semi-Annual Targeted (formerly First Release for Deferred Channel).

You can have different languages for Office 365 applications. Depending on your preference or regions, you can select the language of applications. This wizard will help you to download the languages that will be downloaded for office 365.

You can also configure to “Accept EULA,” and Auto activate the applications. You can also have Pin Icons to the taskbar for Windows 8 and Windows 7 machines. The pin option is not applicable for Windows 10 devices. More details in the video tutorial here.

How to Deploy and Install Office 365 Applications via SCCM CB

How to Deploy and Schedule Office 365 ProPlus Apps via SCCM CB?

Deployment options/settings are also part of Office 365 Client Installation Wizard. You have to select the collection you want to deploy the Office 365 client on your SCCM CB environment. Select the content locations or DPs from Content page.

There are two types of Office 365 client installation options. Mandatory and Optional deployments. You can schedule the Office 365 client deployment as per your organization requires.

End User Experience of Office 365 App on Windows 10 Devices

You can see the Office 365 app listed in Software Center. As it was a mandatory deployment, it got automatically installed on Windows 10. All O365 Applications got installed on Windows 10 Device. The Office365 update channel is Current Channel (Monthly channel).

Excel, PowerPoint, Outlook, etc. apps are installed successfully on Windows 10 device. There was no internet connection on Windows 10 device hence the activation didn’t happen automatically. The License will automatically assign as per users subscription. You can launch all the applications (Word, Excel, PowerPoint, OneDrive, etc..) from Windows 10 machine after the install.

How to Deploy and Install Office 365 Applications via SCCM CB

Office 365 Client Management dashboard provides the details number of clients managed O365 clients in your SCCM CB hierarchy. How to create Office 365 ADR and How to deploy Office 365 Software Updates? More details in the video tutorial here.

Example of Office 365 Client Installation Wizard Configuration

 Application Settings
• Application name: Office 365 Client Install
• Administrator comments:
• Content Location: \\DC1\Sources\Office365\Client Install Pre Prod
 Office 365 Settings
• Suite: Office 365 ProPlus
• Excluded Applications: Groove
• Additional Office Products: None
• Edition: 64-Bit
• Channel: Current
• Languages: English (United States) default, Hindi (India), Malayalam (India)
• Version: 16.0.8326.2107
• Shared Computer Activation: False
• Pin Icons To Taskbar: True
• Autoactivate: False
• Accept EULA: True

• Collection: All Desktop and Server Clients
• Use default distribution point groups associated to this collection: False
• Automatically distribute content for dependencies: True
 Success: Content (1):
 Deployment Settings
• Action: Install
• Purpose: Required
• Pre-deploy software to the user's primary device: False
• Send wake-up packets: False
• Allow clients to use a metered Internet connection to download content: False
• Time based on: UTC
• Available Time: As soon as possible
• Deadline Time: Disabled
• Delayed enforcement on deployment Disabled
 User Experience
• User notifications: Display in Software Center and show all notifications
• Ignore Maintenance Windows: False
• System restart (if required to complete the installation): False
• Commit changes at deadline or during a maintenance win&dow (requires restarts): True
• Enable System Center Operations Manager maintenance mode: False
• Generate System Center Operations Manager alert when a software installation fails: False
• Create a deployment alert when the threshold is lower than the following:: False
• Create a deployment alert when the threshold is higher than the following: False

Sample Configuration.XML file configuration for Office 365

 <Add OfficeClientEdition="64" Channel="Current" Version="16.0.8326.2107" OfficeMgmtCOM="True">
 <Product ID="O365ProPlusRetail">
 <Language ID="en-US" />
 <Language ID="hi-IN" />
 <Language ID="ml-IN" />
 <ExcludeApp ID="Groove" />
 <Display AcceptEULA="TRUE" />
 <Property Name="SharedComputerLicensing" Value="0" />
 <Property Name="PinIconsToTaskbar" Value="TRUE" />
 <Property Name="AUTOACTIVATE" Value="0" />

References :-