Zebra OEMConfig Profile

PC
Paul Courtney
nokiantyres

I have Zebra TC21's that we are bringing into Mobicontrol, there are some feature settings that I can only find in the OEMConfig profiles.  The profile shows up on the device page but for three days it is stuck at 'Pending Installation.  The OEM config app is installed on the device and the only setting is to lock the rotation of the screen.

Any suggestions?

7 months ago
SOTI MobiControl
ANSWERS
MD
Matt Dermody Diamond Contributor
7 months ago

OEMConfig administers Zebra MX configuration settings. The TC21 by default is a purposefully feature limited value tier device from Zebra that does not support all of the available MX configuration options that you see available in OEMConfig. You can filter the MX feature matrix by "Professional Series" to see the reduced set of configuration options available to the TC21.

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

If you want to have the full set of OEMConfig /MX configuration options available to you on these cheaper Zebra devices you have to purchase a separate Mobility DNA Enterprise license and apply it to the device in order to unlock those capabilities.

I can't say for sure that this is the cause of the Pending Installation issues but it would otherwise not surprise me to hear there are issues applying OEMConfig settings to this particular device model since we know that it is a device that has a purposefully stripped down set of capabilities, including a reduced list of MX settings that will work with it, without the Mobility DNA Enterprise license. 

PC
Paul Courtney
7 months ago

The configuration work with Stage Now, and it works if you send the Stage Now XML file to the device then run a script to activate it.  The profile using the build in Zebra OEM Config does not.

MD
Matt Dermody Diamond Contributor
7 months ago

That's a good test. If the settings apply correctly through StageNow they should also work through OEMConfig. The issue therefore appears to be more related to the delivery of the OEMConfig payload.

How are you administering OEMConfig? Are you doing so as a Public Google Play app delivered via App Policy, a standalone Enterprise app delivered through App Policy, or through the configuration payload in Profiles?

The configuration payload in Profiles may not work in your situation and you may need to utilize the original method of App Policy based distribution with Managed Configurations as you would need to specify which OEMConfig to use based on the situation. 


PC
Paul Courtney
7 months ago

These are all Android 13 devices so the .release version is used.   They are installed both ways, Play Store and APK.  Both are showing the same behavior.  The profile just says 'Pending Installation'.  This is the same thing that happens in Intune as well using the OEMConfig.  I was hoping that someone had gotten it to work correctly, and I was just missing something.

RK
Radim Kadlec
6 months ago

I just tested OEMConfig (via a Soti profile) on Zebra TC21 Android 13 (13-38-24.00-TG-U00-STD-HEL-04) and everything works as expected.

Have you checked if your device has access to Google Play to download the OEMConfig app?

K
KAMOD@soti.net
6 months ago

Hi Paul,

Thanks for posting on SOTI Pulse.  Thanks, Radim and Matt for responding to the post, your expertise and willingness to help are greatly appreciated!

Has your query been resolved? If this post did not assist you in resolving the issue completely and you have additional questions, please do not hesitate to reach out or you can contact SOTI Support (support@soti.net) to open a new case and one of our support engineers will be there to assist you.

Kind Regards
Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |