Forum Discussion
MDM Session: OMA-DM session ended with status: (Unknown Win32 Error code: 0x80072f0c)
- Nov 29, 2020
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!
John Dooley IT Yes, I am afraid so. This is an error that has not been addressed by MS Support yet, as far as I am aware.
My solution to reinstall windows 10 20H2 from the cloud was rather crude and Federico's solution was more elegant.
But this should not occur in the first place, of course.
Good luck!
Martin
Autopilot reset therefore won’t fix this issue?
Thanks
John
- martingroenDec 01, 2020Copper Contributor
John Dooley IT Hi John, I am indeed referring to the new 20H2 feature. This works perfectly, with a good internet connection.
The problem I had was that MDM sync wasn't happening. Everything worked fine on the laptop itself, only the MDM sync didn't work with that mysterious error code as a result. I did a extensive search on the internet for more info on this error but to no avail. So, I decided to try this new cloud reinstall feature. And that helped. Apparently, during the previous update to 20H2 something went wrong which was corrected this time around.
I'm not using autopilot yet, but am planning to start using it. Hopefully that will make it easier to locate the source of these issues?
Thanks
Martin