Zebra OEMConfig is an administrative tool for performing Actions and settings configurations on Zebra devices running Android. OEMConfig works with Zebra's Mobility Extensions Management System (known simply as MX), an XML-based communication framework for managing the capabilities and behaviors of Zebra devices.
OEMConfig is not pre-installed on Zebra devices; it must be installed through the Google Play store before it can be used to perform Actions and configure settings. These activities are typically done using an Enterprise Mobility Management (EMM) or Unified Endpoint Management (UEM) system.
- Fully managed Zebra device(s) running Android 7.x (Nougat) or higher
- MX 9.1 or higher* on device(s) is recommended. Which version is installed?
- A UEM or EMM system with support for OEMConfig-compliant admin tools
*OEMConfig runs on devices with MX versions older than MX 9.1, but attempting to access newer MX features not implemented in older MX versions will result in error(s). See the MX Feature Matrix for a complete list of features in each MX version.
The exact process for setting up an EMM console to use Zebra OEMConfig varies widely depending on the device management system in use. For EMMs compatible with the Google Play system, the generally required steps are listed below.
- Download OEMConfig app from Google Play Store
- Point EMM console to Zebra schema to display data-driven UI for configuring Zebra devices
- Create Transaction(s) using Managed Configurations described in schema
OEMConfig.apkto the Zebra device(s) to be configured
- Push Transaction(s) to device(s) for consumption by OEMConfig tool
For EMMs that use the Android Management APIs and Google's CloudDPC device policy controller as their EMM agent, Google offers an option to define a JSON document that specifies a set of
.apks to be installed, Managed Configurations to be applied to those
.apks, and other non-application-oriented management operations. In such a case, some of the steps above would happen together in a way that might not be obvious to the administrator or console operator.
.apk that supports Managed Configurations must provide a schema, which defines the Managed Configurations supported by that
.apk. The Play Store provides server-to-server APIs that allow an EMM server to acquire the schema from the Play Store for the published
.apk. There's more about schemas on the FAQ page.