Deploy Zebra OEMConfig and Enterprise Browser

Application: Nomid MDM Document: V1.0.0 Last updated: 07/11/2026 Editorial owner: Nomid MDM Documentation Last editorial review: 07/11/2026 Editorial language: en-US

This guide shows how to install two Zebra apps from managed Google Play on Zebra devices managed by Nomid MDM, and how to configure them with managed configurations:

• Zebra OEMConfig Powered by MX (com.zebra.oemconfig.release) applies Zebra device settings, such as the clock, display, Wi-Fi, scanner (DataWedge), keyboard and licenses, through Zebra's MX management framework.
• Zebra Enterprise Browser (com.zebra.mdna.enterprisebrowser) runs web apps on Zebra devices with kiosk, scanning and SAP options.

You can deploy either app on its own. The steps use the Policy 2.0 editor. In the Classic editor, the same fields open from the gear on the app card; see 4.1 Tablet policies — Classic.

Risk: OEMConfig changes settings of the device itself. A wrong Wi-Fi, clock, screen lock, Google services or update value can disconnect the device from the network and from device management, lock people out or restart the device. Enterprise Browser kiosk settings can disable the HOME, BACK and RECENT keys. The device behavior in this guide comes from Zebra's documentation. Test every change on a pilot policy with one Zebra device before you link the policy to the fleet.

Before you begin

• An Android Enterprise company in Nomid MDM with fully managed Zebra devices, and the Edit policy permission for the policy you will change.
• Zebra devices with Google Play services. Managed Google Play installs both apps only on devices with Google Mobile Services (GMS). For devices without GMS, Zebra offers OEMConfig from its support portal; that installation is outside this guide.
• The right OEMConfig app for the Android version. According to Zebra, Zebra OEMConfig Powered by MX (com.zebra.oemconfig.release) supports Android 11 and later and is not compatible with Android 10 or earlier. Legacy Zebra OEMConfig (com.zebra.oemconfig.common) supports older devices and is not compatible with Android 13 or later. For a fleet with both, use separate policies. This guide uses Powered by MX.
• For Enterprise Browser managed configurations, Zebra requires Enterprise Browser 5.0 or later on Zebra devices running Android 11 or later. Enterprise Browser licensing is handled by Zebra; see Zebra's Enterprise Browser documentation.
• A pilot policy linked to a single Zebra test device, so a wrong value affects only that device.

Add the apps to the policy

1. In the Nomid Portal, open Policies and select the pilot policy.
2. Open the Apps & experience tab and select Apps in this policy.
3. Select Add App. Choose Add via Package, type com.zebra.oemconfig.release and confirm that Zebra OEMConfig Powered by MX appears under the field. Select Add. You can also choose Add via Play Store and search for the app in managed Google Play.

Type the package name and check that the match is the Zebra app before you add it.

4. Repeat step 3 with com.zebra.mdna.enterprisebrowser to add Zebra Enterprise Browser.
5. Both apps appear in the list with the Configurable badge, which means they publish managed configurations. The pane footer shows Edited. Save the policy to apply until you save. The installation choice next to each app starts as Required, which installs the app and keeps it on the device. Optional, Blocked and the other app controls are described in 4. Policies — Policy 2.0.

Open the managed configurations

Select the gear next to the app in the list. The Managed configurations editor lists every field that the current version of the app publishes. Google Play supplies this list from the app, so it changes when Zebra releases a new version; Google Play keeps only the latest schema.

• Each field shows its title, a description written by Zebra and the key name. Zebra publishes titles and descriptions in English. The button next to the key copies a link to that field.
• OEMConfig descriptions often end with Supported from: MX and a version, or Not supported on Device(s) and a list of models. A field has no effect on a device with an older MX version or on a listed model.
• Default value shows the value the app declares. It is information only: the editor does not send it.
• A choice field shows Select options... until you pick a value. While it shows that text, Nomid sends nothing for the field. Use the × in a field to clear it. Some OEMConfig choices include Do not change, which is a value Zebra defines, not an empty field.
• Groups open and close with the arrow on the right; Expand All and Collapse All do it for every group. A group that has values shows Clear configuration, which clears every value in that group.
• Lists, such as Files Configuration or Package Configuration in OEMConfig, start empty. Add New Item adds an element and shows its fields; the × on the element removes it.
• Use the filter box to find a key, and All, Filled or Not Filled to review what you have entered.
• Delete all configurations, at the end of the editor, clears every value for this app in the policy.
• Save keeps your values in the policy edit. Cancel asks Discard your changes?: Discard leaves the editor without them, and Keep editing returns to it. Neither sends anything to devices until you save the policy.

Zebra OEMConfig settings

OEMConfig Powered by MX groups its settings into nine top-level groups. On 07/11/2026 the editor showed close to 500 fields, plus the fields of each list element. The table lists the groups and what they cover, using Zebra's own descriptions. For each field, follow its description in the editor and Zebra's OEMConfig documentation.

Collapse All shows the top-level groups and their keys; scroll for the rest. Open only the group you need.

Some groups need extra care:

• Wireless LAN and Network Connection change how the device connects. Nomid policies also manage Wi-Fi networks under Connectivity. Configure each network in one place only, and keep a working network on the pilot device until the change is confirmed.
• GMS Configuration can limit which Google apps and services run. Android Enterprise management and managed Google Play rely on Google Play services.
• Lifeguard Configuration controls Zebra LifeGuard OS updates, including update mode, updates over cellular data and reboot suppression. Plan it with your update windows; Nomid policies also have system update settings under System.
• Screen Lock Configuration overlaps with the password and lock settings of the Nomid policy. Set each option in one place only.
• Pass-Through Command sends MX XML directly to the device. Zebra's description says the XML must not include Batch, ConditionMgr or persist XML. Use it only for features the schema does not expose.

Sample OEMConfig values for shared frontline devices

This example keeps the clock and screen consistent on shared devices. Replace ntp.example.com with your time server.

Enterprise Browser keys

Zebra describes how Enterprise Browser handles managed configurations in Using Managed Configurations:

• Managed configurations and a Config.xml file cannot be combined. When managed configurations arrive, Enterprise Browser writes a new Config.xml that contains only those values; every other setting returns to its default.
• New values take effect the next time Enterprise Browser starts. If it is running when a change arrives, it shows a message on the device.
• Enterprise Browser must be installed and opened on the device once before any configuration applies.
• Zebra states that some Enterprise Browser settings are available only in Config.xml. If you need one of them, use Config.xml instead of managed configurations.

Each field shows its key and the default value Zebra declares.

The tables follow the field titles shown in the editor; when the key is different, it appears in parentheses. Most default values appear as numbers: according to Zebra, 0 is the first choice (Turn Off, Hidden or Use EMDK) and 1 is the second (Turn On, Shown or Use DataWedge). On 07/11/2026 the editor showed 67 fields and 2 lists.

Navigation Configuration (navigationConfig)

Kiosk Configuration (kioskConfig)

Barcode Scanning Configuration (barcodeScanningConfig)

ScannerOnNav and ExistingAudioFile sit under EMDKBarcodeConfiguration; the three beeper fields sit under UseEBGeneratedAudio inside it. Zebra requires all three beeper fields to be set together.

Application UI Configuration (appUiConfig)

Broadcast Receiver Configuration (broadcastReceiverConfig)

DOM Custom Configuration (domCustomConfiguration)

License, keyboard and WebView

The zoom fields sit under webViewConfig > webUiConfig > zoomConfig, and the viewport fields under viewPortConfig beside it.

SAP ITS and ZPP

These groups apply only to SAP apps. SAP ITS Configuration (sapItsConfig) is for SAP ITSmobile apps, and ZPP Configuration (zppConfig) is for Zebra Picking Plus, Zebra's Enterprise Browser app for SAP Extended Warehouse Management (EWM).

The first eleven rows belong to SAP ITS and the rest to ZPP.

Names in Zebra's documentation

Zebra's managed configurations page lists most settings by the titles above, not by their keys, and a few names differ from the editor: it uses BadLinkUri for BadLinkUrl, EbKb for KbEb and IntentCategrory for the intent category list, and it does not list AutoRotate. The editor shows what the app publishes, and Nomid sends the keys it shows.

Sample Enterprise Browser policy for shared frontline devices

This example opens a warehouse web app in full screen and keeps the browser on company sites. Replace the addresses with your own.

Check every address your web app loads, including sign-in pages, on the pilot device: an address missing from UrlWhitelist is blocked.

To keep people inside Enterprise Browser, prefer Nomid's single-app kiosk: under Launcher mode, choose Nomid Kiosk, Single-app and Enterprise Browser as the Kiosk app, as described in 4. Policies — Policy 2.0. It keeps a maintenance exit protected by a password. If you turn off the HOME, BACK and RECENT keys in Enterprise Browser instead, check on the pilot device that you can still leave the app for maintenance.

Use Filled to review every value before you save.

Save and apply the policy

1. In the managed configurations editor, select Save, then Done in the apps pane.
2. Select Save in the policy header, review the list of changes and confirm.
3. Linked devices receive the policy when they synchronize. OEMConfig applies the values it receives; Enterprise Browser applies them the next time it starts.

Verify on the device

1. In Devices, open the pilot device, run a synchronization and confirm that both apps are installed.
2. Check each OEMConfig setting on the device itself. With the sample values, the Android date and time settings should show automatic time and the 24-hour format, and the screen should turn off after five minutes. Zebra's release notes say OEMConfig 10.0 and later show a SUCCESS or FAILURE result for managed configuration actions. The Nomid Portal does not show these results.
3. Open Enterprise Browser once. If it was already open, close it and open it again. The start page opens in full screen, the status bar is hidden, and an address outside UrlWhitelist is blocked.

Troubleshooting

Undo the configuration

• To stop sending a value, clear the field with its ×, then save the policy. Clearing a field does not necessarily restore the device's earlier setting; to change a device setting back, choose the value you want and save.
• Clear configuration clears one group, and Delete all configurations clears every value of the app in this policy after you save.
• To remove an app, change its installation to Blocked, as described in 4. Policies — Policy 2.0, and save.

See also

• 4. Policies — Policy 2.0: apps and launcher mode
• 4.1 Tablet policies — Classic: app managed configuration
• 3. Devices: synchronization and installed apps
• Zebra OEMConfig documentation
• Zebra OEMConfig frequently asked questions
• Zebra Enterprise Browser: using managed configurations