1. Home
  2. General
  3. How to pass device and user information using the wildcards supported by Hexnode MDM?

How to pass device and user information using the wildcards supported by Hexnode MDM?

Hexnode MDM supports wildcards containing information about each device and user to which you are assigning the management policies. You can use these variables for the commonly used device and user fields instead of entering them manually. This lets you create policies that can be pushed to a bulk of devices. When the policy/action is sent to a device/user, these variables will be automatically populated with the corresponding data retrieved from the details that have been provided during device enrollment.

Wildcards supported by Hexnode MDM

The below table lists the wild cards supported by Hexnode MDM:

Wildcard Substitution
%devicename% Name of the device as shown in the portal.
%model% Name of the device’s model or product.
%serialnumber% The serial number of the device.
%imei% The International Mobile Equipment Identity assigned to the device. This number uniquely identifies the mobile device.
%osname% Name of the operating system running on the device.
%osversion% The version number of the device’s OS.
%deviceid% A number assigned to each device in the order in which they had been enrolled.
%iccid% The ICCID from the device’s SIM card, if present.
%udid% The unique identifier assigned to the device by the manufacturer.
%phonenumber% The phone number associated with the mobile device.
%wifimacaddress% The Media Access Control address that uniquely identifies the network interface on the device.
%name% Name of the device user as displayed in the portal.
%email% The email address associated with a particular user.
%username% Name of the user or the email address associated with the user.
%domain% AD (Azure AD) domain name associated with the user.
%netbiosname% NetBIOS name of the Active Directory domain.
%ssid% Service Set Identifier (SSID) or simply the name for a WiFi network.
%assettag% Asset tag info. (provided by admin as a custom attribute in the device summary page) to identify the device.
%department% Department name as provided by the admin in the device summary page.
%devicenotes% Device notes provided by the admin in the device summary page.

Where are these wildcards used?

  • The following wildcards can be included in the messages broadcasted to iOS and Android devices.
    • %devicename%
    • %email%
    • %imei%
    • %deviceid%
    • %serialnumber%
    • %domain%
    • %name%
    • %netbiosname%
  • Wildcards like %username%, %email%, %domain% are used to fill in certain configuration fields in the WiFi, Email, Exchange ActiveSync, VPN Policies for iOS, Android and macOS devices.
  • %email% can be used to fill in the email address field in iOS Google Accounts policy.
  • CalDAV, CardDAV and LDAP policies for macOS and iOS and Calendar policy for iOS support %email% to fill in the User Name.
  • While adding web apps to be opened with Hexnode Browser Lite to the app inventory, the following device information can be passed:
    • %deviceid%
    • %serialnumber%
    • %devicename%
    • %imei%
    • %wifimacaddress%
    • %name%
    • %email%
    • %domain%
    • %netbiosname%
    • %udid%
    • %model%
    • %phonenumber%
    • %iccid%
    • %department%
    • %assettag%
    • %devicenotes%
  • Asset Tag Information for iOS lock screen message supports the following wildcards:
    • %devicename%
    • %imei%
    • %serialnumber%
    • %name%
    • %email%
    • %deviceid%
    • %domain%
    • %netbiosname%
    • %udid%
    • %model%
    • %phonenumber%
    • %iccid%
    • %wifimacaddress%
  •  
  •  
  •  
  •  
  •  

Was this article helpful?

Related Articles

Leave a Comment