Hi Keith,

1)What version of MobiControl are you trying to setup these configurations on?

2)Are you trying to configure these settings for Android Enterprise Devices or Android+ devices?

3)What specific Symbology settings are you trying to configure? 

Does Datalogic expose those non-standard Android configurations through some sort of configuration file? If so you could build the config files and deploy them to the device as part of a package. SOTI is not going to natively expose the configuration of those settings within the webconsole until such a point that both SOTI and Datalogic support OEMConfig. 

This is running on:

Android 4.4.4 (They say it's enterprise)

I'm testing this in MobiControl cloud based platform, and the agent is 13.6.0 build 1257.

The settings I'm trying to configure to start are:

Code 39: Disable Checksum

Code 32: Disable

EAN13: Send Checksum Enabled

EAN13: Send System Digit Enabled

UPCA: Send Checksum Enabled

UPCA: Send System Digit Enabled

Wedge: Enable keyboard wedge

Notification: Disable display notification

Ultimately I want to disable everything we want disabled and enable everything we want enabled since I've seen fresh handhelds from the factory arrive with different defaults. To ensure consistency, I want to define everything we want disabled and everything we want disabled . (It's not much more than above)

In addition we have wireless settings we want adjusted as mentioned above.

-Keith

I'm not sure. Datalogic told us SOTI lets you push these configurations, so we reached out and SOTI told us it did also. We started the trial, and now I'm trying to find where to set these settings and not really get the feeling that what I was told was true.

So I did find a way to export the majority of the settings I need, the problem is they export them as a binary in what I'm guessing is a proprietary format, it ends in a .DXU extension and is exported from their "DXU Datalogic Configuration Utility". Not sure if there is a way to push that via SOTI, but if there is it would be what gets me over the hump of deciding whether to go with SOTI or even continue considering the Datalogic devices. Personally I'm surprised there isn't an enterprise configuration deployment option, they can't possibly expect people to configure these things by hand.

If all you need to do is distribute the .DXU file to a specific directory on the device then you should be able to do that with the Package Builder. 

You have to realize that currently there are a number of common Android management APIs that will be shared across all versions of Android. Those common configurations are typically exposed by an EMM like SOTI within a UI like Feature Control. Manufacturers with specific use cases like a ruggedized DataLogic barcode scanning device have to build their own supplemental management APIs on top of the baseline Android management APIs maintained by Google as their needs are likely to be somewhat unique (eg. like programming a barcode symbology setting) which would not be applicable to all Android devices and therefore would not be something that Google would natively have support for managing. If you what you're saying is true that Datalogic exposes these configurations as an external file that you can deploy through any EMM, then you should consider yourself lucky as otherwise you would be configuring those settings manually on every device. 

What it sounds like you're looking for is an "Easy Button" that exposes all of the device specific configuration settings within the EMM admin console so that you can administer them without having to manually create a configuration file and deploy it. That kind of process will ultimately be delivered as OEMConfig, a solution that Zebra co-developed with Google, but is not limited to just Zebra Android devices. It is limited to manufacturers that build support for OEMConfig and to newer versions of Android that are enrolled with Android Enterprise (previously AFW). Until Datalogic adds support for OEMConfig and you get devices that are on a newer version of Android that actually supports Android Enterprise (4.4 is relatively long in the tooth) then you'll be stuck deploying an external configuration, which to my earlier point is really not that bad compared to manually configuring every device. 

From the SOTI console, you can send a "script" calling Datalogic's Android intent to apply the DXU configuration you have.

Here is the syntax of the script (adapted to work with SOTI):

sendIntent -b "intent:#Intent;component=com.datalogic.dxu/.plugin.EnterpriseReceiver;action=com.datalogic.dxu.action.APPLY_SETTINGS;S.path=/sdcard/config.dxu;end;"

In this example, the DXU configuration file is config.dxu located under /sdcard/ on the device.

Just a quick update since this thread mentioned OEMConfig:

"Datalogic OEMConfig" app is officially released and can now be used on Datalogic Android 8 devices and above.

It is present in the Google Play Store: https://play.google.com/store/apps/details?id=com.datalogic.oemconfig

Great! Thanks for the update, and congrats on the OEMConfig launch!

Dear Seif,

I am fairly new to the Soti Mobicontrol platform. I have a Dxu file that I have managed to send to a Memor 10 in the sdcard\download folder . What I don't know is how I get this DXU to deploy?  i believe this requires some sort of script but I do not know what this is and where it needs to go on the device . Are you able to help here?

The sendintent script is already posted in this thread. Please read through the whole thread.