Alternate solution to provide read, write, execute to file in AE.

Alternate solution to provide read, write, execute to file in AE.

Hello Everyone,
My customer has Zebra TC52 devices running Oreo, enrolled as AEDO. They push a datawedge.db file to their devices, and they seem to be having some permission issues. In the past, using an OEM signed agent, they were able to use the execute_shell chmod 777 script to grant read, write and execute permissions when they copied that file over to the device. With AE, that script is no longer supported. They have noticed two things: 
1: If the file is pushed through adb, all the permissions are granted and the datawedge app consumes the db file. This is not a viable solution.
2: When they create a package to push that file, the datawedge app does not pick the file up, unless they reboot the device. They however would not want to reboot their devices. 
What is a good solution for them, is there anything else we can use to grant read, write and execute permissions to that file within AE? 

3 Answers

Order By:   Standard | Newest | Votes
Matt Dermody | posted this 14 April 2020

Good call! I have also moved to the __chmod 777 script for the AEDO device deployments and it works perfectly. DataWedge configures itself without a reboot. 

  • 1
  • 0
John Doe | posted this 14 April 2020

I know its a really old post but i stumbled across this one while doing research on autoimport too (wasnt working for me).

You can use the following script as post-install and the procedure should work without reboot:

__chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db


"__" is important


Just to help others looking for a solution :)

Kind Regards John

  • 0
  • 0
Matt Dermody | posted this 08 February 2019

The device doesn't have to be completely rebooted, only DataWedge needs to be relaunched, which the reboot is effectively doing. What if you were to script a kill of DataWedge then relaunch it and then call a different application like the SOTI Lockdown to the foreground so that you hide DataWedge again?

With that said, I tried looking for an elegant solution to this problem in the past before I realized that a required reboot is really not that bad. I typically just have the end users reboot or script a reboot. I'd almost rather that be the case so that you can ensure that the device is not in use while the DataWedge changes are being applied. Otherwise if you were to successfully push the .db into the autoimport directory with the correct permissions I feel like there'd be a chance for the DataWedge configuration to change on an end user while in use. 

  • 0
  • 0

Give us your feedback
Give us your feedback