%wildcard%OR%wildcard% %wildcard%%wildcard% ✅ %wildcard%OR%wildcard%%wildcard%%wildcard% ❌ When you use the ‘OR’ operator to append a set of wildcards, separate the OR combination from other wildcards in the list using space. If the email is unavailable, it checks for the user’s alternate email and replaces the whole wildcard combination with it. For example: Entering %email%OR%alternateemail% in the Username field of the iOS CalDAV configuration fetches the user’s email from the enrollment information. This auto-populates the field with the first available wildcard data from among the combination. You can enter wildcard combinations separated by the keyword ‘OR’. Hexnode also supports the use of the logical OR operator in the fields that permit using two or more wildcards. For example, %email% will fetch the email address associated with the device’s user, easing the process of dynamically deploying multiple devices. This prompts the Hexnode UEM server to auto-populate by fetching the corresponding value associated with the user/device. In any field that supports wildcards, insert the wildcard (for example, %email%) instead of typing in the required value. Use this wildcard to insert a line break. Provide to use the enrollment information to populate the user principal name (UPN).Īn alternate email address associated with a particular user. Service Set Identifier (SSID) or simply the name for a Wi-Fi network.Īsset tag information (provided by admin as a custom attribute in the device summary page) to identify the device.ĭepartment name as provided by the admin on the device summary page.ĭevice notes provided by the admin on the device summary page. NetBIOS name of the Active Directory domain. Name of the user or the email address associated with the user.ĪD (Azure AD) domain name associated with the user. The email address associated with a particular user. Name of the device user as displayed in the portal. The Media Access Control address which uniquely identifies the network interface on the device. The phone number associated with the mobile device. The unique identifier which is assigned to the device by the manufacturer. The ICCID from the device’s SIM card, if present. Name of the operating system running on the device.Ī number that has been assigned to each device in the order in which they had been enrolled. This number uniquely identifies the mobile device. The International Mobile Equipment Identity is assigned to the device. Name of the device as shown in the portal. The below table lists the wild cards supported by Hexnode: 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. This lets you create policies that can be pushed to a bulk of devices. ![]() You can use these variables for the commonly used device and user fields instead of entering them manually. ![]() Hexnode supports wildcards containing information about each device and user to which you are assigning the management policies.
0 Comments
Leave a Reply. |