SOTI Pulse Logo

Zebra OEM Config causing Wifi to drop repeatedly every time settings are applied

DL
Dan Lewis
Pilkington Group Limited

My Mobicontrol server is offline and so I have no enterprise binding.

Using Mobicontrol I have deployed Zebra OEM config (com.zebra.oemconfig.release) to Android 13-14 Zebra scanners in my enviroment specifically to apply Datawedge settings as it was recomended by Zebra since using  MXCONFIG with a StageNow XML is deprecated.

The managed configuration transaction items inlclude downloading the datawedge.db and applying it.  All other configuration items are left blank or "do not change" is set.  This feature is working just fine.

I am seeing a serious issue with all devices that I have deployed OEM config to.  Every time the device re-applies OEM Config's transactions it is repeatedly disconnected from Wifi.  Once it is finished applying the connection is stable again for an hour or so.  Then the issue loops.  Has anyone encountered this issue or have any recomendations?

OEM Config mobicontrol android zebra
yesterday
SOTI MobiControl
ANSWERS
MD
Matt Dermody Diamond Contributor
21 hours ago

Are you sure there aren't any other MX WiFi settings contained within the OEMConfig Managed Configuration settings? The WiFi radio will bounce if any WiFi related MX settings are applied. 

DL
Dan Lewis
6 hours ago

Hi Matt,

There are blank wifi setting getting applied as Soti includes all 440 possible transactions in the JSON payload.  The targeted client's OEM config logs are a mile long full of these blank transactions (some of which error because of the null value being invalid).  If you use the "export" feature in the "managed app config" window you will get a JSON back that has EVERY POSSIBLE TRANSACTION with the undefined ones having blank values.  Even when I created a JSON that only included the values I want and used the "import" feature it simply merged those values back into the group of 440.

-Dan

Similar Discussions