By entering a configuration URI, you enable the following workflow for the user who is installing DME:
This will send the user's configuration URI to the MobiControl server, and configure the DME client for first use by setting the DME server path, port, HTTPS setting, and user name.
The configuration URI is created in an Application Catalog rule. To work correctly, it must have a form similar to the example below:
dmeexcitor://dme.company.com:5011/?secure=1&id=%DEVICEIDENTIFIER%&user=%ENROLLEDUSER_USERNAME%
The example is split into parts below, and each part is explained.
Part |
Explanation |
|
This is the literal protocol identifier. This makes the DME client pick up the configuration URI. |
|
This is the server path of your DME installation, including port number. |
|
|
|
This is the number by which the device is identified in MobiControl. Use the variable
|
|
This is the user name with which the device was enrolled in MobiControl in the first place through the Add Devices rule. Use the variable
Note, however, that for MobiControl to know the device's user name, the device must have been enrolled using the option Utilize User Directory credentials to verify device enrollment in the Authentication part of the Add Devices rule. If the device have been enrolled using the email address instead, use the variable
|
Caution: Please note that if any MobiControl variable cannot be resolved, then the entire URI operation will fail. For instance, if the %PHONENUMBER%
cannot be found in MobiControl, the configuration operation will fail. Due to the fact that some phone vendors do not permit a third party to read the phone number from the device, the %PHONENUMBER%
variable is especially uncertain, and should probably not be used in the configuration URI at all.
When a device is configured using this rule, all information required to log in to DME is supplied (apart from the user's password).
Two more variables from MobiControl are available in the configuration URI:
%ENROLLEDUSER_DOMAIN%
%PHONENUMBER%