Home

WiFi Device Configuration Profile - Error WindowsWifiEnterpriseEAPConfiguration 0x87d1fde8

%3CLINGO-SUB%20id%3D%22lingo-sub-319787%22%20slang%3D%22en-US%22%3EWiFi%20Device%20Configuration%20Profile%20-%20Error%20WindowsWifiEnterpriseEAPConfiguration%200x87d1fde8%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-319787%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20assigning%20our%20first%20WiFi%20Device%20Configuration%20Profile%2C%20most%20of%20our%20devices%20are%20now%20non-compliant%2C%20with%20the%20following%20error...%3CBR%20%2F%3E%3CBR%20%2F%3ESETTING%3A%20WindowsWifiEnterpriseEAPConfiguration%3CBR%20%2F%3ESTATE%3A%20Error%3CBR%20%2F%3ESOURCE%20PROFILES%3A%20Source%20Profile%20WiFi%20PeckhamData%3CBR%20%2F%3EERROR%20CODE%3A%200x87d1fde8%3CBR%20%2F%3EERROR%20DETAILS%3A%20Remediation%20failed%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20researching%20this%20error%2C%20I%20found%20an%20older%20blog%20post%20about%20how%20to%20create%20a%20custom%20OMA-URI%20policy%20to%20deploy%20WiFi%20settings...%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Ftune_in_to_windows_intune%2F2015%2F01%2F19%2Fdeploy-wi-fi-profiles-to-windows-phone-devices-with-microsoft-intune-oma-uri-policy%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EDeploy%20Wi-Fi%20profiles%20to%20Windows%20Phone%20devices%20with%20Microsoft%20Intune%20OMA-URI%20policy%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20this%20article%2C%20there%20is%20a%20reference%20to%20the%20error%20we%20are%20receiving.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEM%3EThere%20is%20an%20undocumented%20value%20which%20requires%20for%20the%20hex%20value%20of%20the%20Wi-Fi%20name.%20This%20value%20should%20be%20added%20before%20the%20SSID%20name%20(see%20example%20below).%20If%20this%20value%20is%20not%20configured%2C%20the%20Wi-Fi%20profile%20will%20function%20but%20Microsoft%20Intune%20will%20report%20this%20as%20an%20error%20(0x87D1FDE8)%20non-compliant.%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3ECould%20it%20be%20that%20the%20new(er)%20WiFi%20Configuration%20Type%20is%20not%20properly%20configuring%20the%20%22hex%20value%20of%20the%20Wi-Fi%20name%22%3F%20And%2C%20if%20this%20is%20a%20bug%2C%20how%20would%20I%20report%20it%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20help%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-319787%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Nathan Hartley
Occasional Contributor

After assigning our first WiFi Device Configuration Profile, most of our devices are now non-compliant, with the following error...

SETTING: WindowsWifiEnterpriseEAPConfiguration
STATE: Error
SOURCE PROFILES: Source Profile WiFi PeckhamData
ERROR CODE: 0x87d1fde8
ERROR DETAILS: Remediation failed

When researching this error, I found an older blog post about how to create a custom OMA-URI policy to deploy WiFi settings...

Deploy Wi-Fi profiles to Windows Phone devices with Microsoft Intune OMA-URI policy

In this article, there is a reference to the error we are receiving.

There is an undocumented value which requires for the hex value of the Wi-Fi name. This value should be added before the SSID name (see example below). If this value is not configured, the Wi-Fi profile will function but Microsoft Intune will report this as an error (0x87D1FDE8) non-compliant.

Could it be that the new(er) WiFi Configuration Type is not properly configuring the "hex value of the Wi-Fi name"? And, if this is a bug, how would I report it?

Any help would be greatly appreciated.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies