Co-management (cloud attach) enables you to manage Windows 10 or later devices simultaneously by using both Configuration Manager and Microsoft Intune. For more information about co-management, please refer here.
For a device to be co-managed, one of the pre-requisite is Windows devices must be connected to Azure AD using Hybrid Azure AD joined or Azure AD joined (cloud domain joined).
Currently, co-management supports the following workloads.
Co-management supports the following workloads:
- Compliance policies
- Windows Update policies
- Resource access policies
- Endpoint Protection
- Device configuration
- Office Click-to-Run apps
- Client apps
Let's assume, you have enabled the cloud attach (co-management) and you have also moved some of the workloads such as windows updates and device compliance policies to intune.
The devices will receive the policies and start communicating with Microsoft Intune for the applied workloads.
If you wanted to know the workloads applied for a specific device for troubleshooting purposes, you can either look at the intune console, for a specific device and check the intune managed workloads in the overview page.
The other way is to get the co-managed workload ID from the SCCM database and translate the workload ID into a descriptive value which is blogged by Ben
Although there is a co-management dashboard view within the SCCM console, it is limited and not possible to click the workloads to see data further.
And, I cannot find any reports available to see the workload information at a device level.
So, are you co-managed and you are interested to view the workloads applied to a specific device including the device hybrid azure adjoined or azure adjoined and other important information with one click view from the SCCM console, devices node?
I have this covered for you in this blog post.
when you right-click on a device in the SCCM console, you will see the Co-Mgmt workloads icon and click on that.
If the device is co-managed and workloads are switched to intune or with ConfigMgr, you will see the status in the workloads section.
If the device is not co-managed, you will see red color indicator with workload status as not Co-Managed. This is something you will need to troubleshoot further to get the device into co-managed state.
This tool is not applicable for server OS as co-management is applicable only to non-server OS (windows 10 and later OS).
How to implement the changes?
Download the files (co-managed workloads.zip) from Github.
Right click on the zip file, unblock the file.
Extract the files, you will find comanagement.workloads.ps1, and folder.
Edit Co-mgmt.Workloads.xml located inside folder ed9dee86-eadd-4ac8-82a1-7234a4646e62
You need to edit line 19 for the location of the PowerShell script. You can copy the comanagement.workloads.ps1 to your ConfigMgr admin location or anywhere that you have access.
"G:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\comanagement.workloads.ps1"
I copied it to the admin console install folder (bin).
Now, copy the folder (ed9dee86-eadd-4ac8-82a1-7234a4646e62) to XmlStorage\Extensions\Actions folder.
In my case, the actions folder is in G:\Program Files\Microsoft Configuration Manager\AdminConsole\XmlStorage\Extensions\Actions
Close the SCCM console (in case it is opened already) and launch the console again to see the changes.
I hope you find this tool useful for troubleshooting!
If you have any feedback on this tool or would like to add more data into the tool of device, please comment below.
