How to setup Zebra device management using Hexnode MDM

TL;DR

Zebra device management combines standard Android controls with Zebra-specific capabilities to centrally configure, secure, and maintain enterprise rugged devices.

Hexnode supports enrollment, app management, restrictions, monitoring, kiosk configurations, networking, and other Android management capabilities for Zebra devices.
Zebra OEMConfig powered by MX extends management with manufacturer-specific controls for hardware, connectivity, firmware, and specialized device functions.
Using native Android policies alongside OEMConfig helps IT manage Zebra fleets while addressing deeper rugged-device requirements.

Table of Contents

Why Zebra device management requires more than standard Android management
How to setup Zebra device management using Hexnode’s native device management features?
Enrollment
Management
Restrictions
Policies
Other key features
How Zebra MX and OEMConfig extend Android Enterprise management
How to setup Zebra device management using Hexnode’s OEMConfig capabilities?
Controlling Zebra OS and firmware updates
Zebra’s OEMConfig capabilities with Hexnode MDM
FAQs

Zebra Technologies is an American Public company from Illinois, USA that manufactures enterprise solutions.

Zebra technologies focuses on building enterprise-level data capture and automatic identification solutions that provide businesses with operational visibility.

Hexnode’s partnership with Zebra Mobile enables our users to leverage Zebra’s API for device management via OEMConfig which extends the management capabilities beyond our native features.

Note:

Zebra’s OEMConfig app is called the Zebra OEMConfig powered by MX.

The main list of Zebra devices include:

Zebra TC21 and TC26 Touch Computers
Zebra EC30 Enterprise Companion
Zebra MC9300 Mobile Computer
Zebra TC72 and TC77 Touch Computers
Zebra TC52 and TC57 Series Touch Computers
Zebra TC52-HC Touch Computer
Zebra TC25 Rugged Smartphone
Zebra TC20 Mobile Computer
Zebra M60 Mobile Computer
Zebra MC33xx Series Mobile Computer
Zebra MC3200 Mobile Computer
Zebra TC8300 Touch Computer
Zebra TC8000 Touch Mobile Computer
Zebra MC9200 Mobile Computer
Zebra Workabout Pro 4 Mobile Computer
Zebra Omnii XT15 Mobile Computer Series
Zebra MC55X Mobile Computer Series
Zebra PS20 Personal Shopper
Zebra MC18 Personal Shopper

Besides these, they also specialize in enterprise scanners, printers and tablets.

Why Zebra device management requires more than standard Android management

Zebra devices often operate in warehouses, retail environments, manufacturing facilities and field operations where downtime can directly disrupt business-critical workflows. Managing these endpoints therefore involves more than applying standard Android policies.

IT teams need centralized control over device configurations, enterprise applications, connectivity and security while keeping large fleets operational across distributed locations. Rugged deployments can also involve specialized hardware such as barcode scanners, programmable buttons and other peripherals that standard Android management frameworks may not expose. Competitors consistently emphasize lifecycle management, uptime and rugged-specific controls as core requirements for Zebra fleets.

Zebra addresses these requirements through technologies such as Mobility Extensions (MX), which expose additional controls for Zebra hardware and software. When combined with Android Enterprise and a UEM solution, these capabilities allow organizations to apply standard Android management where possible and use Zebra-specific configurations when workflows demand deeper hardware control.

How to setup Zebra device management using Hexnode’s native device management features?

Hexnode’s Android device management capabilities can be leveraged to manage Zebra devices directly.

Enrollment

Hexnode MDM provides a wide variety of enrollment methods for Android devices, you are free to choose the ones that are convenient for your business model.

No authentication enrollment: It is the fastest enrollment method available. It only requires the server name. No authentication and no enrollment credentials are needed. All devices enrolled this way are assigned to a default user.

Email/SMS enrollment: Here the enrollment credentials are sent to the users via email or SMS. These credentials have to be entered to complete the enrollment process.

Self-Enrollment: This method allows the users to enroll their devices via Azure Active Directory, Active Directory, or Google user credentials. For other users, the admin may create a default user and a dedicated password manually or assign a common password or individual passwords for the users and sends it to them as a bulk mail. The enrollment process is pretty much the same.

QR code enrollment: In certain scenarios, it is difficult to enroll devices with credentials like username, password and portal name. Hexnode MDM lets you enroll devices easily by scanning a QR code.

ROM enrollment: If your enterprise has a collaboration with Zebra you can flash a custom ROM to the Android Device with Hexnode MDM as a system app.

Android Enterprise Enrollment: Previously known as Android for work, it is currently the main enrollment method for android devices. Depending on the enrollment mode, Android Enterprise can fully manage the device or create a separate work profile. The separation of corporate and personal data is necessary if the devices are BYOD (Bring your own device) or COPE (Corporate owned personally enabled). The Hexnode for work app is used for Android enterprise enrollment. AFW# and ADB methods are also used for Android Enterprise Enrollment.

Zero-touch enrollment: This is ideal for bulk deployment of devices. The devices need to be purchased from a Zebra zero-touch reseller partner. It is ideal for corporate-owned devices as it is a one-time configuration process. Hence, the devices come pre-configured out of the box. This also eliminates the need for user intervention in setting up the devices.

Management

Hexnode provides the A – Z in device management. The main management features for Zebra devices include:

Device info and monitoring: Android Device monitoring features include device summary which provides a summary of the hardware info like model, type, OS version, root info, battery level, memory level. It also provides enrollment details (last checked-in, last scan, device id, enrollment date, and status).

Location information is also available with map support to pinpoint the exact location the device was last active at. Compliance to policies and restrictions, the number of apps currently on the device, activity status, the number of policies currently associated, kiosk status, and last checked-in time can also be viewed from the Manage section.

The device info section includes the device model name, manufacturer (Zebra), Serial no, UID, etc. Network Info section includes the phone number of the SIM cards on the device, IMEI numbers of the device, roaming status, carrier details, etc.

Application, Policies, Security sections under manage has the full list of associated policies and applications.

Actions: A large list of actions are available for Zebra devices. Scan option is used for scanning the devices to refresh the data and listing the current device status, it can also be used to scan the device location. Lock, wipe, remote ring, enabling lost mode actions are useful in cases of emergency (lost or stolen devices with valuable corporate data).

Changing the device owner, installing and uninstalling applications, associating configured policies, OS updates, changing the friendly name for the device, changing ringtone, importing contacts to device can all be done remotely via the actions tab in device management.

Enabling and disabling kiosk mode can be achieved at the click of a button. Broadcasting notifications and messages to the selected devices are very popular among our users.

The action tab also allows the exporting of device details as a pdf file. When you are all done with a device you can disenroll it from the Henoxde MDM portal using the Disenroll device action.

Action History section shows the activity log for the device along with the status of each action and messages related to it.

Remote control and view: The manage tab for Android devices provides the remote device view option. This is achieved via the remote view app which can be remotely installed on any device. It lets you view the user’s device in real-time. This nifty feature lets you monitor the users that require supervision.

The remote control feature is available for supported Android 5.1+ devices, including Android Enterprise devices enrolled in Device Owner mode. The remote control allows admins to monitor and take control of the device from their PC. It can come in handy when you need to take control of the devices to diagnose and fix problems reported by the users in real-time.

Data Management: The data management section under Manage shows the data usage by the device as a whole and for each app individually.

Total data usage, Mobile data usage, WIFI data usage as a whole, and for each application are listed under this section. The data usage details can be exported as a CSV or PDF from here. The section also has filters to view the usage by dates and periods. A list of apps with blocked data access are also listed here.

Users, devices, and groups: All enrolled devices can be divided into groups for easier monitoring. Similarly, users can also be grouped.

Grouping of devices and users not only allows easier monitoring, it also helps in managing them together via actions and policies. Grouping is highly recommended in cases where the device count is high.

Hexnode MDM also supports dynamic grouping. Dynamic groups keep changing automatically based on certain specified conditions. In dynamic grouping, devices move in and out of the group during the periodic group sync, whereas custom groups maintain devices as a fixed list. The sufficiency of minimal manual effort makes dynamic grouping more desirable than manual grouping.

Restrictions

Device Functionality: Enable or disable device functionality features like camera, USB file transfer, safe mode, lock screen orientation and lock screen timeout.

Network Settings: Provision to forcefully turn the Wi-Fi on and off besides disabling or enabling the feature can be useful to certain enterprise needs.

Enabling or disabling Bluetooth, tethering, a portable wi-fi hotspot, and data roaming can be done.

Synchronization settings: Backing up or restoring data from google drive can be disabled on Android 8.0+ devices in device owner mode.

Advanced device functionality restrictions: Disabling of the device microphone, screen capture, making a call, volume adjustment, and the copying of content between normal and work profiles are available for Zebra devices.

Advanced Display settings: Hiding the device status bar and displaying dialogs/windows are available under this section.

Advanced Connectivity settings: Bluetooth data transfer, android beam, configuring Bluetooth, configuring cell broadcast, configuring cellular network, configuring Wi-Fi, configuring hotspot and tethering, and the ability to reset network settings can be disabled from the Hexnode MDM portal.

Advanced account and application settings: Sending SMS, configuring user credentials, and modifying the user’s Google accounts (add, delete, switch) can be done here.

Installing and uninstalling apps, modifying application settings, app verification before installations, allowing the installation of applications from unknown sources, parent profile app linking, and app runtime permissions can all be enabled or disabled to suit your enterprise’s needs.

Other advanced settings: Factory reset protection can be disabled or bypassed on devices in Android Enterprise device owner mode.

Enabling location sharing, USB debugging, factory reset, reading external connected media, setting up time zone, updating date and time automatically, and configuring VPN can also be done via the Hexnode MDM portal.

All advanced device settings are available only for Android Enterprise devices.

Policies

Password: Secure your Zebra devices with Hexnode’s password policy. Password complexity, password age, password history can be configured for the devices. Added security via auto-lock and device wipe after a set number of failed attempts can also be configured. This method is used to lock the entire device in normal mode. In Device Owner mode, the password policy applies to the device rather than a separate work profile.

For devices running Android 7.0+ enrolled in profile owner mode the work profile alone can be locked with the password policy.

App Management: Mandatory app policy allows you to install applications on the device. In android enterprise mode (as managed google apps), rooted devices, and devices with Hexnode MDM app as a system app, apps can be installed on the device silently. In all other cases, user intervention is required to install applications.

Blocklisting apps on Android Enterprise devices hides the blocklisted apps and prevents users from installing or updating them. In the Profile Owner mode, blacklisted apps will be hidden from the work container. Whitelisting of apps causes all other apps(not whitelisted) to be considered as blacklisted.

App Cataloging is used to create a customized app store on the end user’s device. App configuration and app permissions can be used to manage and configure the applications before pushing them to the devices (Only in Android Enterprise).

Networks: Wi-Fi networks can be pre-configured and associated to the devices so that they can connect automatically to the network without prompting the users to enter passwords. This saves the organization the hassle of sharing the credentials with each employee.

Security: Certificates can be installed on the Zebra devices remotely to ensure higher security. Similarly, OS updates can also be scheduled on devices enrolled in Device Owner mode.

Configurations: Wallpaper for the device home screen is customizable on all devices with Android 4.4 and above from the Hexnode MDM portal.

Mobile Data Management and File Management: The Mobile data management feature on Android 6.0+ devices allow admins to monitor how Wi-Fi and mobile data connection are used. Usage limits can be set up, network connectivity can also be restricted if limits are reached (monthly, daily, etc. on the device as a whole or on apps individually). This can be useful in tracking data hogging applications.

File Management can be used to upload files (videos, audios, images, documents) to a designated space within an enrolled device.

Kiosk Features: In most enterprises, the devices are used to access only a limited set of applications. Single app and multi-app kiosk modes by Hexnode MDM can be used for locking down your devices to only the required applications.

Hexnode also provides the option to run apps in the background as certain apps require access to other apps to function properly. The devices can be turned into Digital signages for advertisements and can be set up as a self-service kiosk. A custom kiosk launcher, kiosk screen savers, website kiosks are just the tip of the iceberg.

Kiosks can also be highly customized by restricting device actions and buttons. Kiosk exit settings and website kiosk settings should be configured as per the requirement to adapt the kiosk to the enterprise’s needs. Hexnode browser lite and Hexnode kiosk browser features can also be modified to control how the website kiosk works.

Zebra devices are commonly used as rugged devices, hence Hexnode’s extensive kiosk capabilities will complement it quite nicely.

Geofencing and Location Tracking: Location tracking is useful for turning automatic location tracking on and off and setting the location tracking interval. Users will not be able to change these settings once the configuration policy is associated.

Geofencing is used to create a virtual fence on the map when devices exit the fence they will be marked as non-compliant and the admins will be notified. One of the many high-security Hexnode features.

Android Enterprise Compliance: This policy can be used to deactivate the Android Enterprise container on non-compliance. The deactivation time can be set for securing corporate data.

Other key features

Apps: The apps tab has everything related to applications. You can add enterprise apps and push them to the devices directly or via policies. App catalogs, app grouping, store layouts can be configured here.

You can turn websites into web apps and push them to the devices. Customizing apps, creating file shortcuts for video and pdf files, app management, app configurations, app permissions, and OEMConfig capabilities can be created and modified here.

Admin Settings and Reports: In addition to all the specific features Hexnode’s common alert and management features are also available for Zebra devices.

Inactivity settings to mark devices as inactive after a specified period. Scheduling device scans at regular intervals. Added compliance setting like device encryption, device inactivity, MDM app removal from the device, battery level alerts and notifications, etc.

Action and compliance notifications can be enabled/disabled to notify the admins or users as the case may be. A detailed report section shows a list of device, user, compliance, location, data management, application, and audit reports. These reports can be filtered and viewed. They can also be scheduled and exported as a CSV or PDF file.

How to setup zebra device management using Hexnode MDM

How Zebra MX and OEMConfig extend Android Enterprise management

Android Enterprise provides the foundation for managing corporate Android devices, but Zebra endpoints can expose additional hardware-specific controls through Zebra Mobility Extensions (MX).

MX acts as Zebra’s management framework for configuring device settings and behavior that extend beyond standard Android capabilities. Zebra makes many of these controls available through its OEMConfig application, allowing compatible UEM platforms to deliver manufacturer-specific configurations through managed app configurations.

With Hexnode, the Zebra OEMConfig powered by MX application can provide controls for functions such as scanner configuration, programmable hardware buttons, Bluetooth pairing and device-specific firmware behavior. Hexnode deploys these settings as managed app configurations, allowing administrators to manage supported Zebra capabilities from the UEM console without relying solely on standard Android Enterprise policies.

This makes OEMConfig particularly useful when a deployment requires deeper control over rugged hardware while retaining Android Enterprise as the underlying management framework.

How to setup Zebra device management using Hexnode’s OEMConfig capabilities?

To access the OEMConfig set of features for Zebra devices

Step 1: Go to the Apps tab on your Hexnode portal

Step 2: Select Add apps > Managed Google Apps

Step 3: Search for Zebra OEMConfig application and Approve it

Step 4: Go to Policies > New Policy > Android > App Management > App Configurations > Configure > +Add new configuration > select the Zebra OEMConfig powered by MX app

Selecting the application will show you the list of all available device features that can be managed on Zebra devices using OEMConfig.

Select the management options for the required features and save the policy. Assign this policy to the required Zebra devices for management.

OEMConfig – Breaking the boundaries of Android device management

OEMConfig is a provision by the device manufacturers that guarantees the latest device management capabilities before anyone else for Android.

Controlling Zebra OS and firmware updates

OS and firmware maintenance becomes especially important when Zebra devices support frontline operations. Updating every endpoint immediately can introduce operational risk, while delaying security and stability updates for too long can leave the fleet exposed.

Zebra LifeGuard provides Android security updates and maintenance releases for supported enterprise devices, and competing Zebra management solutions prominently address firmware and LifeGuard update control as part of device lifecycle management.

Hexnode can use Zebra OEMConfig controls to govern LifeGuard OTA update windows on supported devices. Administrators can also restrict access to the device’s Firmware Update button, helping prevent users from initiating unauthorized firmware changes.

These controls allow IT teams to coordinate updates around operational requirements instead of leaving firmware changes entirely to device users. For large Zebra fleets, a controlled update strategy can reduce unnecessary disruption while helping endpoints remain on approved software versions.

Zebra’s OEMConfig capabilities with Hexnode MDM

Connectivity Settings

Error Mode: Specifies how to handle errors that occurs during this OemConfig Step

State: Specifies whether Analytics data and events are allowed to be collected from the device. Supported from: MX 4.3

User Control of State: Set whether the Device User will be allowed to control whether Analytics data and events are allowed to be collected from the device. Supported from: MX 7.2

App Feature State: Specifies whether the specified Application Feature for a particular application should be on or off. Supported on Android: Pie and Oreo. Supported from: MX 9.3

App Feature Name: Specifies the name of the Application Feature that will be turned On or Off. Supported on Android: Pie and Oreo. Supported from: MX 9.3

App Feature Package Name: Specifies the package name of the application for which the Application Feature will be turned On or Off. Supported on Android: Pie and Oreo. Supported from: MX 9.3

State: Specifies whether the AppGallery Client will be enabled or not. Supported from: MX 6.0

Push Notifications: Specifies whether the AppGallery push notifications will be enabled or not. Supported from: MX 6.0

Credential Type: Specifies whether the AppGallery Client will use default or custom credentials to authenticate to the AppGallery Server. Supported from: MX 6.0

Custom User Name: Specifies the Custom Credentials User Name to be used by the AppGallery Client to authenticate to the AppGallery Server. Supported from: MX 6.0

Custom Password: Specifies the Custom Credentials Password to be used by the AppGallery Client to authenticate to the AppGallery Server. Supported from: MX 6.0

Custom Organization Key: Specifies the Custom Credentials Organization Key to be used by the AppGallery Client to authenticate to the AppGallery Server. Supported from: MX 6.0

Play AC Detect Sound: Specifies whether a notification chime will play when AC power is connected. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Replication Action: Set whether headset audio will be replicated to the built-in speaker. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.2

Mute/Vibrate: Specify whether Mute and/or Vibrate should be applied to the device. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

State: Specifies whether automatic triggering (e.g. of an input device such as a barcode scanner) should be performed based on device proximity. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Range: Specifies whether automatic triggering (e.g. of an input device such as a barcode scanner) should be performed based on device proximity. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Action: Specifies an Action to be performed on a built-in system application. Supported from: MX 4.2

Allow System Package Name: Specifies the package name of a built-in system application to which the Allow Action should be applied. Supported from: MX 4.2

Disallow System Package Name: Specifies the package name of a built-in system application to which the Disallow Action should be applied. Supported from: MX 4.2

Discoverability: Specifies whether the device should be discoverable via Bluetooth by entities outside the device. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

New Pairings: Specifies whether the Device User is allowed to create new Bluetooth pairings. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.1

Turn On/Off Silent Pairing: Sets whether the Device User is allowed to silently perform Bluetooth pairings. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Action: Specifies a Bluetooth Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Add Rule Name: Specifies the name to be assigned to a new Rule that is Added. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Add Rule MAC Address: Enter the Bluetooth MAC Address XX:XX:XX:XX:XX:XX along with CoD/UAP/PIN for adding a new rule. Supported on Android: Pie. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Add Rule Device Class: Specifies the device class for a Rule to be Added. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Add Rule Device Upper Address Part: Specifies the device upper address part for a Rule to be Added. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Add Rule Pairing PIN Code: Enter the Pairing PIN Code if remote device is prior to Bluetooth 2.1. Supported on Android: Pie. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Remove Rule Name: Specifies the name to be assigned to a new Rule that is Removed. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Remove Rule MAC Address: Enter the Bluetooth MAC Address XX:XX:XX:XX:XX:XX along with CoD/UAP/PIN for removing a new rule. Supported on Android: Pie. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Remove Rule Device Class: Specifies the device class for a Rule to be Removed. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Remove Rule Device Upper Address Part: Specifies the device upper address part for a Rule to be Removed. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Remove Rule Pairing PIN Code: Enter the Pairing PIN Code if remote device is prior to BT 2.1. Supported on Android: Pie. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Extensions State: Specifies whether enhanced bug reporting (vs. standard) will be used. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Intent Enable: Specifies whether bug reports can be initiated by intent. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Screenshot Enable: Specifies whether screenshots can be attached to bug reports. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Show In Power Key Menu: Specifies whether an option to initiate bug reporting is shown in the Power Key Menu. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

ANR Error Action: Sets the action to take when an Application Not Responding (ANR) error is detected. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Unexpected Error Action: Sets the action to take when an Unexpected Application error (other than ANR) is detected. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

State: Specifies whether bug reports should be automatically sent to the Zebra cloud. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Time to Live: Sets the Time To Live (time before expiration) of enabling Sending of Bug Reports to the Cloud. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

State: Specifies whether bug reports should be stored in the device. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

File Path: Specifies where bug reports should be stored in the device (if enabled). Default = /storage/sdcard0/BugReports/. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Time to Live: Sets the Time To Live (time before expiration) of enabling Storage of Bug Reports. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

State: Specifies whether bug reports should be sent via email. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

SMTP Host: Specifies the SMTP server address for delivering bug reports via email. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

SMTP Port: Specifies the SMTP server port for delivering bug reports via email. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Sender ID: Specifies the sender identification for delivering bug reports via email. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Sender Password: Specifies the sender password for delivering bug reports via email. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Send To Address: Specifies the send to address for delivering bug reports via email. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Time to Live: Sets the Time To Live (time before expiration) of enabling Email of Bug Reports. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Device Settings

Dialog Elements: Specifies one or more dialog elements that should be displayed in the enhanced bug reporting dialog. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Type: Specifies the type of a single dialog element. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Error Name Text Box Text: Specifies the text to display in a Dialog Item of Type Error Name Text Box. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Label Text: Specifies the text to display in a Dialog Item of Type Label. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Text Box Text: Specifies the text to display in a Dialog Item of Type Text Box. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Dialog Time Out: Specifies the amount of inactivity (in ms) after which the bug reporting dialog will automatically be dismissed. Default value = 60000. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Use Of Back Camera: Specifies whether the back camera can be used to take pictures. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Use Of Front Camera: Specifies whether the front camera can be used to take pictures. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Use Of Imager: Specifies whether the imager can be used to take pictures. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.1

Time Mode: Specifies the time mode to manual or auto. Supported from: MX 4.2

Manual Date: Specifies the date to a specified value when in manual time mode. Supported from: MX 4.1

Manual Time: Specifies the time to a specified value when in manual time mode. Supported from: MX 4.1

Auto NTP Server Address: Specifies the NTP Server Address when in auto time mode. Supported from: MX 4.2

Auto NTP Sync Interval: Specifies the NTP Sync Interval when in auto time mode. Supported from: MX 4.2

Time Zone Mode: Specifies whether the time zone mode should be manual or auto. Supported from: MX 6.0

Zone: Specifies the time zone to a specified value when in manual time zone mode. Supported from: MX 4.1

Time Format: Specifies the time format to 12 or 24 hour (military) mode. Supported from: MX 6.0

Request Boot File Name (Option 67): Specifies whether the Boot File Name should be requested by the DHCP Server by the DHCP Client. Supported from: MX 4.4

Request Broadcast Address (Option 28): Specifies whether the Broadcast Address should be requested by the DHCP Server by the DHCP Client. Supported from: MX 4.4

Request NTP Server (Option 42): Specifies whether the NTP Server should be requested by the DHCP Server by the DHCP Client. Supported from: MX 4.4

Request TFTP Server Address (Option 66): Specifies whether the TFTP Server Address should be requested by the DHCP Server by the DHCP Client. Supported from: MX 4.4

Request Vendor Encapsulated Options (Option 43): Specifies whether Vendor Encapsulated Option should be requested by the DHCP Server by the DHCP Client. Supported from: MX 4.5

Request Domain Search List (Option 119): Specifies whether the Domain Search List should be requested by the DHCP Server by the DHCP Client. Supported from: MX 4.4

Request TFTP Server Names (Option 150): Specifies whether the TFTP Server Name(s) should be requested by the DHCP Server by the DHCP Client. Supported from: MX 4.4

Request Vendor Specific Option#1 (Option 186): Specifies whether Vendor Specific Option 186 should be requested by the DHCP Server by the DHCP Client. Supported from: MX 4.5

Request Vendor Specific Option#2 (Option 188): Specifies whether Vendor Specific Option 188 should be requested by the DHCP Server by the DHCP Client. Supported from: MX 4.5

Request Vendor Specific Option#3 (Option 230): Specifies whether Vendor Specific Option 230 should be requested by the DHCP Server by the DHCP Client. Supported from: MX 6.3

Send Client Identifier State (Option 61): Specifies whether a Client Identifier value should be sent to the DHCP Server by the DHCP Client. Supported from: MX 6.3

Send Client Identifier Value (Option 61): Specify a Client Identifier value to be sent by the DHCP Server by the DHCP Client. Supported from: MX 6.3

Send Host Name State (Option 12): Specifies whether a Host Name value should be sent to the DHCP Server by the DHCP Client. Supported from: MX 4.4

Send Host Name Value (Option 12): Specifies a Host Name value to be sent by the DHCP Server by the DHCP Client when the Host Name Send State is On. Supported from: MX 4.4

Send User Class State (Option 77): Specifies whether a User Class value should be sent to the DHCP Server by the DHCP Client. Supported from: MX 4.4

Send User Class Value (Option 77): Specifies whether a User Class value should be sent to the DHCP Server by the DHCP Client. Supported from: MX 4.4

Send Vendor Class State (Option 60): Specifies whether a Vendor Class value should be sent to the DHCP Server by the DHCP Client. Supported from: MX 4.5

Send Vendor Class Value (Option 60): Specifies a Vendor Class Value that should be sent to the DHCP Server by the DHCP Client. Supported from: MX 4.5

Send FQDN State (Option 81): Specify whether a Fully Qualified Domain Name value should be sent to the DHCP Server by the DHCP Client. Supported from: MX 6.3

Send FQDN Value (Option 81): Specify a Fully Qualified Domain Name Value that should be sent to the DHCP Server by the DHCP Client. Supported from: MX 6.3

Send FQDN Flag (Option 81): Specify a Fully Qualified Domain Name flag that should be sent to the DHCP Server by the DHCP Client. Supported from: MX 6.3

Request Custom Option Number: Specifies a Custom Option Number that should be requested by the DHCP Server by the DHCP Client. Supported from: MX 8.1

Request Custom Option State: Specifies whether a Custom Option should be requested by the DHCP Server by the DHCP Client. Supported from: MX 8.1

Send Custom Option Number: Specifies a custom option number to be sent to the DHCP Server by the DHCP Client. Supported from: MX 8.1

Send Custom Option State: Specifies whether a custom option should be sent to the DHCP Server by the DHCP Client. Supported from: MX 8.1

Send Custom Option Value: Specifies a custom option value or no value to be sent to the DHCP Server by the DHCP Client. Supported from: MX 8.1

Programmatic Import: Specifies whether applications will be allowed to programmatically import DataWedge Configuration Files using the DataWedge Intent API. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Manual Configuration: Specifies whether Device Users will be allowed to manually alter the configuration of DataWedge from the DataWedge configuration UI. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Automatic Database Import: Specifies whether DataWedge Database Files deployed to the DataWedge autoimport folder on the device will automatically trigger importing of the file. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Database File: Specifies the device path and file name of a valid full (datawedge.db) or partial (dwprofile_profilename.db) Datawedge Database file to be imported to replace or merge with the current configuration of DataWedge. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Device Administration – Secure Start-up Selection by Device User: Select whether Device User Selection of Secure Start-up will be allowed when changing pin/password/pattern. Not supported on Device(s): TC20 and TC25. Supported from: MX 10.0

Unreserve User ID Package Name: Specifies the package name of the application whose user ID can be released. Supported from: MX 9.2

Reserve User ID Package Signature: Specifies the Base 64 encoded value of the content of the DER format certificate used to sign the application to which a user ID is reserved. Supported from: MX 9.2

Reserve User ID Package Name: Specifies the package name of the application to which a user ID is reserved. Supported from: MX 9.2

Submit XML: Specifies the XML to be submitted to MX as part of a SubmitXml Action. Supported from: MX 9.1

Disallow Submit XML Package Name: Specifies the Package Name that should be disallowed from submitting XML. Supported from: MX 4.2

Allow Submit XML Package Name: Specifies the Package Name that should be Allowed to submit XML. Supported from: MX 4.2

Action: Specifies a Device Administration Action to be performed. Supported from: MX 9.2

Firmware Update Button: Specifies whether the device user should be allowed to use the Firmware Update Button to perform Firmware Updates using the Device Central subsystem. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Bluetooth Pairing Control: Specifies how the Device Central subsystem should control pairing. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Bluetooth On/Off Control: Specifies whether the Device User should be allowed to use the Device Central UI to control Bluetooth Power. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Set Font Size: Specifies the system font size to use. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Set Display Size: Specifies the system Display size to use. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Debounce Delay: Specifies which Debounce Delay that will be used for the Signal that will be used to control automatic Display Blanking. Default value = 1000. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Polarity: Specifies which Polarity of the Signal that will be used to control automatic Display Blanking. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Signal: Specifies which Signal will be used to control automatic Display Blanking. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Stay Awake: Specifies whether the Display will stay awake (not time out) when connected to external power. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.2

Blanking Mode: Specifies whether the Display will automatically Blank (display nothing) when triggered by a signal. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Timeout: Specifies the amount of device user inactivity (in seconds) before the screen will timeout. Supported from: MX 4.3

Auto Capitalization: Set whether automatic capitalization of the first letter of a sentence should be turned on within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Auto Correction: Set whether automatic correction of the misspelled words should be turned on within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Block Offensive Words: Set whether automatic blocking of offensive words should be turned on within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Double Space Period: Set whether automatic entry of end of sentence (period followed by two spaces) occurs within the Enterprise Keyboard when the space key is double tapped. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Flick for Alternate Chars: Set whether alternate characters will be shown within the Enterprise Keyboard when a flick gesture is performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.1

Key Long Press Delay: Set the length of time a key within the Enterprise Keyboard must be held pressed to be considered a long press. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Navigation Mode: Set the navigation mode that should be used to control the behavior of the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Numeric Layout Mode: Set the numeric layout mode that should be used when the Enterprise Keyboard that a numeric keyboard should be displayed. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.1

Show Alphanumeric Tab: Set whether the alphanumeric tab (to switch to alphanumeric keyboard) will be shown within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Show Numeric Tab: Set whether the numeric tab (to switch to numeric keyboard) will be shown within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Show Scan Tab: Set whether the key to scan tab (to control barcode scanning) will be shown within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Show Symbol Tab: Set whether the symbol tab (to switch to special symbols keyboard) will be shown within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Show Voice Input Key: Set whether the key to invoke voice input (if supported) will be shown within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Preferred Tab: Set the preferred tab the Enterprise Keyboard should select when entering textual data. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Suggest Contact Names: Set whether showing contact name suggestions based on prior actions should be turned on within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Suggest Misspelling Corrections: Set whether showing correction suggestions while typing should be turned on within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Popup on Keypress: Set whether key popup (visible feedback) occurs on each keypress within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Sound on Keypress: Set whether sound (audible feedback) occurs on each keypress within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Mode: Set the sound volume mode that will be used when a sound occurs on each keypress within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Volume: Set the sound volume that will be used when a sound occurs on each keypress within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Vibrate on Keypress: Set whether vibrate (tactile feedback) occurs on each keypress within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Mode: Set the vibrate duration mode that will be used when a vibrate occurs on each keypress within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Duration: Set the vibrate duration that will be used when a vibrate occurs on each keypress within the Enterprise Keyboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Remap Alpha P1: Set the remapping that the Enterprise Keyboard should apply to the P1 key on the Alpha keyboard at Row 1, Column 1. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Remap Numeric P1: Set the remapping that the Enterprise Keyboard should apply to the P1 key on the Numeric keyboard at Row 1, Column 1. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Remap Numeric P2: Set the remapping that the Enterprise Keyboard should apply to the P2 key on the Numeric keyboard at Row 2, Column 1. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Remap Numeric P3: Set the remapping that the Enterprise Keyboard should apply to the P3 key on the Numeric keyboard at Row 3, Column 1. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Remap Numeric P4: Set the remapping that the Enterprise Keyboard should apply to the P4 key on the Numeric keyboard at Row 3, Column 1. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Remap Symbol P1: Set the remapping that the Enterprise Keyboard should apply to the P1 key on the Symbol keyboard at Row 4, Column 1. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Reset to Defaults: Specifies whether the Enterprise NFC settings should all be reset to their default values. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Type A Tags: Specifies whether the Enterprise NFC should read NFC Type A Tags. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Type B Tags: Specifies whether the Enterprise NFC should read NFC Type B Tags. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Type F Tags: Specifies whether the Enterprise NFC should read NFC Type F Tags. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Type V Tags: Specifies whether the Enterprise NFC should read NFC Type V Tags. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Use NFC Data Exchange Format (NDEF): Specifies whether the Enterprise NFC should use NFC Data Exchange Format (NDEF). Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Polling Mode: Specifies the Enterprise NFC Polling Mode that should be used. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

CPU Boost: Specifies whether the Enterprise NFC should Boost CPU Speed during NFC transactions. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Type A Tag Baud Rate: Specifies the Baud Rate that Enterprise NFC should use for Type A Tags. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Type B Tag Baud Rate: Specifies the Baud Rate that Enterprise NFC should use for Type B Tags. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Peer to Peer Mode: Specifies whether the Enterprise NFC should use Peer to Peer Mode. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Card Emulation Mode: Specifies whether the Enterprise NFC should use Card Emulation Mode. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Use on Lock Screen: Specifies whether the Enterprise NFC should be allowed to be used from the Lock Screen. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Power: Specifies whether Ethernet Power will be turned on or off. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Control by User: Specifies whether Ethernet Power control by the Device User will be allowed or not. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Use Proxy Server: Specifies whether to use a Proxy Server to use for Ethernet. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Proxy Server: Specifies the Proxy Server to use for Ethernet. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Port: Specifies the Proxy Server Port to use for Ethernet. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Bypass List: Specifies the Proxy Server Bypass List to be used for Ethernet. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

IP Address Type: Specifies how an IP Address will be assigned to the Ethernet adapter. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

IP Address: Specifies the IP Address to be statically assigned to the Ethernet adapter. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Gateway Address: Specifies the Gateway Address to be statically assigned to the Ethernet adapter. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Network Mask: Specifies the Network Mask to be statically assigned to the Ethernet adapter. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Primary DNS: Specifies the Primary DNS Server Address to be statically assigned to the Ethernet adapter. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Secondary DNS: Specifies the Seconday DNS Server Address to be statically assigned to the Ethernet adapter. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Delete Path and File Name: Specifies the Path and optionally the File Name of a Folder or File to be Deleted from the Device File System. Supported from: MX 5.0

Download Destination Path and File Name: Specifies the Destination Path and File Name of a File to be Downloaded to the Device File System from a Server. Supported from: MX 5.0

Download File Source URI: Specifies the Source URI of a File on a Server to be Downloaded to the Device File System. Supported from: MX 5.0

Device User Control Mode: Specifies whether the Device User should be allowed to use the UI of the LifeGuard OTA Client. Supported from: MX 9.1

Mode: Specifies whether Firmware Updates will be Automatic (via the LifeGuard OTA Client) or Manual (via Legacy Methods). Supported from: MX 9.1

Mode Manual Action: Specifies a FOTA action to be performed when FOTA operations are being performed in Manual Mode. Supported from: MX 8.1

Enterprise Reset SUW Bypass: Specifies whether the Setup Wizard (SUW) will be bypassed on GMS devices when performing an Enterprise Reset. Supported from: MX 7.1

OS Streaming – Authorization Type: Specifies the authentication type to use to reach the remote file. Supported from: MX 10.0

OS Upgrade Suppress Reboot: Specifies whether an automatic reboot should be suppressed (not performed) following the completion of an A/B Upgrade performed using the OS Upgrade Action. Supported from: MX 8.1

OS Streaming – Custom Authentication Header: Enter Authorization header custom value. Supported from: MX 10.0

OS Streaming – Password: Enter the password associated with the name of a user authorized to access the ZIP file. Supported from: MX 10.0

OS Streaming – Username: Enter the name of a user authorized to access the ZIP file. Supported from: MX 10.0

OS Streaming – Zebra Authentication Token: Enter Authentication token for Zebra Support Central. Supported from: MX 10.0

OS Streaming File URL: Specifies the URL of the file (ZIP, UPL, XML, etc.) to be used for an OS Streaming Action. Supported from: MX 10.0

OS Update/Upgrade/Downgrade File: Specifies the file (ZIP, UPL, XML, etc.) to be used for an OS Update Action. Supported from: MX 8.1

Verify Manifest File: Specifies the file to be used for a Verify Manifest Action. Supported from: MX 8.1

GMS Profile: Select the GMS Profile that identifies the GMS Feature Subset to be used. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

GMS Feature Set: Select Set of GMS Features to be used. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Action: Specifies a GPRS action to be performed. Supported from: MX 8.4

APN Settings

Add APN Name: Specifies the name for an APN to be added. Supported from: MX 4.2

Add APN Replace If Existing: Specifies whether the APN should be replaced if an APN with the same name already exists. Supported from: MX 4.2

Add APN Make Default: Specifies whether the APN should be made the new default APN. Supported from: MX 4.2

Add APN Access Point: Specifies the Access Point Identifier for an APN to be added. Supported from: MX 4.2

Add APN User Name: Specifies the User Name of an APN to be added. Supported from: MX 4.2

Add APN Password: Specifies the Password for an APN to be added. Supported from: MX 4.2

Add APN Port: Specifies the HTTP Proxy port number for an APN to be added. Supported from: MX 8.4

Add APN Proxy: Specifies the HTTP Proxy address or name for an APN to be added. Supported from: MX 8.4

Add APN MMS Port: pecifies the port number of a MMS Gateway Proxy Server for an APN to be added. Supported from: MX 8.4

Add APN MMS Proxy: Specifies the address or name of a MMS Gateway Proxy Server for an APN to be added. Supported from: MX 8.4

Add APN Server: Specifies the WAP Gateway Server for an APN to be added. Supported from: MX 8.4

Add APN MMSC: Specifies the MMSC for an APN to be added. Supported from: MX 8.4

Add APN Type: Specifies the Type of an APN to be added. Supported from: MX 8.4

Add APN MCC: Specifies the MCC for an APN to be added. Supported from: MX 8.4

Add APN MNC: Specifies the MNC for an APN to be added. Supported from: MX 8.4

Add APN Protocol: Specifies the Specify the APN protocol . Supported from: MX 9.3

GPRS Configuration – Action Add APN Roaming Protocol: Specifies the Specify the APN roaming protocol . Supported from: MX 9.3

Add Authentication Type: Specifies the Authentication Protocol to be used for an APN to be added. Supported from: MX 8.3

Add MVNO Type: Specifies the MVNO Type to be used for an APN to be added. Supported from: MX 8.4

Add MVNO Match Data: Specifies the MVNO match Data to be used for an APN to be added. Supported from: MX 8.4

Remove APN Name: Specifies the name of an APN to be removed. Supported from: MX 4.1.1

Action: Specifies a UI Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Clear Application Data Package: Specifies a package name for which the cache should be cleared with performing a Clear Application Cache Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Clear Application Data Package: Specifies a package name for which all data should be cleared for the current user when performing a Clear Application User Data Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Advanced Device Settings

Allow Device User Control of Do Not Disturb Mode: Sets whether the Device User should be allowed to control Do Not Disturb Mode. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

App Info Icon on Long Press on Recent App Header: Specifies whether an App Info Icon will be shown on Long Press on Recent App Header. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.2

Auto Correct: Sets whether Automatic Correction of Entered Data will be Performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Battery Charging LED: Specifies whether the hardware charging system is allowed to use the battery charging LED to indicate battery charging state. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Battery Swap UI Popup: Specifies whether a Device User will automatically be presented with the Battery Swap UI when the device battery level drops below a fixed threshold. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Display of Navigation Bar: Sets whether the on-screen Navigation Bar will be displayed and hence whether it will take up screen real estate and can be used to navigate the device UI. Supported from: MX 7.1

Launcher Package Name: Specifies the package name of the default launcher package. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.1 Locale: Specifies a Locale to be made the current Locale. Supported from: MX 5.1

Long Press on Home Key to Launch Google Assistant: Specifies whether a Long Press on the Home Key will Launch the Google Assistant. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.2

Network Notification Popup: Sets whether the Network Notification Popup will be presented to inform the Device User that their network may be monitored. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.1

On-Screen Power Button: Specifies whether the On-Screen Power Button can be used. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Pull Down Notification Bar: Sets whether the Device User is allowed to Pull Down the Notification Bar to interact with notifications in the Notifications Panel. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.1

Show Airplane Mode in Power Key Menu: Specifies whether the Airplane Mode option should be shown in the Power Key Menu. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Show Pairing Popup: Specifies whether the pairing popup should be displayed for new Bluetooth pairings. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Show Passwords: Specifies whether passwords should be visibility displayed globally on the device. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Show Virtual Keyboard when Physical Keyboard is Active: Sets whether the Virtual Keyboard will be shown when the Physical Keyboard is Active. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Status Bar: Sets whether the Android Status Bar should be displayed. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.4

Use Of Clipboard: Specifies whether the device user is allowed to use the clipboard. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.2

Use of Date in Notification Panel to Access Clock Application: Specifies whether the Date in the Notification Panel can be used to invoke the Clock Application. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.2

Use of Home Key: Sets whether the device user is allowed to Use the Home Key. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Use of Magnification Gestures: Sets whether the Device User is allowed to Use Magnification Gestures. Supported from: MX 8.0

Use of Recent Apps Key: Sets whether the Device User is allowed to Use the Recent Apps Key to access recently launched applications. Supported from: MX 7.1

Use of Split Screen Mode: Sets whether Split Screen Mode is allowed to be used on the device. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

User Control of Multi User: Specifies whether the Primary Device User is allowed to invoke UI to manage Multi User, including the ability to Create, Delete, and limit the actions of Secondary Users. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Touch Mode: Specifies the touch panel mode. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Screen Protector: Specifies the touch panel mode should account for the presence of a screen protector. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Turn on/off the Large Key Indicator feature: Turn the Large Key Indicator on or off. Supported from: MX 9.0

Device user control of Large Key Indicator: Select whether the user may turn Large Key Indicator on/off. Supported from: MX 9.0

Device Name: Specifies the name by which the device will be known on the network. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.1

Add Mapping Behaviors: Specifies a list of behaviors to be defined for a key for an AppMapping Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Table Name: Specifies the name of the key mapping table into which a defined behavior should be added by an AddMapping Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Type: Specifies the behavior to be defined for a key when Action is Add Mapping. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Send Key Code: Specifies a key code to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Alt: Specifies with the alt state should be set when a key code to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Ctrl: Specifies with the ctrl state should be set when a key code to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Fn: Specifies with the fn state should be set when a key code to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Shift: Specifies with the shift state should be set when a key code to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Send Trigger: Specifies a trigger to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Send Intent: Specifies when an intent will be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Type: Specifies an intent type to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Action: Specifies an intent action to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Category: Specifies an intent category to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Package Name: Specifies an intent package name to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Class: Specifies an intent class to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Data URI: Specifies an intent data uri to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Flags: Specifies an intent flags to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

MIME Type: Specifies an intent mime type to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Extra Name: Specifies an intent extra name to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Extra Value: Specifies an intent extra value to be sent by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Launch Application Name: Specifies an application name to be launched by behavior. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Add Mapping Key ID: Specifies the identifier of the key to be remapped for an AddMapping Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Action: Specifies a Key Map Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Permission Access Action: Specifies an action to be performed to manage which Sensitive Android Permissions are allowed to be used by which applications. Supported from: MX 10.0

Grant Permission: Specifies the name of a Sensitive Android Permission to be Granted to a specified Application. Supported from: MX 10.0

Grant Application Package: Specifies a Package Name that identifies an application to which a specified Sensitive Android Permission should be Granted. Supported from: MX 10.0

Grant Application Signature: Specifies a Package Signature that identifies an application to which a specified Sensitive Android Permission should be Granted. Supported from: MX 10.0

Revoke Permission: Specifies the name of a Sensitive Android Permission to be Revoked from a specified Application. Supported from: MX 10.0

Revoke Application Package: Specifies a Package Name that identifies an application from which a specified Sensitive Android Permission should be Revoked. Supported from: MX 10.0

Revoke Application Signature: Specifies a Package Signature that identifies an application from which a a specified Sensitive Android Permission should be revoked. Supported from: MX 10.0

Ask Permission: Specifies the name of a Sensitive Android Permission, the granting or revoking of which should be left to the Device User for a specified Application. Supported from: MX 10.0

Ask Application Package: Specifies a Package Name that identifies an application for which the granting or revoking of a specified Sensitive Android Permission should be left to the Device User. Supported from: MX 10.0

Ask Application Signature: Specifies a Package Signature that identifies an application for which the granting or revoking of a specified Sensitive Android Permission should left to the Device User. Supported from: MX 10.0

Power Action: Specifies a Power Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.1

Battery Percentage Decommission Threshold: Specifies the percentage of remaining battery capacity below which the battery will be deemed ready for decommissioning. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Battery Usage Decommission Threshold: Sets the amount of battery usage (e.g. charge/discharge cycles, coulombs in/out, etc.) that can occur before the battery is deemed to be need to be decommissioned. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Battery Critical Low Threshold: Sets the threshold battery level below which the battery is deemed to be critically low. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Battery Optimization Action: Sets the action to be performed related to adding or removing applications that should be subject to battery optimization. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Add Package Names: Sets the list of package names (comma separated) to be added to the list of packages to be subject to battery optimization. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Remove Package Names: Sets the list of package names (comma separated) to be removed from the list of packages to be subject to battery optimization. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.0

Port Action: Specifies an Action to be performed related to control of Power to a Port. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Port Select: Specifies an Port for which the Output power will be turned on or off. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Auto Power Control: Specifies whether device power will be automatically controlled. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Auto Power Off: Specifies whether/how device power will be automatically turned off as part of automatic power control. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Timeout: Specifies the timeout that will be in effect before device power is automatically turned off as part of automatic power control. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Auto Power On: Specifies whether/how device power will be automatically turned on as part of automatic power control. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Heater Action: Specifies an Action to be performed related to control of Device Heaters. Supported on Android: Oreo and Pie. Supported on Device(s): VC80X and VC8300. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Heater Select: Specifies the Heater to be affected by a specified Heater Action. Supported on Android: Oreo and Pie. Supported on Device(s): VC80X and VC8300. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Off Threshold: Specifies the threshold temperature above which the specified Heater should automatically turn off. Supported on Android: Oreo and Pie. Supported on Device(s): VC80X and VC8300. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

On Threshold: Specifies the threshold temperature below which the specified Heater should automatically turn on. Supported on Android: Oreo and Pie. Supported on Device(s): VC80X and VC8300. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

All Wake-up Sources State: Select whether all Wake-Up Sources will be enabled or not. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Doze Mode State: Specifies a whether Doze Mode should be used globally on the device. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.2

Wake-up Source Key Identifier: Select the key identifier of the Wake-Up Source to control. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Custom: Enter the Custom name of the key identifier of the Wake-Up Source to control. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Wake-up Source to Activate the Display State: Turn on or off the ability of a Wake-up Source to activate the display. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Wake-up Method: Select the Method that will be used to implement and control device Wake-up. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.3

Query Target: Specifies which tags will be be the target when a tag query is initiated. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Query Session: Specifies which query session will be used when a tag query is initiated. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Query Select: Specifies what types of tags will be selected to be queried when a tag query is initiated. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Transmit Power Level: Specifies the power level to be used when the RFID module radio is transmitting. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Update Firmware File: Specifies a File in the device file system that will be used to perform an Update Firmware Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Action: Specifies an Action that will be performed by the RFID Module. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Channel Hopping: Specifies whether hopping will be performed between supported Channels for the selected Country in which the RFID Module will Operate. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Channel Mask: Specifies the Channel Mask that derives from the fixed channel sequence for the selected Country in which the RFID Module will Operate, enforcing compliance to appropriate Regulatory Requirements. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Country of Operation: Specifies the Country in which the RFID Module will Operate, enforcing compliant to appropriate Regulatory Requirements. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Unpair Serial Number: Specifies the Serial Number of the Remote Scanner to be affected by the Unpair Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.2

Disconnect Serial Number: Specifies the Serial Number of the Remote Scanner to be affected by the Disconnect Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.2

Page Serial Number: Specifies the Serial Number of the Remote Scanner to be affected by the Page Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.2

Reset Serial Number: Specifies the Serial Number of the Remote Scanner to be affected by the Reset Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.2

Update File: Specifies the Remote Scanner Update File to be applied by the Update Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Update Serial Number: Specifies the Serial Number of the Remote Scanner to be affected by the Update Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Config File: Specifies the Remote Scanner Config File to be applied by the Config Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.2

Config Serial Number: Specifies the Serial Number of the Remote Scanner to be affected by the Config Action. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.2

Action: Specifies the Remote Scanner Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Screen Lock Timeout: Specifies the amount of time following screen off after which the screen will be locked when it is turned back on. Supported from: MX 4.3

Screen Lock Type: Specifies the type of Screen Lock (e.g. None, Swipe, PIN/Password, Pattern, etc.) to be used. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.0

Instant Screen Lock on Power Key: Set whether a Screen Lock (if a Screen Lock Type is configured) will occur immediately when the display screen is turned off using the Power Key (vs. waiting until the Screen Lock Timeout expires). Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Encrypt SD Card Key Name: Specifies the name of a named encryption key to be used when performing the encrypt SD Card action. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Remove Key Name: Specifies the name of a named encryption key to be removed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Add Key Value: Specifies the value of a named encryption key to be added. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Add Key Name: Specifies the name of a named encryption key to be added. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Action: Specifies a Security Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Service Binding Action: serviceBindingAction. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Allow Service Identifier: Specifies A Service Identifier to which Binding should be allowed when the Service Binding Action is Allow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Disallow Service Identifier: Specifies A Service Identifier to which Binding should NOT be allowed when the Service Binding Action is DIsallow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Service Caller Action: serviceCallerAction. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Allow Service Identifier: Specifies A Service Identifier to which Calling should be allowed when the Service Caller Action is Allow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Allow Caller Package: Specifies A Caller Package Name that should be allowed to call a specified Service when the Service Caller Action is Allow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Allow Caller Signature: Specifies A Caller Signature that should be allowed to call a specified Service when the Service Caller Action is Allow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Disallow Service Identifier: Specifies A Service Identifier to which Calling should NOT be allowed when the Service Caller Action is Disallow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Disallow Caller Package: Specifies A Caller Package Name that should NOT be allowed to call a specified Service when the Service Caller Action is Disallow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Disallow Caller Signature: Specifies A Caller Signature that should NOT be allowed to call a specified Service when the Service Caller Action is Disallow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Use CSP Action: Specifies an action to be performed to manage which CSPs are protected and which applications are allowed to use protected CSPs. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Protect CSP Auto Approve: Specifies whether the callers of a CSP being protected should be automatically be approved to use that CSP when the Use CSP Action is Protect. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Protect CSP Name: Specifies the name of a CSP to be protected when the Use CSP Action is Protect. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Custom: Specifies the name of a custom CSP to be protected when the Use CSP Action is Protect. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Unprotect CSP Auto Unapprove: Specifies whether the callers of a CSP being unprotected should be automatically be unapproved to use that CSP when the Use CSP Action is Unprotect. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Unprotect CSP Name: Specifies the name of a CSP to be unprotected when the Use CSP Action is Unprotect. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Custom: Specifies the name of a custom CSP to be unprotected when the Use CSP Action is Unprotect. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Approve CSP Name: Specifies the name of a CSP to be approved when the Use CSP Action is Approve. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Custom: Specifies the name of a custom CSP to be approved when the Use CSP Action is Approve. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Approve Caller Package: Specifies A Caller Package Name that should be allowed to use a specified Protected CSP. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Approve Caller Signature: Specifies A Caller Package Signature that should be allowed to use a specified Protected CSP. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Unapprove CSP Name: Specifies the name of a CSP to be unapproved when the Use CSP Action is Unapprove. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Custom: Specifies the name of a custom CSP to be unapproved when the Use CSP Action is Unapprove. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Unapprove Caller Package: Specifies A Caller Package Name that should NOT be allowed to use a specified Protected CSP. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Unapprove Caller Signature: Specifies A Caller Package Signature that should NOT be allowed to use a specified Protected CSP. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Use CSP Function Group Action: Specifies an action to be performed to manage which CSP Function Groups exist, are protected, and which applications are allowed to use them. Supported from: MX 10.0

Create Group Details: Specifies the details of a custom CSP Function Group to be created. Supported from: MX 10.0

Create Group Name: Specifies the name of a CSP Function Group to be created,. Supported from: MX 10.0

Delete Group Name: Specifies the name of a CSP Function Group to be deleted. Supported from: MX 10.0

Protect Auto Approve: Specifies whether the caller of a CSP Function Group being protected should be automatically be approved when the Use CSP Function Group Action is Protect. Supported from: MX 10.0

Protect Group Name: Specifies the name of a CSP to be protected when the Use CSP Action is Protect. Supported from: MX 10.0

Custom: Specifies the name of a custom CSP Function to be protected when the Action is Protect and the custom option is selected for group name. Supported from: MX 10.0

Unprotect Auto Unapprove: Specifies whether the caller of a CSP Function Group being unprotected should be automatically be unapproved to use when Action is Unprotect. Supported from: MX 10.0

Unprotect Group Name: Specifies the name of a Function Group CSP to be unprotected when the Use CSP Action is Unprotect. Supported from: MX 10.0

Custom: Specifies the name of a custom Function Group CSP to be unprotected when the Action is Unprotect. Supported from: MX 10.0

Approve Caller Package: Specifies A Caller Package Name that should be approved to use a specified Protected CSP Function Group. Supported from: MX 10.0

Approve Caller Signature: Specifies A Caller Package Signature that should be approved to use a specified Protected CSP Function Group. Supported from: MX 10.0

Approve Group Name: Specifies the name of a CSP Function Group to which a specified Package is to be approved to use. Supported from: MX 10.0

Custom: Specifies the name of a custom CSP Function Group to which a specified Package is to be approved to use. Supported from: MX 10.0

Unapprove Caller Package: Specifies A Caller Package Name that should be unapproved to use a specified Protected CSP Function Group. Supported from: MX 10.0

Unapprove Caller Signature: Specifies A Caller Package Signature that should be unapproved to use a specified Protected CSP Function Group. Supported from: MX 10.0

Unapprove Group Name: Specifies the name of a CSP Function Group to which a specified Package is to be unapproved to use. Supported from: MX 10.0

Custom: Specifies the name of a custom CSP Function Group to which a specified Package is to be unapproved to use. Supported from: MX 10.0

Allow Device User Access Quick Settings: Specifies whether the device user is allowed to Access Quick Settings. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.2

Allow Device User Control Airplane Mode: Specifies whether the device user is allowed to control the stage of Airplane Mode. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Allow Device User Control App Notifications: Sets whether the device user is allowed to control App Notifications. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.2

Allow Device User Control Apps: Specifies whether the device user is allowed to control Apps. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Allow Device User Control Background Data: Specifies whether the device user is allowed to control the use of Background Data. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Allow Device User Control Ethernet: Specifies whether the device user is allowed to control Ethernet. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Allow Device User Control Instant Lock: Specifies whether the device user is allowed to control Instant Lock on Power Key. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Allow Device User Control USB: Specifies whether the device user is allowed to control USB. Supported from: MX 4.2

Allow Device User Control Unknown Sources: Specifies whether the device user is allowed to control Unknown Sources. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Allow Device User Control WLAN: Specifies whether the device user is allowed to control WLAN. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Allow Device User to Initiate an Enterprise Reset: Specifies whether the device user is allowed to initiate an Enterprise Reset. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.2

Show Quick Settings Icon: Specifies whether the Quick Settings Icon will be displayed. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.1

Use Reduced Version: Specifies whether to use the reduced version of Settings or the full version. Supported from: MX 4.1

Use of Notification Settings Icon: Sets whether the Device User is allowed to use the Settings Icon on the Notification Panel to launch the Settings UI. Not supported on Device(s): TC20 and TC25. Supported from: MX 5.1

Use of Settings Slide Out Drawer: Sets whether the Device User is allowed to use the Slide Out Drawer in Settings UI to rapidly switch laterally to other parts of the Settings UI. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Use of Tethering and Portable Hotspot: Sets whether the Device User is allowed to use the Settings UI to configure and utilize Tethering and Portable Hotspot mode. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Action: Specifies a Threat Management Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Detect Threat Type: Specifies a Type of Threat to be detected when Action is Detect. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Detect Countermeasures: Specifies the list of countermeasures to be applied when a specified threat is detected. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Unsolicited Alert Message: Specifies the Message that should be sent by an Unsolicited Alert countermeasure. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Unsolicited Alert Class: Specifies the Class to which an Unsolicited Alert countermeasure should be sent. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Unsolicited Alert Package Name: Specifies the Package Name to which an Unsolicited Alert countermeasure should be sent. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Uninstall Package Name: Specifies the Package Name to be uninstalled for an Uninstall Package countermeasure. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Type: Specifies a type of a countermeasure to be applied when a specified threat is detected. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Additional Device Settings

Action Detect Threat Type MDM Client Removal Package Name: Specifies the MDM Client Package Name, removal of which will trigger the MDM Client Removal threat. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Ignore Threat Type: Specifies a Type of Threat to be ignored when Action is Ignore. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Periodic Scan: Specifies whether Threat Management should perform periodic scans for threats. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.1

Interval: Specifies the interval, in seconds, at which Threat Management should perform periodic scans for threats if periodic scans are turned on. Default value = 30. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.1

Additional Folders: Specifies whether Threat Management should perform periodic scans of additional folders for threats. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.1

List: Specifies the list of additional folders (separated by commas) that Threat Management should perform periodic scans of for threats. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.1

Send Externally Detected Threat Message: Specifies a message to be sent to notify Threat Management of the occurrence of the externally detected threat. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Set Current Profile Adjust Volume: Specifies whether to adjust the system volumes based on the presets of a Profile when a Profile is made the current active Profile. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Set Current Profile Name: Specifies the name of a Profile to be made the current active Profile. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Remove Profile Name: Specifies the name of a Profile to be Removed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Visible: Specifies a Stream for a Profile being added will be visible in the UI. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Icon: Specifies the Icon for a Steam for a Profile being added. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Label: Specifies the label associated with a Stream for a Profile being added. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Type: Specifies the type of a Stream for a Profile being added. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Add Profile Streams: Specifies a list of Streams to be configured for a Profile. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Modes: Specifies the mode to be configured for a given Stream. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Type: Specifies the mode type for a single mode to configured for a single Stream for a Profile. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Preset: Specifies the preset volume level that can configured for a single mode of a single Stream for a Profile. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Maximum: Specifies the maximum volume level that can configured for a single mode of a single Stream for a Profile. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Minimum: Specifies the minimum volume level that can configured for a single mode of a single Stream for a Profile. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Add Profile Name: Specifies the name of a Volume UI Profile to Add. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Action: Specifies the Volume UI Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Wakeup Sources: Specifies whether (ALL) Wakeup Sources should be enabled or disabled. Supported from: MX 8.0

Select Wakeup Source Method: Specifies the wake source type to use. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

State: Specifies whether whitelisting of non-built-in (downloadable and installable) applications will be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.1

Disallow Package Name: Specifies the Package Name to be Disallowed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.1

Disallow Signature: Specifies the Signature to be Disallowed for a specified Package. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Allow Signature: Specifies the Signature to be Allowed for a specified Package. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Allow Package Name: Specifies the Package name to be Allowed or Disallowed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.1

Action: Specifies the Whitelist Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Mode: Specifies the whitelisting mode that will be used if whitelisting is On. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

GPS Power State: Specifies whether the GPS radio state should be On or Off. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.3

Antenna Selection: Specifies which of multiple antennas should be used for wireless communications. Not supported on Device(s): TC20 and TC25. Supported from: MX 7.1

Auto Wakeup: Sets whether the WLAN should wakeup (turn on) automatically. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Bands: Specifies the Bands to be configured. Supported from: MX 4.1

Channels: Specifies the RF Channels to use. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.1

Country: Specifies the Country to be configured (or none for Auto). Supported from: MX 4.1

Hotspot State: Sets whether the Hotspot feature should be turned on or off. Supported from: MX 8.1

Verbose Logging: Sets whether the Verbose should be turned on or off. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Security Passphrase: Sets the Security Passphrase to use for the Hotspot feature. Supported from: MX 6.3

Security Mode: Sets the Security Mode to use for the Hotspot feature. Supported from: MX 6.3

5GHz Channel: Sets the Channel to use for the 5GHZ Band for the Hotspot feature. Supported from: MX 6.3

Band 2.4GHz Channel: Sets the Channel to use for the 2.4GHZ Band for the Hotspot feature. Supported from: MX 6.3

Band: Sets the Band to use for the Hotspot feature. Supported from: MX 6.3

SSID: Sets the SSID to use for the Hotspot feature. Supported from: MX 6.3

Datarate: Sets the data rate to use for Omnitrail. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Standard: Sets the data rate standard to use for Omnitrail. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Options: Specifies one or more Omnitrail options to be configured as part of this OemConfig Step. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Value: Sets the Value of an Omnitrail option to be set for a corresponding Name. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Name Custom: Sets the name of a custom (non-standard) Omnitrail option to be set. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Name: Sets the name of a standard Omnitrail option to be set. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Interval: Sets the Omnitrail interval to use (200 to 5000). Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

State: Sets whether the stage of Omnitrail is On or Off. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.0

Advanced Options: Specifies one or more advanced options to be configured as part of this OemConfig Step. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.4

Value: Specifies the Value of an advanced WiFi option to be configured for a corresponding Name. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.4

Custom Name: Sets the name of a custom (non-standard) advanced WiFi option to be set. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.4

Name: Specifies the name of a standard advanced WiFi option to be configured. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.4

Diagnostics Options: Specifies one or more Diagnostics options to be configured as part of this OemConfig Step. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Value: Specifies the Value of an Diagnostic WiFi option to be configured for a corresponding Name. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Name Custom: Sets the name of a custom (non-standard) Diagnostic WiFi option to be set. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Name: Specifies the name of a standard Diagnostic WiFi option to be configured. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

Network Notification: Specifies whether the Device User will be notified about, and allowed to connect to, new WLANs that are detected. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.1

Power: Specifies whether the WWAN power should be turned on or off. Supported from: MX 4.3

Background Data: Specifies whether the use of WWAN background data should allowed or not. Supported from: MX 4.3

State: Specifies whether the WWAN data should be turned on or off. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

SIM Card Slot: Specifies which SIM Card slot to make the active one. Supported from: MX 6.2

Data Limit State: Specifies whether a limit should be imposed on the amount WWAN data that can be used. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Custom Limit: Specifies a custom limit that should be imposed on the amount WWAN data that can be used. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

Data Warning Threshold: Sets the threshold at which a warning to the device user should be generated if the amount WWAN data that has been used exceeds that threshold. Supported from: MX 6.3

User Control of Background Data: Specifies whether the device user should be allowed to control whether WWAN data can be used in the background. Not supported on Device(s): TC20 and TC25. Supported from: MX 4.4

User Control of Data Limit: Specifies whether the device user should be allowed to control the limits on WWAN data that can be used. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

User Control of Power: Specifies whether the device user should be allowed to control WWAN power (turn it on or off). Not supported on Device(s): TC20 and TC25. Supported from: MX 6.3

User Control of Sim Socket: Specifies whether the device user should be allowed to control which WWAN SIM socket is used. Not supported on Device(s): TC20 and TC25. Supported from: MX 6.2

Public Land Mobile Network Lock: Specifies whether the device should be locked to a specific Public Land Mobile Network Lock (PLMN). Supported from: MX 8.1

Value: Specifies the specific Public Land Mobile Network Lock (PLMN) to which the device should be locked. Supported from: MX 8.1

User Control of Public Land Mobile Network Lock: Specifies whether the device user should be allowed to control whether the device is locked to a specific Public Land Mobile Network (PLMN). Not supported on Device(s): TC20 and TC25. Supported from: MX 8.1

Dual SIM Dual Standby Mode: Specifies whether the device should operate dual SIM Cards in Dual SIM Dual Standby Mode. Supported on Device(s): L10, TC57, and TC77. Supported from: MX 8.1

Manual Preferred Text Message Subscription SIM: Specifies the SIM that identifies the Subscription to be used as the preferred Subscription for Text Messages when Manual Subscription Selection is used. Supported on Android: Oreo and Android 10. Supported on Device(s): L10, TC57, and TC77. Supported from: MX 10.0

Manual Preferred Voice Call Subscription SIM: Specifies the SIM that identifies the Subscription to be used as the preferred Subscription for Voice Calls when Manual Subscription Selection is used. Supported on Android: Oreo and Android 10. Supported on Device(s): L10, TC57, and TC77. Supported from: MX 10.0

Manual Preferred Data Subscription SIM: Specifies the SIM that identifies the Subscription to be used as the preferred Subscription for Data Communications when Manual Subscription Selection is used. Supported on Android: Oreo and Android 10. Supported on Device(s): L10, TC57, and TC77. Supported from: MX 10.0

Automatic Preferred Subscription SIM: Specifies the SIM that identifies the Subscription to be used as the preferred Subscription when Automatic Subscription Selection is used. Supported on Android: Oreo and Android 10. Supported on Device(s): L10, TC57, and TC77. Supported from: MX 10.0

Automatic Out of Service Timeout: Specifies the timeout value (in seconds) that the Subscription for the current SIM must remain in an Out of Service condition before automatic switching to the Subscription for the other SIM may occur. Supported on Android: Oreo and Android 10. Supported on Device(s): L10, TC57, and TC77. Supported from: MX 10.0

Subscription Selection: Specifies how Subscription Selection should be performed. Supported on Android: Oreo and Android 10. Supported on Device(s): L10, TC57, and TC77. Supported from: MX 10.0

Unlock Unlock Code: Specifies a string value to use as the Unlock Code for an Unlock Action. This must be the same value previously specified for the Lock Action to be reversed. Supported from: MX 9.2

Unlock Type: Specifies the the Unlock Type to be used for a Unlock Action to be performed. This should match the Lock Type of the prior Lock Action to be reversed. Supported from: MX 9.2

Lock ICCID: Specifies the ICCID, also known as the SIM Card identifier, identifying the ICCID/SIM Card to which a device should be Locked. Supported from: MX 9.2

Lock Network List: Specifies the Network List, as one or more MCC or MNC values, identifying the network(s) to which a device should be Locked. To provide multiple values, separate with commas (e.g. 1,310410,31012). Supported from: MX 9.2

Lock Unlock Retry Count: Specifies the integer Retry Count, from 1-99, for a Lock Action, indicating the maximum number of times a subsequent Unlock Action can be attempted unsuccessfully before disallowing Unlock. Supported from: MX 9.2

Lock Unlock Code: Specifies a string value to use as the Unlock Code for a Lock Action. The same value will need to be provided to perform a subsequent Unlock Action. Supported from: MX 9.2

Lock Type: Specifies the Lock Type to be used for a Lock Action to be performed. Supported from: MX 9.2

Lock Action: Specifies the Lock Action to be performed. Supported from: MX 9.2

Unlock Unlock Code: Specifies a string value to use as the Unlock Code for an Unlock Action. This must be a device-specific value provided by the MNO that originally performed the Lock Action to be reversed. Supported from: MX 9.2

Lock Unlock Retry Count: Specifies the integer Retry Count, from 1-99, for a Lock Action, indicating the maximum number of times a subsequent Unlock Action can be attempted unsuccessfully before disallowing Unlock. Supported from: MX 9.2

Lock Control Key: Specifies the Control Key that will later be used to create Unlock Codes for devices Locked using that Control Key. Supported from: MX 9.2

Lock Activation ID: Specifies the Activation ID that will grant the MNO the permission to perform a Lock Action. Supported from: MX 9.2

Lock Action: Specifies the Lock Action to be performed. Supported from: MX 9.2

Import Lock Info: Specifies whether MNO Lock Information will be Imported from a file stored on the SD Card of the device and used to Lock a device based on information previously Exported from the same or a different device. Supported from: MX 9.2

Wipe Lock Info: Specifies whether the current MNO Lock Information will be Wiped, thus forcing the device to return to an Unlocked state. Supported from: MX 9.2

Export Lock Info: Specifies whether the current MNO Lock Information will be Exported and stored to a file on the SD Card of the device. Supported from: MX 9.2

Activation ID: Specifies the Activation ID that will grant the Service Technician the permission to perform a Service operation. Supported from: MX 9.2

State: Specifies whether the Worry Free WiFi feature should be turned on or off. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Device User Control: Specifies whether the Device User should have access to the UI to control Worry Free WiFi features. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Temporary Password Value: Specifies a Temporary Password that can be shared with a Device User to provide temporary and limited access to configure Worry Free WiFi to collect packets and encrypt those packets without having to share the full administrative password (which provides full access and never expires). Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Worry Free WiFi Configuration – Global Settings Temporary Password Duration: Specifies duration in hours after which a Temporary Password expires and must be replaced with a new one. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Worry Free WiFi Configuration – Global Settings Temporary Password Allow: Specifies whether a Temporary Password feature will be Allowed or Disallowed. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.2

Password Value: Specifies the Password Value that controls Device User access to configure Worry Free WiFi features. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Existing Password: Specifies the Existing Password that is required to change to a new Password that controls Device User access to configure Worry Free WiFi features and encryption of Captured Packet Data. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Analysis Type: Specifies the type of Worry Free WiFi Action to be performed. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Action: Specifies a Worry Free WiFi Action to be performed as part of this OemConfig Step. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Start Server Analytics: Specifies the whether Server Analytics should be performed during a session started for the Worry Free WiFi feature. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Start Activity Mode: Specifies the activity mode for Server Analytics performed during a session started for the Worry Free WiFi feature. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Start Analysis SSID: Specifies the SSID that should be used for Server Analytics performed during a session started for the Worry Free WiFi feature. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Start Session Name: Specifies the name of the Analytics session to be started for the Worry Free WiFi feature. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Start Logger Report Level: Specifies the Logger Report Level to be used during Server Analytics performed during a session started for the Worry Free WiFi feature. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Start Ping Type: Specifies whether Pings performed as part of the Analytics session started for the Worry Free WiFi feature should be data-less or should include data. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Start Remote Gateway Type: Specifies the Type of Remote Gateway to use for the Analytics session to be started for the Worry Free WiFi feature. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Custom Server Address: Specifies the Server Address of the Custom (non-default) Gateway to use for the Analytics session to be started for the Worry Free WiFi feature. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Start SD Card Storage: Specifies the how SD Card Storage should be used during Server Analytics performed during a session started for the Worry Free WiFi feature. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Type: Specifies the type of Worry Free WiFi Packets to be captured. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

On Max Storage Size: Specifies the maximum storage size to which Packet Capture should grow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

On Max File Size: Specifies the maximum size file into which Packet Capture should store can grow. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

On File Name: Specifies the file name into which Packet Capture should store. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

State: Specifies whether Packet Capture should be turned on or off for the Worry Free WiFi feature. Not supported on Device(s): TC20 and TC25. Supported from: MX 8.3

Start Session Name: Specifies the Session Name that should be used Worry Free WiFi as part of Coverage View. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Start Server Analytics: Specifies whether Server Analytics should be performed by Worry Free WiFi as part of Coverage View. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Start Auto Reachability Test: Specifies whether an Auto Reachability Test should be performed by Worry Free WiFi as part of Coverage View. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Start Scan Interval: Specifies Scan Interval to be used by Worry Free WiFi for scanning performed as part of Coverage View. Default value = 5. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Start SSID: Specifies the Service Set ID (SSID) that identifies the network to be used by Worry Free WiFi for scanning performed as part of Coverage View. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Action: Specifies an Action to be performed by Worry Free WiFi as part of Coverage View. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

Scan Feature Type: Specifies the type of Scan Feature Worry Free WiFi Packets should perform as part of Coverage View. Not supported on Device(s): TC20 and TC25. Supported from: MX 9.1

License Action: Specify a Zebra Mode licensing action to be performed. Supported from: MX 8.1

Activate License Method: Specify the Method by which the Zebra Mode license to be activated will be acquired. Supported from: MX 7.1

From Server AID Value: Specify the Activation ID (AID) to be used when acquiring a Zebra Mode license from a Server. Supported from: MX 7.1

From Server Standard Class: Specify the class of Standard Server from which Zebra Mode licenses are to be acquired. Supported from: MX 7.1

From Server Custom Class: Specify the class of Custom Server from which Zebra Mode licenses are to be acquired. Supported from: MX 7.1

From Server Custom URL: Specify the URL of the specific Custom Server from which Zebra Mode licenses are to be acquired. Supported from: MX 7.1

From Server Custom Friendly Name: Specify the Friendly Name of the specific Custom Server from which Zebra Mode licenses are to be acquired. Supported from: MX 7.1

From Local File Path and Name: Specify the Path and Name of a local file in the device file system from which a Zebra Mode license is to be acquired. Supported from: MX 7.1

From Local File Source Server Class: Specify the class of Server from which a Zebra Mode license that is to be applied from a local file was acquired. Supported from: MX 7.1

Return License Server Type: Specify the Type of Server from which Zebra Mode licenses was acquired and hence to which it should be returned. Supported from: MX 8.1

Friendly Name: Specify the Friendly Name of the Server from which Zebra Mode licenses was acquired and hence to which it should be returned. Supported from: MX 8.1

Return License AID Value: Specify the Activation ID (AID) of the Zebra Mode license that is already activated on the device and is to be returned. Supported from: MX 8.1

Return All Licenses Server Type: Specify the Type of Server from which Zebra Mode licenses were acquired and to which all acquired licenses should be returned. Supported from: MX 8.1

Friendly Name: Specify the Friendly Name of the Server from which Zebra Mode licenses were acquired and to which all acquired licenses should be returned. Supported from: MX 8.1

Refresh License AID Value: Specify the Activation ID (AID) of the Zebra Mode license that is already activated on the device and is to be refreshed. Supported from: MX 7.1

Delete Server Friendly Name: Specify the Friendly Name of the Server to be Deleted. Supported from: MX 8.1

Note:

It is highly recommendable to use the native policies wherever possible as the OEMConfig features are still relatively new. The introduction of OEMConfig has opened up a new set of possibilities which will be added to in the future and the existing features are expected to get more fine-tuned.

Zebra focuses on enterprise performance enghancing product lines which includes tablets, printers, mobile computers and enterprise scanners.

A dedicated device management service like Hexnode MDM can assist such devices to maximize productivity at any workplace.

FAQs

What is the difference between standard Android management and Zebra OEMConfig?

Standard Android management covers core controls such as enrollment, app management, restrictions, networking, and kiosk configurations. Zebra OEMConfig extends these capabilities with manufacturer-specific settings exposed through Zebra Mobility Extensions (MX).

When should IT teams use Zebra OEMConfig instead of native Android policies?

Zebra OEMConfig is useful when a deployment requires controls that standard Android management does not expose. These can include Zebra-specific hardware, connectivity, firmware, scanner, and device configuration options.

Can Hexnode manage Zebra devices through Android Enterprise?

Yes, Hexnode can manage supported Zebra devices using Android Enterprise enrollment and management capabilities. Depending on the enrollment mode, IT teams can manage the entire device or maintain a separate managed work profile.

How to setup Zebra device management using Hexnode MDM

TL;DR

Why Zebra device management requires more than standard Android management

How to setup Zebra device management using Hexnode’s native device management features?

Enrollment

Management

Restrictions

Policies

Other key features

How Zebra MX and OEMConfig extend Android Enterprise management

How to setup Zebra device management using Hexnode’s OEMConfig capabilities?

OEMConfig – Breaking the boundaries of Android device management

Controlling Zebra OS and firmware updates

Zebra’s OEMConfig capabilities with Hexnode MDM

FAQs

Share

Jayden Traoré

You May Also Like

[Infographic] OEMConfig process simplified

OEMConfig – Breaking the boundaries of Android device management

Why Motorola rugged devices are the right choice for tough industrial applications?

Toughening the security for Nokia HMD Global rugged devices in the enterprise

Join readers from 120 countries

Subscribe to Hexnode Blog

How to setup Zebra device management using Hexnode MDM

TL;DR

Why Zebra device management requires more than standard Android management

How to setup Zebra device management using Hexnode’s native device management features?

Other key features

How Zebra MX and OEMConfig extend Android Enterprise management

How to setup Zebra device management using Hexnode’s OEMConfig capabilities?

OEMConfig – Breaking the boundaries of Android device management

Controlling Zebra OS and firmware updates

Zebra’s OEMConfig capabilities with Hexnode MDM

FAQs

Share

Jayden Traoré

You May Also Like

Join readers from 120 countries