OEMConfig Setup

OEMConfig 15.0

Overview

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 Google Play 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.

System Requirements

*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.

Download and Install

The specific process for setting up an EMM console for Zebra OEMConfig varies depending on the system in use. For EMMs compatible with Google Play, the generally required steps are shown below.

IMPORTANT: OEMConfig 15.0 (and later) can target GMS and non-GMS devices; capabilities vary by download source (see below).

General EMM Setup

  • Download the OEMConfig app:
  • Point the EMM console to the Zebra schema to display Zebra's data-driven UI for configuring devices.
  • Create Transaction(s) using Managed Configurations as described in the schema.
  • Push the OEMConfig Android app (OEMConfig.apk) to target Zebra device(s).
  • Push Transaction(s) to target device(s) for consumption by OEMConfig app.

Using CloudDPC?

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.

About The Schema

Every .apk that supports Managed Configurations must provide a schema, which defines the Managed Configurations supported by that .apk. Google Play provides server-to-server APIs that allow an EMM server to acquire the schema from the Google Play for the published .apk. There's more about schemas on the FAQ page.

Also See