Forum Discussion
MDM Session: OMA-DM session ended with status: (Unknown Win32 Error code: 0x80072f0c)
Hi,
An increasing number of devices are getting a non compatible status. Is active is non-compatible. When inspecting the event logs with event viewer I see the following error message.
MDM Session: OMA-DM session ended with status: (Unknown Win32 Error code: 0x80072f0c)
This error code did not lead to any results after a search on the internet, so I thought let's try it here. Does anybody have any ideas how I can resolve this?
Thanks a lot
Best wishes
Martin
martingroenHey, I worked on this today and was able to resolve it on several computers without resorting to reinstalling Windows, if you are interested. First, I removed the computers from the AAD Connect sync and GPO scope and completely purged them from Intune and AAD. I then ran dsregcmd /leave from an elevated command prompt on each workstation console. Next, navigate to the following registry hive on each impacted workstation: HKLM\SOFTWARE\Microsoft\Enrollments. Delete as many GUID-named keys as possible from this directory (example attached). Ignore any keys that cannot be deleted. Now restart the workstation and add it back to the AAD Connect sync and GPO containers/groups. Once I logged back in with a MEM-licensed AAD user (user auto enrollment), my devices were once again managed by Intune within the next ~15 minutes. Good luck and thanks for your collaboration on this!
martingroen Did you ever get any help for this? I am having the exact same problem, thanks
NFederico No one offered any help. It is a weird error message. I couldnt find any mention of it on the internet.
What version of Windows 10 are you on? This happened with a couple of laptops that had upgraded themselves to Windows 10 20H2. I resolved the matter by resetting the Windows installation from the cloud. Now they are happily syncing again with Intune.
Best wishes
Martin
martingroen Yes! That is exactly what happened with ours as well! We upgraded to edition 19041 (2004) and these workstations immediately stopped checking in to Intune and now we cannot re-enroll them. What do you mean by "resetting the Windows installation"? Do you mean you rolled back the upgrade? Unfortunately I am not in the position to do that because we require 2004 for full Windows Defender Application Control functionality with custom OMA-URIs
I had a similar issue that lead me to this page, My error code was a little different but the same steps worked to resolve the issue.
So thanks for this information, was banging my head against the wall for a few days trying to figure this out 🙂
