Update 1802 for System Center Configuration Manager available in Current Branch

My last week was full with System Center Configuration Manager :-). I delivered course 20703-1A: Administering System Center Configuration Manager, I took the Beta Exam 70-703: Administering Microsoft System Center Configuration Manager and Cloud Services Integration.

To make the week complete, some great news from the Configuration Manager Team:

Update 1802 for System Center Configuration Manager – Current Branch (CB) is now available!

Previously, it was available in Technical Preview branch, for early adopters.

The key word is co-management. This feature was introduced in Configuration Manager version 1710,  and enables you to concurrently manage Windows 10, version 1709 (Fall Creators Update) devices by using both Configuration Manager and Intune.

  • For on-premise management you need to install the System Center Configuration Manager client. This will offer you full management capabilities, as for other Windows desktop operating systems, based on System Center Configuration Manager infrastructure (Management Point, etc…)
  • For cloud-based management using Microsoft Intune, the device must be automatically enrolled in Azure AD for MDM and will use the OMA-DM protocol for management.

Update 1802 for System Center Configuration Manager is building on this feature with additional functionality.

Please note that you cannot use co-management with Hybrid MDM configuration. I would personally take a guess that co-management will eventually replace Hybrid MDM. Right now I believe this is the best way to manage Windows 10 devices both on-premise and on the Internet.

Please read more details on:

This entry was posted in Uncategorized. Bookmark the permalink.