Does Headwind Application Settings support Zebra OEMConfig?

Question

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?

https://h-mdm.com/zebra/#datawedge

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

Answer 1

Headwind MDM supports Zebra OEMConfig (through application settings) since version 6.29. See details here: https://h-mdm.com/zebra/#oemconfig

Comments

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"}}})?