MDM Compliance reports do not include the Mobility Manager ID, so it is difficult to match the device record to other reports or to the Devices view
Last Updated July 19, 2016
When we run multiple reports and try to club the data then we don't have an unique value to take it as refernece
to match up the data in the multiple reports.
For e.g. If we download "device details" and "apps installed by users" report then we don't have an unique value to
use as a reference to match up the apps installed on a particular device.
Reported Mobility Manager ID prior to SMS 5.5.1 is reporting device_unique_identifier therefore it won't be helpful
as an unique referenece value.
Please note: Multiple devices can have same user, email address and device name so these 3 values can't be considered
as unique value.
No error message
The following reports did not have a unique identifier for the
device within the report...
- MDM compliance status
- MDM non-compliant devices
- Work Mail status
So it was difficult to associate a device within these reports with devices in other reports.
It should also be noted that the "Apps installed by users" report was reporting the "Mobility Manager ID" as
the device's unique_identifier instead of the devices 'acid' value, and this was incorrect as all other places within the UI
the Mobility Manager ID is the acid and not the unique_identifier.
Added the "Mobility Manager ID" column to the 3 reports mentioned above and also corrected the "Mobility Manager ID"
column within the "Apps installed by users" report.
MDM Compliance reports do not include the Mobility Manager ID, so it is difficult to match the device record to other reports or to the Devices view.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe