Getting Ready for Apple Fall 2020 Releases (79996)
iOS 14 WiFi
This payload includes:
• Disable MAC address randomization
Paste the entire XML snippet (<dict>...</dict>) into the Custom XML payload in Workspace ONE UEM.
<string>Configures wireless connectivity settings.</string>
<string>WiFi (Example Wi-Fi)</string>
You can copy the XML as is without any modification.
While you can add this to the existing WiFi profile, I would suggest pushing this setting via a separate profile for easier management and troubleshooting in the future.
I was able to get it to work off my personal home wifi. But I'm having problems getting it to work off our corporate wifi which uses certificate based authentication. I had to set the PayloadDIsplayName to the name of the profile pushing the wifi package and the SSID_STR to the display name of the Wifi to get it to work on my home wifi with a separate profile package. Now we are trying to get it to work with the corporate wifi package but haven't had any success yet.
Looks like the most recent patch allows disabling of it:
18.104.22.168 Patch Resolved Issues
Thank you all. Like others have said, we were able to turn off but not keep it disabled with the custom XML file (we are SaaS 20.05).
If the patch in 20.8 will keep this setting disabled, then it's a good excuse for us to either upgrade or request the same patch be backported to our current version.
well...we just got some bad news today about the hotfix. They've informed us that this hotfix won't be available for 20.07 and we need to upgrade to 20.8. Considering we've only just upgraded last month to 20.07, and that support for this runs till January 2022, I don't understand why the hotfix can't be made available to an existing supported product.
Here's a response from VMware support:
"I have tested the MAC-Access Randomization profile using custom XML. Yes, the behaviour is the same as you mentioned i.e it disables the private IP but doesn't grey it out.
On testing the same feature on console 2008 to 2011 with the built-in option in the wifi payload the result is the same as above, the private IP is disabled with the profile but the user can turn it ON if they want."
So I guess that means there's no fix in sight unless anyone else heard differently?