Forum Discussion
Connection of already Hybrid Azure AD joined Win10 Devices to Intune Management
I have a similar situation although we do not have SCCM on premise. Devices have been Hybrid AD joined and Auto MDM enrolled through GPO but show up as Managed by MDM/ConfigMgr Agent. We do not have Configuration Manager OnPremise. How do i force MDM only?
Device Action status
USERNAME 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.
https://go.microsoft.com/fwlink/?linkid=2009258Hi
I have this same problem.
But i have SCCM co-management configuration set.
Co-management
the configuration is set to device collections.
I removed my test device from this collection and try to register it in Intune as being only managed by MDM.
Unfortunately, it still appears as MDM / ConfigMgr
The MDM policy is set.
How to change the device authorization for MDM, leaving other devices managed by co-management?
- nielsvdJul 10, 2019Copper Contributor
I successfully setup Hyrid ad join and co-management for some Pilot devices. Management is still controlled by ConfigMgr.
In the Azure console I see however stated that the Configmgr Agent state reports as could not connect. (See attached screenshot). Remote restart does work (with some delay) so there seems to be connection. Can anyone put me in the right direction how to troubleshoot this?
- Kamil2345Jul 16, 2019Copper Contributor
nielsvd It seems to me that the communication with the portal is done through the extension (Intune Management Extension - I do not remember the name) installed when connecting the device to Intune MDM.
I would check if the sccm agent on the device is working correctly, possibly reinstalling the agent. In addition, I would check sccm versions, windows10 versions. Not all versions work together.
Sometimes, after uninstalling the sccm agent, the garbage remains in the registry. Intune means the device as co-management but in reality the device does not have the sccm agent.