Forum Discussion
MDM Session: OMA-DM message failed to be sent. Result: (Unknown Win32 Error code: 0x80072efe).
- May 25, 2023
We believe we figured this out. We are still monitoring it but we believe that SSL decryption was the cause of this. Even though the Microsoft articles say to not do it to https://device.login.microsoftonline.com we tried that with no success we had to exclude all Microsoft traffic from being decrypted on our firewall via a Dynamic List. Hope this helps someone out!
Article in reference was https://learn.microsoft.com/en-us/azure/active-directory/devices/howto-hybrid-azure-ad-join that mentioned just that one URL.We also prevented our PCs from being Azure AD Registered as Hybrid was our preferred method and we set the following registry key.
HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin "BlockAADWorkplaceJoin"=dword:00000001
If you could share logs, I could take a look at it...
Any specific logs you are wanting?
- May 19, 2023depends.... 🙂
Try to sync the device and run this command (will fetch all logs... ms also uses it 🙂 )
wget https://aka.ms/intuneps1 -outfile IntuneODCStandAlone.ps1
powerShell -ExecutionPolicy Bypass -File .\IntuneODCStandAlone.ps1- imyouradminMay 19, 2023Copper ContributorPrivate message sent! Thanks!
- imyouradminMay 19, 2023Copper Contributor
Rudy_Ooms_MVP I'm working on getting the logs unfortunately people are actively using the computers so I will get it asap.
I do fine this interesting that they show up in Azure as a device with a MDM status:
But in Intune it doesn't even show up as a device:
You will have to trust me a little that the names are both correct.