10 Reasons to upgradeTo Configuration Manager Current Branch
Kim OppalfensKenny BuntinxTim De Keukelaere
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
Speakers
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
# 01 – NEW SERVICING MODEL
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
In the old days …
• Major Release
– Cumulative Updates
– Hotfixes
– Service Packs
• Next Release
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
Now
• “ConfigMgr as a
service”
• Updates and
Servicing node
• Service Connection
Point
• Online or offline
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
# 02 – CLIENT MANAGEMENT
IMPROVEMENTS
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
Client Piloting
• 3 simple steps
– Configure to use preproduction collection
– Install update (including
new client)
– Promote new client to
production
• See progress in
Monitoring workspace
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
Client Online Status
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
New Software Center
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
# 03 – OS UPGRADE SUPPORT
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
Site server OS
• In place upgrade supported
• For sites running 1602 or later
• Important: Uninstall WSUS 3.2
First
• Using standard upgrade
procedures for Windows Server
• No site restore needed
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
# 04 – ON PREM MDM VS FULL
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
#ECMCDMDay2016
Light-way vs full management
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
# 05 – WINDOWS 10 CONDITIONAL
ACCESS AND PPHC
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
#ECMCDMDay2016
Services
• Sharepoint Online
• Exchange Online
• On-premises Exchange
Starting from Configuration Manager 1602
• Windows 10 Conditional Access with Device Attestion Service
• Pre-release Conditional Access for Managed PCs
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
#ECMCDMDay2016
Device health attestation lets the administrator ensure that client
computers have the following trustworthy BIOS, TPM, and boot software
configurations enabled:
• Early-launch antimalware
• BitLocker
• Secure Boot
• Code Integrity
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
#ECMCDMDay2016
• Device Health Attestation Service – How does it works ?
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
#ECMCDMDay2016
• Device Health Attestation Service Dashboard
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
#ECMCDMDay2016
• Conditional Access based on Device Health
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
# 06 – WINDOWS 10 / OFFICE 365
SERVICING
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
#ECMCDMDay2016
• Natively manage Office 365 desktop client update thru the
regular software update channel
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
#ECMCDMDay2016
• View your state of Windows as a service
• Create servicing plans to form deployment rings
• Ensure that Windows 10 current branch systems are kept up to
date when new builds are released
• View when clients are near end of support for their build of CB
or CBB.
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
# 07 – ENDPOINT PROTECTION
IMPROVEMENTS
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
#ECMCDMDay2016
• New Endpoint protection policies such as PUA
• New Dashboards
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
Kim
• Related objects
improvements
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
Kim
• ”Cluster aware
updating” feature
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
Kim
• Automatic
deployment rule –
Multiple Deployments
#ECMCDMDay2016
10 REASONS TO UPGRADE TO CONFIGMGR CURRENT BRANCH
Kim
• More ”right-
click”actions
#ECMCDMDay2016
Gold Sponsors
Silver Sponsors
Special thanks to our sponsors!