Hi Shane,

I am well aware of your numerous requests to me for some input to your discussion threads related to Zebra devices.  Unfortunately, I have very limited access to Zebra devices for my hands-on cases in my region over the years.  In particular,  I haven't touched a single Zebra MC3300x before.  Hence,  I would rather let others, especially my friend Matt Dermody, to answer you.  Matt is an expert on Zebra device platform, and is very active and responsive in this forum.  So, hopefully you might be able to hear from him within the next few hours.  I will be happy to respond to your request in the future if I can get hold of sufficient Zebra devices to play with for some time.

Hello Shane.

We solved it via Stage Now and sent this:

<wap-provisioningdoc>
  <characteristic version="9.2" type="DataWedgeMgr">
    <parm name="AutoImporting" value="1" />
  </characteristic>
</wap-provisioningdoc>

To be on the safe side I also copied the file to autoimportfolder via StageNow:

<wap-provisioningdoc>
  <characteristic version="0.6" 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="SourceAccessMethod" value="2" />
      <parm name="SourcePathAndFileName" value="/sdcard/datawedge.db" />
    </characteristic>
  </characteristic>
</wap-provisioningdoc>

Mobicontrol script:

mxconfig /sdcard/Copy_Datawedge.xml
__chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db
mxconfig /sdcard/Enable_autoimport.xml

BR
Pelle

I do not typically have to use StageNow MX for the DataWedge *.db processing.

For AE devices like the MC3300x create a Package with your *.db and deliver it to the autoimport directory (/enterprise/device/settings/datawedge/autoimport/) then include the chmod post install script in the Package itself and the .db will be read in automatically.

Also, if you don't use the chmod script the autoimport typically works after a reboot anyway. 

In our environment Android 8.1.0 AEDO worked perfect. But when we tried to use the same script and package with Android 10 it stopped working. Enable DW autoimport was probably the solution. We changed all above and now it works.

Hi Shane,

Thank you for requesting an answer on your post.

As Matt has mentioned, this can typically be resolved with the use of the below post-install script within the Package configuration:

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

If you able to resolve this issue with any of the suggestions from the other posts on this thread, kindly mark the appropriate comment as 'Solution' to help others find the answer.

Kind regards,

Hello Shane,

I'm going to hijack your thread a bit.
Our IT has been trying to integrate a MC33X into Mobicontrol (version: 14.5.4.1035 ) for some time.
Unfortunately, they report a wide variety of problems.
Certificates are not distributed properly. After the agent installation the devices can not be managed, etc.

So far they havent managed to add one working device yet.

Did you have any problems with the integration of the MC33X or did you find out that it finally worked for you, or did your device integrate just like other devices in the past (e.g. the MC33 does not cause any problems).

Would be very happy for an answer

Hello Maik.

A new thread would be better.

But do You have SHA-2 certificates on Your deployment server? We are running old Win Mobile clients and they don't support that so we had to set up a new parallell deployment server before we could add any Android 10 clients. Up until Android 9 SHA-1 was working fine. If You´re not running Win Mobile clients You can change certificate. Not sure if You have to do this with Soti help. You are changing certs on live units, so if You loose them...