This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 77%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Hi all.
What's the timers for the removal of co-management from a device?
I've got a test device that I've removed the MECM agent and after just under 24 hours, Azure still think's its co-managed.
AzureAdJoined : YES
EnterpriseJoined : NO
DomainJoined : YES
From what I've read, it's a check on the device every 8 hours or so but after almost 24, this machine is still showing as:
Co-management
This Windows PC is being co-managed between Intune and Configuration Manager. Configuration Manager agent state is shown below, if the state is anything other than “Healthy” there are a few steps that help with this. Learn more
Configuration Manager agent state
Unknown
Think I've answered by own question. :)
Endpoint Manager isn't smart enough to know when the MECM agent has been removed it just puts it into an unhealthy state.
What worked for me is.
Remove the agent.
Remove the machine. (dsregcmd /leave)
Delete the device from the Endpoint Manager portal.
join the machine back. (dsregcmd /join)
Just in case this helps anyone else out.
What version of the ConfigMgr agent was installed on the endpoint? When I last tested this, with an endpoint that had the 2010 client agent installed, this worked without issue and the MEM console updated in short order.
Currently running 2103 (Client version 5.00.9012.1052)