SOTI Pulse Logo

Soti FileSync to Enterprisefolder on Android14

FH
Franko Heckert
EHG Service GmbH (Ernstings family)

Hey Guys,

we are using over 200 Mde Devices Zebra TC22 with Android14, i must change the general Scan Settings via Datawedge and i've create a profil and will export this to all other devices. With Zebra StageNow i got only errors. I try it via Filesync rule from Sotimobicontrol and try to copy the file to the "/enterprise/device/settings/datawedge/autoimport/" path, but i got only a error messages "filesync failed". Has Soti no acces to this folder,i know that we got with android 14 more and more problems with acces to paths. has anyone an idea to get a mass deployment from the datawedge profile to this folder?

Filesync from Zebra StageNow makes an error and the Autoimport StageNow Profil get also an error...

Best Regards Franko

 
29 days ago
SOTI MobiControl
ANSWERS
BI
Bradley Inglesant
29 days ago

Hi Franko,

This is because post Android 10, it's not been possible to access the Scoped Storage remotely from MDM.

Start by importing the DB file onto the device using the file-sync rule (you'll need to import it into the SD Card). You can then use the DataWedge manager option in StageNow to move this into the /enterprise folder.

Here's a link to Zebra's own article explaining how this is done:

https://supportcommunity.zebra.com/s/article/000021417?language=en_US

Thanks,

Bradley

FH
Franko Heckert
29 days ago

Hi Bradley,

thanks for the fast answer, i tried this, but nothing happend. i've got an error with mxconfig. :(

We have a old profile with the same name on the device and i only try to copy the new profile with the same name on the device to change the settings in the existing profile.


B
Benjamin
29 days ago

Have you tried using the package feature instead? 

  1. Deploy the .db file in the same /autoimport/ folder as you mentioned
  2. Deploy the .xml Stagenow file containing the AutoImporting config in /enterprise/usr for instance
  3. Post-Install :
    __chmod 777 "/enterprise/device/settings/datawedge/autoimport/dwprofile_Profile0 (default).db"
    mxconfig "/enterprise/usr/AutoImporting.xml"
     

That works perfectly on our TC27 running Android 14!

Not sure the __chmod is still mandatory, but I kept it as mentionned here : 
https://supportcommunity.zebra.com/s/article/Deploy-DataWedge-for-Android-Configuration-Using-SOTI-MobiControl

FH
Franko Heckert
28 days ago

Hi Benjamin,

thanks for the answer. I tried it but its the same, nothing happend in Datawedge on the device.

I know on the rollout at the beginning of this year it works with the stagenow datawedge autoimport xml on a older Android14 version. But my teammate installed for 3 weeks the newest u180 version and it looks like we get no access anymore with stagenow datawedge, filemgr, packagestuido or filesync from soti to the datawedge path for automatic import. permanently i've got the error massage that he can't copy to this path... or zebra change with datawedge 15.0.40 version in latest update the paths, but i can't found anything in the documentary. :(

MI
Marius Iversen
28 days ago

Hello

I've been strugling with this my self. On the latest Android 14 updates, none of the old methods work anymore. After hours with both Zebra and SOTI support, this is the method we landed on. This works on SOTI MobiControl 2025.0.1. 

 

1.) You have to recreate the DataWedge configuration from scratch on the updated device. Old .db-files did not work for me. I have not tested with single profiles.

2.) Use app policy with Zebra OEMConfig <-- you will find two in Google Play, do not use the one called Legacy - it is obsolete for our purpose

3.) In the Managed App Config for Zebra OEM Config, configure these settings:

a.) File Configuration

b.) Create new file

c.) Device Path And Name should be - /data/tmp/public/datawedge.db

c.) Add Download Option - On Server - SAVE

d.) Download Server URI - %URL-TO-DOWNLOAD-FILE% <-- We're using this function for timing. If you use any other options like file sync, the timing of when the device gets the new file from file sync, and when Zebra OEMConfig actually starts the import is completly random as far as I've seen.

e.) SAVE

f.) UI Configuration - DataWedge Configuration - APIs Configuration

g.) Import of DataWedge Database - Allow

h.) Database File - /data/tmp/public/datawedge.db

i.) Automatic Database Import - Allow

 

In my opinion this is the worst way yet of mass deploying DataWedge config. It feels inspired by Intune.

FH
Franko Heckert
24 days ago

Hi Marius,

thanks for this Troubleshoot, i give it a try. Which Soti Version you are using and what are you mean by Zebra OEMConfig do not use the legacy? 

At the moment we don't use ZebrOEMConfigs.

A
AMMOD@SOTI
27 days ago

Hi @Franko Heckert,

Thanks for posting on SOTI Pulse, Thanks Bradley,Benjamin and Marius for responding to the post, your expertise and willingness to help are greatly appreciated!

Have you had an opportunity to test the suggested solutions by them and has it successfully addressed your query?

If any of these post has helped you in solving your inquiry, I would request you to mark the particular comment as "is solution", so others may benefit from this information.

MI
Marius Iversen
21 days ago

I'm using 2025.0.1, but in theory it will work with all versions og MobiControl with access to configuring Managed Enterprises.

When you search for Zebra OEMConfig in Google Play, you will find two apps. One of them is called Legacy. Do not use this one, it is obsolete for our purpose.

 

Similar Discussions