Event banner

AMA: Managing Windows with Microsoft Endpoint Manager

Event Ended
Thursday, Nov 18, 2021, 08:00 AM PST
Online

Event details

Join us for Tech Community Live: Microsoft Endpoint Manager edition! From Windows Autopilot to Zero Trust, this live Ask Microsoft Anything (AMA) event is your chance to bring your Windows managem...
Heather_Poulsen
Updated Dec 27, 2024
AMA
Andy0401's avatar
Andy0401
Copper Contributor
Nov 18, 2021
We established Co-Management for a test collection and moved Windows update workload to the test collection. Unfortunatley the client is still recognized as Config Manager managed in intune. Any idea where I can find some logs or information why this is not correct? The configuration was done about two months ago...
Jason_Sandys's avatar
Jason_Sandys
Icon for Microsoft rankMicrosoft
Nov 18, 2021
Hi Andreas, can you be a bit more specific about what this means: "Unfortunatley the client is still recognized as Config Manager managed in intune."? Have you reviewed the Co-management status of the ConfigMgr client itself by reviewing the properties in the ConfigMgr Control Panel Applet as well as the comanagementhandler.log on the client?
  • Andy0401's avatar
    Andy0401
    Copper Contributor
    Nov 18, 2021
    Hi Jason, in the endpoint manager console under devices the client is still marked as "managed by ConfigMgr". I would expect to see here Co-Managed.
    • Jason_Sandys's avatar
      Jason_Sandys
      Icon for Microsoft rankMicrosoft
      Nov 18, 2021
      That's correct assuming the client itself is properly enrolled in Intune. Thus, can you please check the control panel applet and log file as noted.
    • Andy0401's avatar
      Andy0401
      Copper Contributor
      Nov 18, 2021
      on the client the config mgr shows "co-managment capabilites = 1" and Co-Management = disabled (just recognized)
Date and Time
Nov 18, 20218:00 AM - 9:00 AM PST