I'm having a frustrating issue trying to enroll my device in Intune. Normally, I can resolve this kind of problem, but this time nothing's working. I've tried all the commands suggested by various guides, but to no avail. I even went to the extent of completely unjoining the domain, deleting all registry entries related to enrollment, and cleaning up tasks and MDE objects in Intune, Entra, and Active Directory before rejoining. After all that, I can only see an object in Entra marked with MDM as MDE and another one that is hybrid joined but not MDM. I'm concerned that MDE might be blocking the enrollment process, especially since we recently implemented a policy against non-hybrid joined devices. What am I missing? It's perplexing because I would think that taking such drastic measures would remove all traces of the device's connection to Intune or Entra. I even noticed that after reimaging, the device went directly to the Hello setup, and it appeared to register as expected with two MDE objects. Any advice would be greatly appreciated!
3 Answers
It’s worth checking if the device initially came with a Windows Home edition key. Sometimes configurations like that can cause issues with enterprise management setups.
You might want to consider reimaging the device. It’s not a common solution, but sometimes it saves you a lot of headaches trying to figure out the issue. Starting fresh from a known state can help get things back on track.
Have you checked the MDM authority? It could be locked elsewhere, preventing Intune enrollment. Make sure to verify that everything's set right on that front.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures