SCCM team released the newest PREVIEW version of SCCM CB 1706. I know, most of us are waiting for the production release of SCCM CB 1706. I hope, the production release of SCCM CB 1706 will happen somewhere in next month? As per my previous experience and analysis, not all newly introduced features got added to the production version. I expect the same thing might happen with the production version of SCCM CB 1706. I don’t think all the new features got introduced in the PREVIEW version of 1706 will make it to the production version of SCCM CB 1706. In this post, I’ll provide SCCM CB Preview Version 1706 Upgrade and New capabilities Overview Video guide.
The download of SCCM CB 1706 preview version and upgrade from SCCM CB 1705 preview version to 1706 is straightforward. The similar process is explained in the following video step by step guide “Step by Step Video Guide SCCM ConfigMgr CB TP 1705 Download and Upgrade“.
SCCM CB Primary Passive Site Server
Site server role high availability – Now, you can create a passive primary server with SCCM CB 1706 preview version and this passive primary server will use the same SQL database. The passive SCCM primary server can’t write anything to the DB. How to create SCCM CB Passive Primary server? In the console go to Administration > Site Configuration > Sites and start the Add Site System Roles Wizard.
SCCM CB SUP and Boundary Group Improvements
Improved boundary groups for SCCM CB 1706 preview software update points (SUP). Fallback for SUPs now uses a configurable time for fallback to neighbor boundary groups, with a minimum time of 120 minutes. Independent of the fallback configuration, a client attempts to reach the last software update point it used for 120 minutes. After failing to reach its original server for two hours, the client switches to a shorter cycle for contacting a new SUP.
Trigger Compliance Notification Alerts from SCCM CB 1706
There are some great improvements in Device compliance policy improvements. You can configure a time-ordered sequence of actions that are applied to devices that fall out of compliance. For example, you can notify users of non-compliant devices via e-mail or mark those devices non-compliant. This can be done via \Assets and Compliance\Overview\Compliance Settings\Compliance Policies\Compliance Notification Templates.
SCCM CB Compliance Policy options for AAD Registration and Antimalware
Also, I could see the new compliance policies for full SCCM clients which can be used in conjunction with Conditional Access for Managed PCs. Those compliance policies are Azure Active Directory Registration and Antimalware presence.
Android and iOS Enrollment Restrictions is Available in SCCM CB 1706
Admins can now specify that users can not enroll personal Android or iOS devices in their hybrid environment, limiting enrollment to pre-declared company-owned devices or DEP-enrolled devices only. You can configure this from Intune subscription under Cloud Services.
New client settings for Automatically Register the Domain Joined Devices to Azure AD (Default client policies)
New client settings to Configuration Manager. You’ll find these in the Cloud Services section. These settings give you the following capabilities: Control which Configuration Manager clients can access a configured cloud management gateway. Automatically register Windows 10 domain-joined SCCM clients with Azure Active Directory.
Other important Capabilities of SCCM CB 1706 PREVIEW version
- Create and Run Scripts – Create and run PowerShell scripts from the SCCM console
- Device Health Attestation assessment for compliance policies for conditional access
- Android for Work application management policy for copy-paste
- Android and iOS enrollment restrictions
- New mobile application management policy settings
- New Windows configuration item settings
- Cisco (IPsec) support for macOS VPN profiles
- Support for Entrust certification authorities
- Configure Windows Update for Business deferral policies
- Manage Microsoft Surface driver updates
- PXE network boot support for IPv6
- Changes to the Azure Services Wizard to support Upgrade Readiness
- SCCM console Accessibility improvements
- Specify a different content location for install content and uninstall content
- Hide task sequence progress
- Include trust for specific files and folders in a Device Guard policy
Capabilities in Technical Preview 1706 for SCCM CB – Here