Welcome to Headwind MDM Q&A, where you can ask questions and receive answers from other members of the community.

Please do not post bug reports, missing feature requests, or demo inquiries. If you have such an inquiry, submit a contact form.

0 votes
Hi, if Application Settings can’t manage third-party apps, does that mean Zebra OEMConfig (package com.zebra.oemconfig.release) cannot be configured via Headwind as described here?
I’m testing on a Zebra HC25 (Android 14) enrolled as Device Owner (com.hmdm.launcher/.AdminReceiver). OEMConfig is installed, but in the OEMConfig app the fields like “Last update / Last bundle / Last keyed” remain blank after I set Application Settings entries (both simple keys like btState and SecuritySLScreenLockTimeout).
related to an answer for: Apllication settings usage
by (120 points)

1 Answer

0 votes
Headwind MDM supports Zebra OEMConfig (through application settings) since version 6.29. See details here: https://h-mdm.com/zebra/#oemconfig
by (45.3k points)
Extra details / reproducible example (HC25, Android 14):
OEMConfig: com.zebra.oemconfig.release 15.0.0.1
Headwind: com.hmdm.launcher 6.30

Trying to set 24h clock via Headwind → Configuration details → Application settings.

Attempt 1 (flat key):
Attribute: sysClockTimeFormat Value: 1 → OEMConfig: “key does not exist in the schema”.

Attempt 2 (bundle JSON):
Attribute: systemConfig Value: {"clockConfig":{"sysClockTimeFormat":"1"}}
→ OEMConfig: “Nothing to do”, and I also get:
KEY: clockConfig → “Bundle contains ‘clockConfig’ that does not exist in the schema” (so it seems to arrive as a top-level key).

Zebra docs show it’s nested: systemConfig → clockConfig → sysClockTimeFormat.
Does Headwind support bundle-type managed configs for OEMConfig? If yes, what’s the correct syntax (e.g. should it be {"systemConfig":{"clockConfig":{"sysClockTimeFormat":"1"}}})?
Hey, any update on this?
Having the same problem on a Zebra TC22.
No matter what I do, the fields in OEMConfig remain empty.
Using Android 13 / 14 an OEMConfig 15.1.0.1.
The attribute values should be in plain text.

I guess Headwind MDM can only set string attributes, whereas your attribute is integer. We will fix this issue in a future version of Headwind MDM.

By the way, are you able to set a string attribute of OEMConfig?
Hi, according to the Zebra documentation https://techdocs.zebra.com/oemconfig/15-1/mc2/ "sysClockTimeFormat" is a string value.
I have also tested other string settings such as "sysClockAutoNtpServer" and "uiUserAccessDeviceStorageViaUsb", but without success.
I find it a bit surprising that, although I configured the settings as described in the Headwind documentation (Configuring the device by OEMConfig), nothing is shown in the OEMConfig app on the device.
The fields “Last update broadcast” and “Last bundle processed” remain empty.
Thank you in advance!
...