SOTI Pulse Logo

Zebra ET40 - Worked managed - Unable to Remote Control

Solved
DH
David Hercules
Big 5 Sporting Goods Corporation

We are currently running SOTI V15.0.1.1181 attempting to configure some new Zebra ET40 tablets running Android V11 Build 11-23-29.00-RG-U03-STD-GSE-04. 

  • When attempting to remotely control these devices however I am getting different results depending on the package used.
  • Using no package leads to View-Only access
  • Using the Zebra_Hawkeye_RC_AE_1.6.0.102.pcg leads to remote control access but no visibility on the MobiControl client.

Using the SOTI generic plugin leads to visibility and remote access but end-user has to accept the "Recording or Casting with MobiControl" prompt.

Are there any suggestions on which plugin to use with these devices? The ideal goal is to have these devices be able to be remotely controlled without any user interaction. We do currently have Zebra TC52X devices running android 11 using the Hawkeye package without issue. 

We have also ran the following scripts:

_resetfailedrcdetectionflag
restartagent
enforce_rcaccessibility 1 
 
Thanks in advance!
ET40 et45 zebra SOTI 15.0 Remote Control
a year ago
SOTI MobiControl
ANSWERS
DH
David Hercules
a year ago

Issue resolved by updating SOTI server to 15.6.5.1018. Removed SOTI generic Android package and removed Zebra_Hawkeye_RC_AE_1.6.0.102.pcg. Ran devices with only SOTI application installed and was able to succesfully obtain a remote connection that can be controlled. 

Solution
RC
Raymond Chan Diamond Contributor
a year ago

Compatibility and features of different plug-in various with device models and firmware versions.  That is why administrators have to do thorough tests on their own devices to confirm which one, if any, is the best to be deploy to a particular model firmware-version combination.

Prompt related to "Recording or Casting with MobiControl" is often related to the app permission model for the particular Android firmware version the device is running, and is primarily imposed by the device platform owner (Google in the Android case).    In recent years, hardware vendors and device platform owners tend to be very prudent for issues related to end-user privacy, and allowing the starting of a remote-control session silently is getting more controversial.   I believe there is little chance that this prompt can be disabled.

Finally, even if the correct/test plug-in has been chosen to be deployed to your targeted device,  it is still possible that the device agent cannot get the "Remote Control API" properly set up.  In such case, you still have to send the following script to the device in an attempt to get the "Remote Control API" set up properly:

_resetfailedrcdetectionflag
restartagent
 
V
VPMod@SOTI.net
a year ago

Hi David Hercules,

Thanks for posting on SOTI Pulse.

Thank you, Raymond Chan, for responding to the post, your expertise and willingness to help are greatly appreciated.

We are glad to know that your issue has been resolved. If you have any additional questions or concerns, please don't hesitate to reach out. We're dedicated to providing assistance and support.

Technical Support, SOTI Inc.

Similar Discussions