Paths to co-management
Abhishek Yadav
SCCM Architect | Endpoint Mobility - Security | MDM | Intune | Azure | Autopilot | M365 | IAM | MECM | MEM
In my previous post we saw an overview of what Co-management is what it is not, options, pre-requisites, immediate values, benefits and other factors.
Lets move forward and have a look on how to get started and based upon your current configuration what are the paths to choose to enable co-management.
Microsoft offers two ways for organizations to set up co-management. Its important to have a clear understanding of the prerequisites for each path. Both the paths require combination of Microsoft Entra ID (AAD), Configuration Manager(SCCM\MECM), Microsoft Intune, and Windows 10 or Windows 11 client OS.
Path 1: Auto-enrollment of existing SCCM\MECM clients:
If you have existing SCCM managed devices\clients choosing this path will quickly enroll them into Intune. The management of these devices from SCCM will remain same as before you enable co-management. This will enable you to get all the cloud-based benefits. This path is transparent to your users.
The below diagram shows a diagrammatical representation of how to achieve this, with different available options:
Path 2: Enable Co-management for Cloud-Native Devices
The devices which were enrolled in Intune first AAD Join\Cloud-Native\Modern Provisioning\Cloud-first\Intune managed are a few terms how to define these devices. To Enable Co-management on these device you need to prepare your SCCM environment first by enabling\configuring E-HTTP, Cloud attach it to Azure services and install CMG, and the Deploy SCCM client from Intune using the CMG service (Auth token).
The below diagram shows a diagrammatical representation of how to achieve this:
We'll discuss about these 2 paths in details in upcoming posts!! Stay connected!!?????????