Co-Management is another buzz word in device management world. What is this co-management? Windows 10 co-management is a dual management capability available with Windows 10 1709 version (Fall Creators Update) and later. Co-management is the bridge between traditional management and modern management. In this post, we will see more details “Overview Windows 10 Co-Management with Intune and SCCM.”
Refer th the previous post to have more technical details – “How to Setup SCCM CB and Intune Co-Management“.
Topics Covered in this post
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 What is Enterprise Endpoint Experts (E³) Podcast?
Why Modern Management?
What are the problems with traditional management? Why are most of the organizations trying to get into modern management? It’s all about moving fast and adopt agile scrum method.
Traditional IT is designed to manage single business owned device which is always connected to corporate network. Devices and users landscape has changed over the years. To handle these changes in the modern world, IT needs to change.
Modern IT management should be agile and able to handle multiple flavours of devices for users. And it should be able to manage cloud managed SaaS applications. Automation, Pro-Activeness, and Self service are the other 3 trigger points for modern IT.
How to move from Traditional to Modern Management?
Co-management is the transition method proposed by Microsoft to move towards modern management. In my opinion, this transition method will help organizations who are having tons of on-prem infrastructure.
The first step of this transition should be Windows 10 co-management with SCCM and Intune. Prominent organizations can’t take a big leap towards modern management. Co-management is the best approach to transformation in a controlled and iterative way.
Entry Points to Co-Management?
1. SCCM + Domain Joined Devices 2. Intune + AAD Joined Devices
1. SCCM + Domain Joined Devices
Assume that your organization is already an SCCM shop and SCCM manages all the devices. In this scenario, we can offload some of your SCCM workloads to Intune.
When you have Windows 10 device which is already managed by SCCM client then, you can configure co-management to offload compliance policy workload to Intune. From my perspective, setting up compliance policy in Intune is much better experience than in SCCM. And moreover, there are some advanced controls in Intune compliance policies.
After the co-management configuration, compliance policies can be deployed via Intune. We don’t need to create and implement compliance policies from SCCM. Instead, we can use Intune to deploy compliance policies. Other workloads like Win 32 application deployment can be handled through SCCM.
2. Intune + AAD Joined Devices
Assume that you have Intune setup and your organization doesn’t have any on-prem infrastructure. The devices are already managed through Intune. As of today, we have some gaps with Intune management like Win 32 application deployment.
If your organization wants to deploy Win 32 application with some complicated command line to an Intune managed device then, we need to have some help from SCCM. This is where second entry point of Co-management comes into the picture.
You can configure the SCCM to perform co-manage of that machine with Intune as you can see in the co-management configuration video above. Intune can deploy an SCCM client to Intune managed devices so that the device would be capable of installing Win 32 applications via SCCM.
Co-Management SCCM Requirements?
Cloud Management Gateway (CMG) Cloud Distribution Point (CDP)
When you want to use both the entry points to co-management then, there are two prerequisites from SCCM side. Those requirements are CMG (Cloud Management Gateway) and Cloud DP (CDP). CDP and CMG are Platform as a Service (PaaS) solution in Azure. CMG and CDP have its prerequisites which I’m not going to cover on this blog.
The Cloud Management Gateway is SCCM proxy solution hosted in Azure cloud service. I assume CMG communication flow is similar to that of Azure App Proxy.
Example:- A client from internet contacts SCCM to get policies. The request will reach CMG. And the CMG will forward this request from a client to on-prem SCCM components. The on prem SCCM component will validate the request and provide policies via CMG.
The Cloud Distribution Point is another PaaS solution in Azure, and it’s a content location in the cloud. The CDP role is similar to on-prem Distribution Point role. The clients from the internet can easily get the content from Cloud Distribution Point.
Sample High-Level Architecture of Co-Management with SCCM & Intune
What is Enterprise Endpoint Experts (E³) Podcast?
Adaptiva has insightful articles and videos from IT industry experts on their website Adaptiva Academy. E³ podcast is an excellent resource for video/audio interviews with SCCM, Intune, Security experts from the industry.
Bill is an excellent host of Adaptiva’s E³ podcasts. He is very serious with all his interviews. I had a unique experience being his guest for this month’s Enterprise Endpoint Experts (E³) Podcast. You can watch the interview from here.