No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Hello everyone, My Samsung A01 device was running in Android 10, but since there is update, now is running in Android 11, and after update i found out RC become Remote View only. Is there anyone have same experience here? Is it supposed to running Remote View only in Android 11 ? Thanks & regards, Randy Saputra
Hi everyone, Recently I enrolled around 90 Samsung A01 devices for 1 of my client. I enrolled it using AE through Zero Touch portal. My Mobicontrol version is 15.3.0.6711 After enrollment i found out 1 device can't do Remote Control. The API that showed only Remote View. It's weird because the rest of the device all can do Remote Control. Anyone experienced this before? Maybe someone has suggestion to my issue.. Thanks & regards, Randy Saputra
Hi, I'm having trouble doing the remote control, the remote control is stuck as shown.but when we use the plugin version remote control, the remote control runs smoothly. we use soti mobicontrol 15.0.1.1181
Hello community, i have the following issue, that the remote control will not show the scanner with Soti Assits (Web based). With the plugin it works.It is only one scanner who has that issue. The scanner is in the same network. Also a Factory reset did not help. Does some know how to fix the issue? Modell: Zebra MC93OS Version: Oreo 8.1.0Agent Version: 14.5.0.1011Remote Control Version: 1.18.2.100
We use the same tablet in all vehicles, Samsung Tab A. When we install SOTI they all have the Remote option, but over time some tablets no longer show the Remote option. Is there a way to add that back over the system without having the tablet in hand?
I am having an issue whenever I try to enroll my pi into mobicontrol it downloads the agent through MC url, but the device only downloads the agent version 15.0.2 536, which does not have the functionality of RC. Also, when I download the agent through rule it downloads the lastest Linux agent. It does not make sense to me why it downloads the old version of the MC agent when the server have the new version of the MC. When we try to upgrade the agent it gives an error "attempt failed"We are currently on MobiControl server version 15.1.2.1035. Anyone face the same issue?
We have a few Android 10 devices (Motorola Moto G8 Power) and trying to use the Remote View resulted in the device displaying an "Exposing sensitive info during casting/recording... Cancel/Start now" confirmation dialog which is a new feature in Android 10 as discussed on Google support forum: https://support.google.com/android/thread/13791498?hl=en We've found a workaround by applying an ADB command via USB debugging, found e.g. on Stackoverflow: https://stackoverflow.com/questions/63039084/android-stop-permission-promt-for-screen-recording For MobiControl it's: adb shell appops set net.soti.mobicontrol.androidwork PROJECT_MEDIA allow I'd be happy to hear about more elegant solutions than enabling Developer more and USB Debugging on each device and applying this manually device by device. I haven't installed any device specific plug-ins. (As found at https://docs.soti.net/mobicontrolagentdownloads/) I see there's a "Lenovo ARM" one which probably would be the right one. The devices are in Android Enterprise mode and will run a kiosk mode once delivered to end users.
Mobicontrol Cloud v. 14.3.2.1171 Samsung Galaxy Tab S4 Android 10 enrolled in Android Enterprise Agent version 14.4.6.1001 When I connect to a device remotely, via Web or Legacy remote control, mouse clicks register above the actual location where I am clicking. For example, in Settings if I click the topmost menu item, Connections, nothing happens but if I click the fourth one down, Display, the Connections menu will open. If I click the 6th item, Lock Screen, the second menu, Sounds and vibration will open. Some time ago there was a remote control issue on Samsung devices where SOTI support had us manually change the x,y resolution due to weird stretching aspect ration stuff but now the image in remote is fine but the x,y placement of the cursor on-screen in the rmeote window is not matching the correct coordinates on the device. Any ideas?
Bear with me on this one.... I am having issues connecting to certain Samsung Devices that are at a specific Agent Version or above; First issue is that the Remote Access icon has changed on some of these from "Remote Control" to "Remote View" Agent Version 14.4.3.1074 Model SM-T515 - Has Remote Control - Allows connection Agent Version 14.4.5.1033 Model SM-T835 - Has Remote View - Does not allow connection Agent Version 14.4.4.1051 Model SM-T515 - Has Remote Control - Allows connection Agent Version 14.4.3.1074 Model SM-T835 - Has Remote View - Does not allow connection Agent Version 14.3.3.1038 Model SM-T835 - Has Remote Control - Allows connection Agent Version 14.4.1.1064 Model SM-T835 - Has Remote View - Does not allow connection All have Android Version 10 My question is why do they T835s that are at a higher Agent Version of 14.3.3.1038 (seemingly at 14.4...onwards) have "Remote View" icon which doesn't work, and how do I change it back to the "Remote Control" icon that works. I have been speaking to Soti Support but they are not sure and I need this fixing to remotely support users!
I'm having trouble getting the web-based remote control working on MobiControl Whenever you try to connect with HTML, the navigator goes to the login page of the WebConsole. If I try to login, the cicle keeps spinning but it never logs or shows an error. I have installed SOTI Assist version 3.0 and am running MobiControl 15.2 I have checked the following in this file <SA Install folder>/Server/Config/RestAPI.config --> MobiControl Rest API URL and it matches my FQDN I have checked the "SOTI assist server" URL in the Global settings of my web console and it matches my FQDN as well Any suggestions on what to try next?
Dear Community! Please help me. I'd like to enroll a Zebra MC3300, but "Enrollment failed". Parameters: Android 8.1 - Build number: 02-32-04-.00-OG-U001-STD SOTI Android Enterprise Agent: GoogleMobiControl1444_1051 VERY IMPORTANT: the Remote Control feature is necessary!!! I have no idea how can I manage the correct enrollment, earlier I had some success enrollment with this MC3300 device but only with Work Profile, only Remote View feature. Thanks in advance. Regards: SN
Hi all, We have a number of Zebra TC21 devices on a version 15 SOTI cloud all on same agent (14.4.4.1051). I have some devices that don't have the Remote Control. Even though these are the same devices, same build version etc. and the enrolment rule(s) are the same other than the device name and deployment target folders. Some have APIs: * RC Virtual Display, Work Managed Device, Android Zebra EMDK, Android Plus 1.6 * Zebra RC, Work Managed Device, Android Zebra EMDK * Remote View, Work Profile Any ideas why the differences, would have thought they would all have the same supported APIs, and therefore all have remote control. Thanks for any pointer. Gary
Hi, A client of ours is having problems with MobiControl, they have a few new Zebra TC26 (I think) with Android 10 installed. He was able to control them remotely without any problem, but suddenly the Remote Control button is no longer visible for those devices. Note that the MDM plugin is installed and is a part of the profile on the devices. Regards, Daníel
Hi everybody, I have two Zebra MC3300 (one the two is a long range one) enrolled to a SOTI Mobicontrol console version 15.2. Both the two devices have Android Oreo with latest LifeGuards released. I am observing a very strange behavior when I remote control the devices. In case the device is not used for a while (actually impossible to determine how much time) I am no longer able to use the bottom of the device display remotely, like for example, it's not possible to use the back button or to swipe up the bottom task to display the back button. I have enrolled the devices with StageNow by using GoogleMobiControl1443_1074.apk and I added the MDMPlugin_Notification package (with Zebra_Hawkeye_RC_AE_1.6.0.102.pcg file) in the profile linked to the enrollment rule. Did anybody of you see the same behavior or have any idea on how to fix this? Thanks a lot for your help! Have you all a great day.
Hi, The option to remote control via HTML5 has disappeared from the menu. Has anyone else noticed this? We have to use this more than the plug-in route due to our corporate network settings. We're using MobiControl v13.4. The option was there yesterday.
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points.
Highly experienced members with valuable inputs. Should have more than 700 points.
Beginners taking the initiative. Should have more than 500 points.
New contributors starting their journey. Should have more than 250 points.