1. Home
  2. Wildcards – Where and How they can be used in Hexnode MDM

Wildcards – Where and How they can be used in Hexnode MDM

Wildcard stands for ‘wild character’ which refers to a symbol used for replacing or representing one or more characters. Hexnode MDM supports wildcards containing information about each device and user to which you are assigning the management policies.

You can use these variables to replace individual device or user details. This enables you to create a single policy for the bulk rather than creating policies for each device/user separately. When the policy/action is sent to a device/user, these variables will be automatically replaced with the corresponding data retrieved from the details that have been provided during device enrollment. Here is how they are used:

Broadcast Messages

To display device/user details in a message via broadcast message, Hexnode MDM supports the use of wildcards. Including them within the message will fetch the details from the Hexnode servers. Supported on Android, iOS, Windows PC.

To send a broadcast message go to Manage –> Select the device/group –> Actions –> Select the broadcast message option from the drop down.

Wildcard Substitution
%devicename% Displays the device name as shown in the portal
%serialnumber% The serial number of the device.
%imei% The IMEI number of the device is fetched.
%deviceid% A number assigned to each device in the order in which they had been enrolled.
%phonenumber% The phone number associated with the mobile device.
%name% Name of the device user as displayed in the portal.
%email% The email address associated with a particular user.
%domain% AD (Azure AD) domain name associated with the user.
%netbiosname% NetBIOS name of the Active Directory domain.

Broadcast messages

A message like this with wildcards included will have the following results:

Broadcast messages

Setting a friendly name and renaming a device

When there is a bulk amount of devices, setting a friendly name/renaming the devices can be very hard. With the support of wildcards in Hexnode MDM you can rename the devices easily based on OS version/OS name/device id, etc and similar names can be differentiated with the ‘append number’ option to assign different numbers to the selected set of devices.

The wildcards can also be used to individually rename each device or set friendly names for them. To set the friendly name go to Manage –> Select the devices to be renamed –> from the Actions tab select the Set Friendly Name option.

  • Renaming a device is only supported on supervised iOS devices
  • Setting a friendly name is supported for all devices but the wildcards supported will be platform and device type specific.
Wildcard Substitution
%devicename% Displays the device name as shown in the portal
%serialnumber% The serial number of the device.
%imei% The IMEI number of the device is fetched.
%deviceid% A number assigned to each device in the order in which they had been enrolled.
%phonenumber% The phone number associated with the mobile device.
%name% Name of the device user as displayed in the portal.
%email% The email address associated with a particular user.

Remote ring message

Remote ring action is used to play a sound on the device even if the device volume is turned off. Hexnode MDM also supports an optional custom message along with the ring in Android devices. You can include wildcards within the message to display the device/user details on the device. To send a remote ring with message go to Manage –> Select the device/group –> Actions –> Select the Remote ring option from the drop down.

Wildcard Substitution
%serialnumber% The serial number of the device.
%imei% The IMEI number of the device is fetched.
%phonenumber% The phone number associated with the mobile device.
%name% Name of the device user as displayed in the portal.
%email% The email address associated with a particular user.

Network policy configuration set up

Wildcards can be used to set up Network configuration policies like Wi-Fi, VPN.

%name% Name of the device user as displayed in the portal.
%email% The email address associated with a particular user.
%ssid% Service Set Identifier (SSID) or simply the name for a WiFi network.

Work accounts configuration

Hexnode MDM supports wildcards for configuring work accounts in iOS and macOS such as Email, Google account, LDAP, CalDAV, CardDAV, Calendar, Exchange ActiveSync, etc.

%name% Name of the device user as displayed in the portal.
%email% The email address associated with a particular user.
%domain% AD (Azure AD) domain name associated with the user.
Note:

LDAP, CalDAV, CardDAV wildcards are available for both iOS and MacOS. Calendar and Google account policy configurations are only supported on iOS.

Lock Screen Message

Hexnode MDM lets you set up a lock screen message on supervised iOS 9.3+ devices. It can come in handy if the users misplace the devices.

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 IMEI number of the device is fetched.
%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.
%domain% AD (Azure AD) domain name associated with the user.
%netbiosname% NetBIOS name of the Active Directory domain.

Web apps in Kiosk Mode

For specific websites, certain device information can be passed along with the URL on to the target device with the help of wildcards. Such URLs would display the device information. Web apps opened with Hexnode Browser Lite (Hexnode’s default browser) allow the users to pass device information.

Go to Apps –> Add apps –> Web apps –> In the field to add the URL for the web app, enter the URL in the format “myURL/wildcard”. The following device information can be passed:

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 IMEI number of the device is fetched.
%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.
%domain% AD (Azure AD) domain name associated with the user.
%netbiosname% NetBIOS name of the Active Directory domain.
%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.
Note:

This feature is supported only on Android kiosk Mode.

  •  
  •  
  •  
  •  
  •  

Was this article helpful?

Leave a Comment