On the MDM page, you can choose if you want to use DME for Mobile Device Management (MDM) or an external MDM provider.
DME has partnered with an external MDM/MAM provider, SOTI, to integrate their advanced MDM capabilities called MobiControl into DME. This is described in detail in Appendix B - see Appendix B: External MDM integration.
To go with standard DME MDM, leave the Enable external MDM switch Off. You then have these options for enrolling devices:
For a stronger and more coherent MDM integration, you can choose to integrate with an external MDM provider. If you do so, and the external MDM provider has been set up, you can, set the Enable external MDM switch to On.
Furthermore, all enrollment information for all enrolled Apple devices will be deleted, and any existing enrollment will no longer work. This is made clear by a dialog:
If you are sure that you know what you are doing, select Yes, stop using DME MDM, and click Delete. If not, click Cancel, and read Appendix B.
Block / unblock device function
Apple MDM and Apple profiles subtabs on device
Android security settings
Options to Allow Basic MDM devices and Lock jailbroken/rooted devices
The Applications panel section for blocking apps at device, group, and default level
The Apple MDM status is not shown in Server configuration > Monitor
The Apple MDM enrollment page is disabled
When external MDM is enabled, enter the following details:
This is the path to the server where the external MDM system is installed. The following is an example of a path:
https://mobi.company.com
This is the name of a user with administration permissions on the external MDM system.
This is the password for the user above.
With MobiControl 13 or later, it is recommended to use the REST API, as this is the only supported interface. For more information about the MobiControl REST API, please click on the link: External MDM REST API
below the Use REST API button.
The REST API uses OAuth2 authentication, and therefore requires a Client ID and a Client Secret created by the MobiControl server. The Client ID and Client Secret can be generated this way:
MCAdmin.exe APIClientAdd -n:DMEServer1
When an external MDM provider is selected, we recommend that devices are allowed to switch users. If this is not allowed, a device is currently prevented from passing to another user unless the device is completely removed from DME first. This option has been moved from Server configuration > Authentication to this window to remind you to consider whether it should be allowed or not.
If this switch is OFF, DME checks all devices that try to access DME to see if they are enrolled with the external MDM system, active in the system, and not blocked by the external MDM system. If a device fails either of these tests, it is denied access to DME.
If this switch is ON, you allow devices access to DME, even if they are not enrolled with the external MDM system. An un-enrolled device is only denied access if it has been blocked in DME. This is a more relaxed setting which allows you to include Bring Your Own Device (BYOD) in your device mix, even when integrating with an external MDM system.
Below these options is a link to the administration interface of the external MDM provider, based on what you entered in the field Path to external MDM.
Click Save to complete the switch to or from external MDM control. For more information, see Appendix B: External MDM integration.