SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial Configuration Manager | Endpoint Manager

SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial Configuration Manager | Endpoint Manager?SCCM/ConfigMgr CB 1707 preview version got released last week. I had the pleasure of upgrading my SCCM CB 1706 preview version to 1707.

As expected, this was a straightforward process for me. I didn’t see any issues during the upgrade process of SCCM CB 1707. We see SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial in this post.

Step by Step Video Tutorial to upgrade SCCM CB 1706 to 1707 Preview

here

Preview versions of SCCM CB should NOT be deployed to a production environment. This is similar to the Windows insiders program, which helps SCCM admins to test the new features of SCCM CB. 

Before installing this version of the technical preview, you can go through the limitations of the SCCM CB version here.

Patch My PC
SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial Configuration Manager | Endpoint Manager
SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial Configuration Manager | Endpoint Manager

What are the New Features introduced in SCCM CB 1707 Preview?

Windows Defender application guard policies for Windows 10 RS3 and PowerShell Script parameter investments are my favorite features of the SCCM CB 1707 preview version.

  • Client Peer Cache support for express installation files for Windows 10 and Office 365
  • Surface Device dashboard
  • Percent of Surfaces
  • Percent of Surface models
  • Top five operating system versions
  • Configure and deploy Windows Defender Application Guard policies for Windows 10 RS3
  • Add parameters when you deploy PowerShell scripts

Known Issues with SCCM CB 1707 Upgrade

SCCM CB 1707 upgrade process is not changed much. It’s the same as the preview SCCM CB preview upgrades. There are new features introduced in this preview version. There are some known issues with an upgrade when you have a passive primary server installed. 

The issue is the only application for the SCCM environment with 1706 TP and used the site server always-on, a feature that means the passive site server was configured.

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc……………

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.