NomidNomid MDM allows administrators to use dynamic variables in Managed Configurations of Android applications. These variables are automatically replaced with the actual device value when the policy is applied.
Purpose
- Automate application provisioning.
- Avoid manual entry of unique values for each device.
- Ensure configuration consistency even in scenarios of app reinstallation or policy reset.
Supported Variables
| Variable | Description | Example substitution |
|---|---|---|
%imei% |
Device IMEI | 357842105887001 |
%serial_number% |
Device serial number | R9ZT12345AB |
%serialnumber% |
Alias for %serial_number% (same behavior) |
R9ZT12345AB |
IMEI and serial number are persistent asset identifiers. Use these variables only when the application truly needs to identify the device, and confirm who can access the value in the app backend, how long it will be retained, and which channel is allowed for support.
How to use
1. Access Managed Configuration
- In the Nomid MDM portal, open the policy or configuration profile.
- Select the desired app (e.g., HR Portal – com.company.hrportal).
2. Identify the configuration field
- Each compatible app exposes specific keys (e.g.,
username,device_id,user_identifier). - These fields vary by app but all accept Nomid MDM variables.
3. Insert the variable
- Instead of entering a fixed value, insert the dynamic variable.
Example 1 – Automatic login using IMEI
username = %imei%
→ The app will receive: 357842105887001
Example 2 – Unique identifier using serial number
user_identifier = %serial_number%
→ The app will receive: R9ZT12345AB
Example 3 – Building strings with variables
account = user_%serialnumber%@company.com
→ The app will receive: user_R9ZT12345AB@company.com
4. Save the configuration
- Nomid MDM backend interprets and replaces the placeholders.
- The app on the device receives the resolved value.
Before publishing to production, validate the effect of each field in a pilot group: whether the app accepts the resolved value, whether there is a fallback when IMEI/serial is unavailable, whether the format requires a prefix/suffix, and whether the value is not being used as a password or secret.
Automatic Reapplication
- Nomid MDM has an optional worker that can periodically reapply variables.
- This is useful in scenarios such as:
- App reinstallation.
- Cache/data reset.
- Policy changes.
⚠️ The minimum reapplication interval is 15 minutes. If disabled, substitution occurs only when the user interacts with the Nomid launcher.
Limitations and Considerations
-
Current behavior: Nomid MDM does not monitor new app installations on the device. This means that if an app is installed after the policy has been applied, it will not immediately receive dynamic variables.
-
How to resolve:
- Force a manual synchronization of the device using the device's home button.
- Or wait for the reapplication worker (if enabled).
-
Variables must be written exactly as supported (
%imei%,%serial_number%,%serialnumber%). -
If the app field does not support Managed Configurations, the variables will have no effect.
-
Always test in a pilot device group before rolling out to production.
-
Do not use IMEI or serial as a password, secret token, or sole proof of identity. These values identify the device, but they may appear in inventory, logs, or support screens.