I am trying to deploy a datawedge.db file to a bunch of Zebra devices to update a setting on it. Running into some challenges. Seems like whenever I export the settings from the datawedge app on...
See more...
I am trying to deploy a datawedge.db file to a bunch of Zebra devices to update a setting on it. Running into some challenges. Seems like whenever I export the settings from the datawedge app on a device and move it off the device physically, even if zipping before doing so, the file seems to get corrupt or I can't update the permissions like Soti says to. Whenever I upload the file and try moving it like this it complains about the XML format basically: <wap-provisioningdoc> <characteristic version="10.1" type="FileMgr"> <parm name="FileAction" value="1" /> <characteristic type="file-details"> <parm name="TargetAccessMethod" value="2" /> <parm name="TargetPathAndFileName" value="/enterprise/device/settings/datawedge/autoimport/datawedge.db" /> <parm name="IfDuplicate" value="1" /> <parm name="SourceAccessMethod" value="2" /> <parm name="SourcePathAndFileName" value="/sdcard/datawedge.db" /> </characteristic> </characteristic> </wap-provisioningdoc> This will error even if I take a file on the device and just try to move it with the above. Seems these XML files don't work. have the latest Zebra MX and OEMConfig apps. If I just copy the datawedge.db file to a device and move it to the enterprise folder it complains the file is invalid or corrupt. I'm at a loss how to deal with this. Permissions on a local device working export and one I copied over seem to be the same. Although Soti says to do a chmod 777 on it, which WS1 can't seem to do, the files don't seem to have that permission set for the local working one and the one I uploaded. Any thoughts?