Integrating DME and MobiControl

Follow the basic steps below to integrate DME and MobiControl:

1. If you haven't installed DME, do so now. See DME Resource Center for information about this.
2. If you haven't installed SOTI MobiControl, do so now. See documentation from SOTI.

   The DME server must be able to reach the MobiControl server over HTTP. The certificate installed on the MobiControl server must be a CA-accredited certificate (for instance from Verisign). The default self-signed certificate will not be enough to verify the server in DME.

3. Enable External MDM in DME, and enter the path to SOTI MobiControl - see MDM.
4. Create Add Devices rules (to enroll devices) and Application Catalog rules (for DME installation) for Android and iOS - see DME installation through external MDM.
5. When users enroll their device with MobiControl, the device gets a unique ID.
6. When users install DME and attempt to connect to DME for the first time, the unique device ID from MobiControl is transferred to DME.
7. DME will verify that the device exists and is not locked in MobiControl, and then create (or update) it as a device in DME.

   Note that the MobiControl ID is used in addition to the device ID that DME generates for the device. This way, if you are upgrading from an existing DME installation (where you have not used MDM), the devices created through MobiControl will not duplicate existing devices.

From now on, DME will check the MobiControl server that a device is still under MobiControl control every time the device connects. If the device is somehow un-enrolled from MobiControl, the device will be denied access to DME as well.