If the active MDM API's reported on the device agent configuration tab or the device detail tab on your web-console do not include "remote control", you have to send script to make it re-detect remote-control capability.

Use either

1.  _resetfailedrcdetectionflag
     restartagent

   for device agent lower than v13.6

2. retryrcdetection

    for v13.6+ agent

Great, works beautifully!

10 out of 17 of our TC8300 on Android 10 are in 'RC Error" status and can't be remote controlled..I'm dealing with the same garbage with the TC8000 on Android 5.1 - I am really not excited about Android 10 right now and just submitted a case to Soti!

Do you have the Zebra RC Plugin installed in addition to the AE agent? If so and it is still not working then it should work after this script:

retryrcdetection

restartagent

Hello,

I am having the same problem with 40 Zebras TC21, Android 10,  Agent Version 15.0.0.1110. It usually impacts 5 to 7 devices per week.

It says: Supported APIs: RC Error, Work Managed Device, Android Zebra EMDK, Android Plus 1.6

I can temporary heal it by calling retryrcdetection.

As it is Work Managed Device (Device Owner), I use Zebra_Hawkeye_RC_AE_1.6.0.102 plugin. 

Yes, everything works fine after initial enrollment.  1 week alter and devices are in RC Error status, just like the TC8000 devices.

I can send the retryrcdetection and get remote control working again, but WMS Superusers don't have access to do that, and doing that once a week seems like there is a serious problem happening similar to the TC8000 catastrophic failure that is out there.

 1.  _resetfailedrcdetectionflag
     restartagent

   for device agent lower than v13.6

2. retryrcdetection

    for v13.6+ agent

I'm sorry, but this is only a temporary solution. RC error will return soon.

You should not mark this as resolved.