Agent for Zebra TC20?
I have had success on the TC51 and VC80x running N with version 188.8.131.528 of the Zebra agent. I haven't tested a TC20 specifically but the the other two Zebra Android N devices didn't work properly in DA mode until I upgraded them to that version.
TC2x is managed through Android Enterprise. You need to select Android Enterprise and Zebra Hawkeye SOTI MDM plugin on Soti’s web page.
Thank you for your reply!
MDM plugin doesn't works, mobicontrol log said: "invalid platform"
What are the differences between the Zebra Legacy and Zebra Hawkeye Android Enterprise Agents? Is Hawkeye explicitly for the TC20/TC25 (given the code name)? Can the TC20/TC25 ONLY be managed as Android Enterprise? If so, is that a result of the limited MX support on that value tier device or some other reason?
It looks like that you enrolled the device in PO mode and not in DO mode. Please enroll the device in DO mode and test the plugin again. I dont have any issues with this plugin on TC20/TC25 and remote control works fine for me.
thank you for your reply.
I've enrolled my device in DO mode but now all pre - installed applications (including enterprise apps) have been deleted! and remote control works but file system explorer during remote control doesn't! I can use remote control with MDM plugin but I should install enterprise apps such as: datawedge (very important), stage now and others.
So, my question is: doesn't exists an agent like TC70 agent?
We talk about an enterprise device not a consumer one.
Thank you for your time,
I am aware that file system explorer during remote control doesnt work on TC20/TC25. There is opened case with SOTI support for this.
There is no signed agent for TC20/TC25 as for other devices like TC70...etc.
If I enroll my device in DO mode then all apps are still installed on the device. We need to know how you enrolled the device onto SOTI. Heve you used StageNow to enroll the device onto SOTI (DO mode)?
Check out this other recent thread regarding DataWedge (a system app) disappearing off of another Zebra Android device:
It appears that you should be able to re-enable it by sending the following script to the devices:
it seems to works, I tried with Chrome...I will try with datawedge.