Try using this script in legacy:

Tim,

You can use the legacy script mentioned by Mitchell if you find out that the active MDM API's for the single problematic device are different from those reported for the other 124, namely a remote-control related API is missing.  Your might re-try applying the script more than once on the device until the missing API is reported to be active.

If there is still problem if the remote-control API is already there, then you might need to check if this device has any difference  (e.g. device brand/model, agent and firmware version, MDM policies deployed etc.) from the others for further debugging,  Log files from the device and server may help.

Hello Tim,

Thanks for raising this issue.

Have you gotten a chance to try the script suggestion made by Mitchell? If not, let us know if you are still having difficulties.  

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |