Zebra Android Devices: The Difference Between MX and OEMConfig

Administrators managing Zebra Android devices have multiple tools and methods available for configuration, including Zebra's Mobility Extensions (MX) via StageNow or XML, the Legacy Zebra OEMConfig application, and the newer Zebra OEMConfig Powered by MX application. It can be confusing to understand the purpose, capabilities, and appropriate use cases for each method, leading to uncertainty about which tool to use for specific configuration tasks or device/OS versions.

• Zebra Android Enterprise devices managed under SOTI MobiControl

• Configuration performed using:

  • Zebra StageNow tool

  • SOTI MobiControl deploying direct MX XML

  • SOTI MobiControl profiles deploying Legacy Zebra OEMConfig via Managed Google Play

  • SOTI MobiControl profiles deploying Zebra OEMConfig Powered by MX via Managed Google Play

• Uncertainty about whether to use StageNow/MX XML or an OEMConfig app for a specific configuration setting.

• Confusion regarding the existence of two different Zebra OEMConfig applications in the Managed Google Play Store.

• Difficulty finding specific MX features within an OEMConfig application schema.

• Configuration failures when using an inappropriate method (e.g., trying to use an older MX feature via a newer OEMConfig app that doesn't expose it, or vice-versa).

• Inconsistent configuration capabilities across devices with different Android OS versions or firmware builds.

Understand the fundamental differences between direct MX configuration and the OEMConfig standard, as well as the specific characteristics of Zebra's Legacy and Powered by MX OEMConfig implementations. Choose the configuration method that best aligns with your specific configuration requirements. 

The different configuration methods exist due to the evolution of Android device management and Zebra's strategy:

• Zebra MX: Zebra's proprietary framework providing deep device control beyond standard Android Enterprise capabilities. It predates the widespread adoption of OEMConfig.

• OEMConfig Standard: Google's initiative to allow OEMs (like Zebra) to expose their unique management features (like MX) through a standardized application interface within SOTI MobiControl.

• Legacy Zebra OEMConfig: Zebra's initial implementation of the OEMConfig standard.

• Zebra OEMConfig Powered by MX: Zebra's current, recommended OEMConfig implementation, designed for more frequent updates and alignment with the latest MX features and Android versions.

Understanding the core differences to help in select the appropriate method

1. Zebra MX (Direct Configuration - StageNow / XML):

https://techdocs.zebra.com/mx/

• What it is: Zebra's underlying management framework. Configuration is done using tools like StageNow (which generates encrypted XML or barcodes) or by directly crafting and deploying MX XML via SOTI MobiControl.

• Pros: Offers direct access to the full suite of MX features available on the device's specific MX/OS version. Can be used for initial device staging (StageNow barcodes) or ongoing management (XML via SOTI MobiControl).

• Cons: Requires using Zebra-specific tools (StageNow) or manual XML creation. Integration within the SOTI MobiControl Webconsole is limited to simply deploying the XML file rather than having interactive configuration fields.

• When to Use: Complex staging scenarios, accessing MX features not yet exposed via OEMConfig, troubleshooting specific MX feature behavior.

• 

2. OEMConfig (General Concept):

https://support.google.com/work/android/answer/9388447

• What it is: A Google standard. OEMs (like Zebra) create an "OEMConfig app" published on the Managed Google Play Store. SOTI MobiControl reads this app's schema to display configuration options directly within the EMM console. When SOTI MobiControl sends a configuration, the OEMConfig app on the device receives it and translates it into device-specific commands (like MX commands for Zebra).

• Pros: Standardized configuration within SOTI MobiControl. Potentially easier configuration workflow for admins comfortable using the web console.

• Cons: Feature availability depends on what the OEM exposes in their specific OEMConfig app schema. Configuration possibilities are limited by the schema version of the deployed OEMConfig app.

3. Legacy Zebra OEMConfig:

https://techdocs.zebra.com/oemconfig/

• What it is: Zebra's older OEMConfig application (often identifiable by the package name (com.zebra.oemconfig.common).

• Pros: Provides access to a range of MX features via the OEMConfig standard on devices/firmware where it was the primary supported version.

• Cons: Updated less frequently than "Powered by MX". May lack support for the newest MX features or compatibility with the latest Android OS requirements (e.g., certain permission grants on newer OS versions). Generally considered legacy.

• When to Use: Required for specific older Zebra devices or OS/firmware versions that do not fully support "Zebra OEMConfig Powered by MX", or if explicitly recommended by Zebra documentation for a particular scenario/device build (especially around the Android 11/12 transition period for some models).

• 

4. Zebra OEMConfig Powered by MX:

https://techdocs.zebra.com/oemconfig/

• What it is: Zebra's current, recommended OEMConfig application (often identifiable by the package name (com.zebra.oemconfig.release).

• Pros: Updated frequently via the Managed Google Play Store, providing faster access to new MX features and ensuring compatibility with the latest Android Enterprise requirements and Zebra device capabilities. Aligns more closely with ongoing MX development. Generally offers the widest range of configurable features via the OEMConfig standard.

• Cons: Requires the device to have a compatible underlying MX version. Feature availability is still dependent on the schema version and the underlying device capabilities.

• When to Use: Recommended for most modern Zebra devices running supported Android versions (especially Android 11+). Use this for SOTI MobiControl-based configuration whenever possible, unless specific compatibility issues necessitate Legacy OEMConfig or direct MX configuration.
  

• Check Compatibility: Always verify the recommended OEMConfig app version and required minimum MX/OS version for your specific Zebra device model in the official Zebra documentation or release notes.

• SOTI MobiControl Support: Both Legacy Zebra OEMConfig and Zebra OEMConfig Powered by MX are supported through the Managed App Config in the App policy. From SOTI MobiControl 2025.1, both OEMConfig variants are available as a profile.