Identifying imported mobile devices and their users
This section describes how Matrix42 Enterprise Service Management identifies mobile devices that are imported from Silverback. Besides, it describes how Matrix42 Enterprise Service Management identifies users of mobile devices that are imported from Silverback and AirWatch.
Silverback: identifying imported mobile devices
When identifying the imported mobile devices for Silverback, Matrix42 Enterprise Service Management uses the following data:
- Manufacturer Unique Device ID (UDID). Unique identifier that is provided by the operating system of the mobile device and is available for all devices.
- IMEI, WiFi MAC, Serial Number. Additional unique identifiers that are provided by the operating system of the mobile device but are not available for all devices.
The table below shows the identifiers (matching criteria) for available operational systems/devices and Silverback device platforms. These identifiers should detect duplicated device records, which may result from different connector imports.
If two devices have the same matching criteria (for example, IMEI+Serial Number) but different enrollment statuses, only a device with the enrollment status of higher priority is imported to Matrix42 Enterprise Service Management.
| OS/Device | Silverback Device Platform | Manufacturer UDID | IMEI | WiFi MAC | Serial Number |
|---|---|---|---|---|---|
| iPhone (iOS) | iphone | ok (#1) | ok (#4) | ok (#3) | ok (#2) |
| iPad (iOS) | ipad | ok (#1) | ok (#4) | ok (#3) | ok (#2) |
| iPod (iOS) | ipod | ok (#1) | n/a | ok (#3) | ok (#2) |
| Android | Android | n/a | ok (#2) | ok (#1) | n/a |
| Samsung Safe | SamsungSAFE | n/a | ok (#2) | ok (#1) | n/a |
| Windows Phone 8.0 | WP | n/a | n/a | n/a | n/a |
| Windows Phone 8.1 | WP | n/a | ok (#2) | ok (#1) | n/a |
Silverback: assigning users to imported mobile devices
When identifying the users of the imported mobile devices for Silverback, Matrix42 Enterprise Service Management uses the following data:
- Email. User's email address that is specified in the Silverback Console should correspond to the user's corporate or private email address in Matrix42 Enterprise Service Management.
The system tries to find a unique match in person records by following the defined sequence. After a respective key returns a unique match, a corresponding person is defined as a principal user of the given mobile device.
| Sequence | MDM Information | Data Definition | Attribute(s) |
|---|---|---|---|
| 1 | E-Mail Address | SPSUserClassBase | MailAddress or PrivateMailAddress |
| 2 | E-Mail Address | SPSAddressClassBase |
Silverback: assigning users to imported SIM cards
When identifying the users of the imported SIM cards for Silverback, Matrix42 Enterprise Service Management uses the following data:
- SIM Card. SIM card ID and phone number that are specified in the Silverback Console should correspond to the SIM card ID and phone number in Matrix42 Enterprise Service Management.
| Sequence | MDM Information | Data Definition | Attribute(s) |
|---|---|---|---|
| 1 | SIM Card Id | SPSAssetClassSIMCard | SimCardId |
| 2 | Phone Number | SPSAssetClassSIMCard | PhoneNumber |
Phone numbers are compared in a normalized way (digits only, no spaces, "00" equal to "+").
AirWatch: assigning users to imported mobile devices
When identifying the users of the imported mobile devices for AirWatch, Matrix42 Enterprise Service Management uses the following data:
- User Name. Username that is specified in the AirWatch Console should correspond to the username in Matrix42 Enterprise Service Management.
- First Name and Last Name. First name and last name that are specified in the AirWatch Console should correspond to the first name and last name in Matrix42 Enterprise Service Management.
- Email. User's email address that is specified in the AirWatch Console should correspond to the user's corporate or private email address in Matrix42 Enterprise Service Management.
- Phone Number. User's phone number that is specified in the AirWatch Console should correspond to the user's corporate or private phone number on the SIM card of the imported mobile device.
The system tries to find a unique match in person records by following the defined sequence. After a respective key returns a unique match, a corresponding person is defined as a principal user of the given mobile device.
The MWM AirWatch data provider supports only the basic authentication type, i.e. applies the user email, not the Active Directory account, as a username. Besides, the REST API of the MWM AirWatch data provider does NOT return the first and the last name of the user.
| Sequence | MDM Information | Data Definition | Attribute(s) |
|---|---|---|---|
| 1 | E-Mail Address | SPSUserClassBase | MailAddress or PrivateMailAddress |
| 2 | E-Mail Address | SPSAddressClassBase | |
| 3 | User Name | SPSAccountClassBase | AccountName |
| 4 | Telephone Number | SPSUserClassBase | BusinessPhone or PrivatePhone or MobilePhone |
| 5 | Telephone Number | SPSAddressClassBase | Phone |
Phone numbers are compared in a normalized way (digits only, no spaces, "00" equal to "+").