Hello,
All of our Android 12 devices are reporting in with their Serial as HUBNOSERIAL.
Please advise on the remediation steps.
This is normal behavior for Android 12 devices that are enrolled with a Work Profile:
https://kb.vmware.com/s/article/82775?lang=en_US
In the patch notes for 21.5.0.48 there is the following entry:
AGGL-11510: Android 12 Profile Owner Device Serial Number "HubNoSerial".
However, I believe that with this fix, only the placeholder is no longer displayed.
This is normal behavior for Android 12 devices that are enrolled with a Work Profile:
https://kb.vmware.com/s/article/82775?lang=en_US
In the patch notes for 21.5.0.48 there is the following entry:
AGGL-11510: Android 12 Profile Owner Device Serial Number "HubNoSerial".
However, I believe that with this fix, only the placeholder is no longer displayed.
Thanks Alexander. This is problem for us as we depend on the Serial as a unique identifier. What is the suggested workaround?
I doubt that there is a workaround for BYOD (Work Profile). The fact that the DPC (=Intelligent Hub) can no longer access hardware identifiers (IMEI, MEID, serial number) with BYOD/Android 12 is Google's guideline.
The alternative would be COPE, but when it comes to employees' private devices, COPE is not an alternative.
Ivanti (MobileIron) is also affected by this and recommends not using hardware identifiers:
https://www.ivanti.com/blog/ivanti-delivers-day-zero-compatibility-and-key-feature-support-for-andro...
I personally find this change negative as well, since we have e.g. certificate templates for Wifi that also use serial numbers among other values. It just doesn't affect us as much because we primarily use COPE and Work Managed.