Many devices says "See ConfigMgr" under Intune compliance

Question

The compliance workload has been switched to Intune for all devices here (about 7,000), however we've got several hundred that seem to be stuck on SCCM for this workload and are not switching over to Intune.

We've tried reboots, forcing device and user policy on the clients, etc and they remain showing as "See ConfigMgr" when you look at them on Intune, and the Workloads shown there is blank.

Any ideas please?

Answer 1

I notice the last sync time is a lit bit long, it is suggested to sync each policy again in CM agent to see if it persists.

If it still doesn't help, as Jason suggested, located to comanagementhandler.log to see if there is any errors.

-----------------------------------------------------------------------------------------------------------------------------

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

This example user has synced each policy, but the issue persists. However this issue appears to be affecting dozens, if not hundreds, of our devices and has been going on for weeks. It's not feasible to manually sync each of them. Besides in that time they really should have synced themselves several times at least.

Here's the Log file from the machine above. It had recycled very recently, so including the previous one for more history.

[90751-comanagementhandler-20210422-153233.log][1]

Answer 3

I noticed that there is a log uploaded, to protect you privacy, please make sure there is no private information included.

Can I know is the CM version 2006? If so,please make sure it has installed KB 4578605 and clients have upgraded to version 5.00.9012.1052 before completing the co-management onboarding process. It looks like the scenario described in KB4575787:
Co-management enrollment takes longer than expected for Configuration Manager clients

If clients have not yet upgraded to version 5.00.9012.1052 from KB 4578605, it is recommended first to disable automatic client upgrade on the Client Upgrade tab of Hierarchy Settings. This removes the need to upgrade clients twice in a row: once from the update rollup and once from this standalone update. The client.msp file shipping in this update contains all of the prior changes that shipped with update rollup KB 4578605.

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

We've decided to upgrade our SCCM platform to 2103 because we want to make use of the new feature update task sequence capabilities, and this is scheduled for tomorrow, subject to change request approval today.

I presume the Co-management issue mentioned above will be resolved in the 2103 update?

Answer 5

We completed the SCCM update to 2103 on Tuesday. The clients are all updating now.

One of the clients with the issue I was looking at previously has now been updated as of yesterday, he's now running version 5.00.9049.1010. Unfortunately 24 hours later, including at least two runs of the device and user policy download options, it still shows as "See ConfigMgr" in Intune. He does now show one Intune workload though, "Windows Update for Business". But compliance still doesn't seem to have moved over.