2.6.6 Linking with an MDM system
You can manage smart devices in JP1/IT Desktop Management 2 by linking with an MDM system and collecting information about the smart devices it manages. You can then manage the information in JP1/IT Desktop Management 2, and use the features of JP1/IT Desktop Management 2 to control smart devices.
To link with an MDM system in a multi-server configuration, you must link with an MDM system for each management server.
The following table shows the features made possible by linking with an MDM system:
Feature |
Description |
---|---|
Collecting information about smart devices |
You can collect information about the smart devices managed by an MDM system, and use the information to manage those devices in JP1/IT Desktop Management 2. By collecting information periodically from the MDM system, you can manage the device information, asset information, and security status of individual smart devices. |
Control smart devices |
JP1/IT Desktop Management 2 can lock, wipe, and reset passcodes on smart devices managed by an MDM system. |
Related Topics:
-
(1) Collecting information for smart devices managed by an MDM system
-
(2) Device information that can be acquired from MDM systems
- Organization of this subsection
(1) Collecting information for smart devices managed by an MDM system
You can collect information about smart devices managed by an MDM system, allowing you to use the features of JP1/IT Desktop Management 2 to manage the device information, asset information, and security status of smart devices. You can keep the information up-to-date by collecting the latest information.
- Tip
-
Like other devices, each smart device managed by JP1/IT Desktop Management 2 uses one product license.
The following figure shows how smart device information is collected from an MDM system.
You can use the following methods to collect information about smart devices managed by an MDM system:
- Immediate
-
JP1/IT Desktop Management 2 connects to the MDM system immediately and collects information about smart devices. Use this option when you first install JP1/IT Desktop Management 2 or when you want changes to the information in the MDM system to be immediately reflected in the JP1/IT Desktop Management 2 database.
- Scheduled
-
Smart device information is collected regularly according to the MDM linkage settings. Discovered devices are automatically made management targets. The schedule is determined by the values in Start At, Repeat Interval (daily, weekly, or monthly), and Repeat in the Settings module. By default, no schedule is set.
- Tip
-
When you delete a smart device from an MDM system, the corresponding information is not deleted from JP1/IT Desktop Management 2. When you remove a smart device from an MDM system, you can remove the device from JP1/IT Desktop Management 2 by deleting its device information.
(2) Device information that can be acquired from MDM systems
The following table lists the device information you can obtain from an MDM system.
System information
Device information item |
Whether device information can be acquired |
Corresponding item in the source MDM system |
Contents |
||
---|---|---|---|---|---|
In the case of JP1/ITDM2 - SDM#1 |
In the case of MobileIron |
||||
Device Type |
Si, SA, M |
-- |
-- |
Smart Device is set as the device type. |
|
Computer Details |
Computer Name (Description) |
Si, SA, M |
One if the following is displayed:#2
|
-- |
The smart device name#2, user name, contract phone number, and model name used to identify the smart device in the MDM system. |
Host Name |
Si, M |
||||
Model (Manufacturer) |
|
A combination of the following items is displayed.
|
-- |
The name of the manufacturer of the smart device, and the model name assigned by the manufacturer. |
|
Serial # |
Si, SA#3, M |
Hardware - Serial # |
SerialNumber |
The serial number of the smart device. |
|
Memory |
SA, M |
Hardware - RAM |
total_ram_size_bytes |
The total memory installed in the smart device. |
|
OS Details |
OS |
Si, SA, M |
A combination of the following items is displayed.
|
OS |
The name and version of the operating system. |
Network Details |
MAC Address |
Si, SA, M |
|
|
The MAC address of the device. |
Smart device information |
IMEI |
Si, SA, M |
Hardware - IMEI |
imei |
The IMEI that identifies the smart device. |
UDID |
Si, M |
Hardware - UDID |
udid |
The UDID assigned to Apple smart devices. |
|
IMSI |
Si, SA, M |
System Information - SIM Card |
|
The IMSI assigned to the SIM card of smart devices that the telecommunications company uses to identify the subscriber. |
|
ICCID |
Si, SA, M |
Hardware - ICCID |
-- |
The ICCID number assigned to the SIM card of the smart device. |
|
Model (Manufacturer) |
|
A combination of the following items is displayed.
|
-- |
The name of the manufacturer of the smart device, and the model name assigned by the manufacturer. |
|
Serial # |
SA#3, Si, M |
Hardware - Serial # |
SerialNumber |
The serial number of the smart device. |
|
Contract phone number |
Si, SA, M |
System Information - Phone Number |
Number |
The telephone number used by the smart device. |
|
|
Si, SA, M |
System Information - E-mail address |
-- |
The E-mail address used by the smart device. |
|
Carrier |
Si, SA, M |
System Information - SIM Card |
|
The communications provider of the smart device. |
|
Passcode or password setting |
Si, SA#3, M |
-- |
PasscodePresent |
Whether a passcode or password is set on the smart device. |
|
RAM (free) |
SA, M |
Hardware - RAM |
A combination of the following items is displayed.
|
|
|
Internal storage (free) |
Si, SA, M |
Hardware - Internal storage |
A combination of the following items is displayed.
|
|
|
External storage (free) |
SA, M |
Hardware - SD Card |
A combination of the following items is displayed.
|
|
|
Memory Details |
Capacity |
SA, M |
Hardware - RAM |
total_ram_size_bytes |
The amount of memory. |
Hard Disk Details |
Capacity |
Si, SA, M |
Hardware - Internal storage |
total_storage_size_bytes |
The space of entire hard disk. |
Software Inventory#4 |
Software Name |
Si, SA |
Software - Application name |
-- |
The software name of the installed software is collected. |
Version |
Si, SA |
Software - Version |
-- |
The version of the installed software |
|
Software Vendor |
Si, SA |
Software - Manufacturer |
-- |
The manufacturer of the installed software |
- Legend:
-
Si: Can be collected when the system links with JP1/IT Desktop Management 2 - Smart Device Manager, and the OS of the smart device is iOS.
SA: Can be collected when the system links with JP1/IT Desktop Management 2 - Smart Device Manager, and the OS of the smart device is Android.
M: Can be collected when the system links with MobileIron.
--: Regardless of whether the device information can be collected, there is no corresponding item in the source MDM system.
#1: JP1/ITDM2 - SDM: JP1/IT Desktop Management 2 - Smart Device Manager
#2: When JP1/IT Desktop Management 2 - Smart Device Manager is 11-00-03 or a later version, Managed Smart Device List-Name is displayed as the smart device name by default. By changing the SDM_Mapping_Name property in the configuration file (jdn_manager_config.conf), you can display a combination of System Information-User, System Information-Phone Number, and Hardware-Model, with the items separated by colons (:). For details, see the description of how to change the processing settings in the configuration file in the JP1/ITDM2 - Manager Configuration Guide.
#3: This information can be acquired when JP1/IT Desktop Management 2 - Smart Device Manager is version 11-00-04 or later.
#4 : To collect the software information, you need to create the definition file sdm_import.properties, and then store it in JP1/IT-Desktop-Management-2-Manager-installation-folder\mgr\conf. For details about the definition file sdm_import.properties, see (3) Settings for collecting software information from an MDM system. This software information is displayed in the Software List view and Installed Software tab of the Inventory module, or the Managed Software view of the Assets module. Note that, in some cases, thousands of information items are collected, which might adversely affect viewabilty.
You can also collect the information in the following table:
Device information item |
Description |
---|---|
Management Type |
MDM linkage management is set as the management type. |
Device Status |
Unknown is set if you collect smart device information from an MDM system, or re-register a wiped smart device. Warning is set if the smart device was successfully wiped. |
Management Status |
Agent not Installed is set. |
Last Alive Confirmation Date/Time |
The date and time when the smart device connected to the MDM system is set. |
See the following for details about device information:
(3) Settings for collecting software information from an MDM system
The following describes how to specify the definition file (sdm_import.properties) required to collect software information for smart devices.
To specify the definition file (sdm_import.properties):
-
Create a definition file (sdm_import.properties) that is coded in Key=Value format, and then store the file in the following location. Use UTF-8 character encoding to save the file.
JP1/IT-Desktop-Management-2-Manager-installation-folder\mgr\conf
The following table describes the information to be specified in the definition file (sdm_import.properties).
Key |
Value details |
Description |
---|---|---|
sdm.N.name |
The name of the MDM setting that defines information about linkage with the MDM system (JP1/ITDM2 - SD Manager) from which to collect information. |
Specify the same value specified in MDM settings name in the MDM Linkage Settings view that opens from General in the Settings module. For N, specify a natural number. To specify multiple linkage settings to collect information, you can specify multiple keys, such as 1 and 2. |
sdm.N.dbhost |
The IP address or host name used to connect to the database of the JP1/ITDM2 - SDM#1 server. |
Specify the IP address or host name#2 of a JP1/ITDM2 - SDM#1 server that can be connected within the same network segment as the computer on which JP1/IT Desktop Management 2 - Manager is installed. For N, specify a natural number. To specify multiple linkage settings to collect information, you can specify multiple keys, such as 1 and 2. |
sdm.N.dbport |
The port number used to connect to the database of the JP1/ITDM2 - SDM#1 server. |
Specify the port number#3 used to communicate with the database which is set up on the smart device manager of JP1/ITDM2 - SDM#1 server. For N, specify a natural number. To specify multiple linkage settings to collect information, you can specify multiple keys, such as 1 and 2. If omitted, the port number [26066] is used. |
#1: JP1/ITDM2 - SDM: JP1/IT Desktop Management 2 - Smart Device Manager
#2: When specifying a host name, note the following:
-
Use 1 to 32 characters.
-
Specify the host name that is displayed by executing the hostname command.
-
Host names are case sensitive.
-
You cannot specify an alias of the host name.
-
The specified host name must be registered in the hosts file or DNS and resolved in advance.
-
To specify the host name in FQDN format, the host name must be defined in FQDN format in advance.
#3: If the smart device manager server of JP1/ITDM2 - SDM#1 controls the port number by using Windows Firewall, specify firewall settings to enable the designated port (send/receive both directions).
Example of specifying the definition file (sdm_import.properties)
The following shows an example of specifying the definition file when MDM linkage products have been registered with MDM setting names ITDM2 SD Manager 01 and ITDM2 SD Manager 02 .
sdm.1.name=ITDM2 SD Manager 01 sdm.1.dbhost=192.168.50.100 sdm.1.dbport=26066 sdm.2.name=ITDM2 SD Manager 02 sdm.2.dbhost=SDM-Server02 sdm.2.dbport=36066
(4) Notes on MDM linkage
Note the following when linking with an MDM system:
-
You cannot use underscores (_) in the host name of an MDM server.
-
The device information that can be collected by the MDM linkage function depends on the OS of the smart device and the MDM system from which the information is being collected. JP1/IT Desktop Management 2 only displays the items it was able to collect.
-
If you swap the SIM card in a smart device, the IMEI stays the same but the contract phone number changes. As a result, a situation might arise in which the device information does not match the IMEI, causing the device to be recognized as a new smart device.