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.
I have set up some users as Technicians who have limited access to console functions but one area they have always had is Remote Control of all our devices (for support and for training remotely) Now I am being told that these users no longer have Remote Control, only Remote View. I have ruled out the device-- Admin users can control all devices, Techicians cannot control any...all they have is Remote View. All devices are Samsung Tab S4, Android 10, Work Managed, all enrolled using same enrollment rule, all devices in the same folder. Mobicontrol Cloud 15.5 I don't want to have to elevate these users to Admins, all I want to do is grant just those permissions needed to grant Remote Control access-- any advice?Thanks, Matt
Hi, i have a strange problem. When i start the remote control session on a Samsung Galaxy XCover 5 with Android 13.0.0. I can´t turn on the display by clicking on the power button. Installed is Soti Version 15.6.1 1048
Good afternoon, as stated in the object, I have a PC with Windows 10 on which the remote desktop doesn't work most of the times. I always need to reboot it and only then the remote desktop works, but after a while (like the day after) it doesn't work anymore and needs another reboot. I have several PCs of the same model and same OS installed on that plant, but this one is the only one with this issue. What can I try to fix this? Below some information: MobiControl instance version: 15.6.1.1048 Agent version: 15.6.1.143 Find below the screenshots about the PCs OS version and software: The PC is enrolled with SOTI self-signed certificate: And we do not use te Windows Notification Services (WNS). I know this adds a slower application of configurations and applications, but this is not an issue. Plus, as I said above, this is the only PC with this issue (all the others, which work fine, are enrolled in the same way). The PC is connected to the network with a static IP configuration through Wi-Fi connection. It never disconnects from the console (the icon is always green and I don't see any disconnection from the logs), but the remote control is very problematic as stated above. Thank you, best regards.
Almost every time i have to remote control an Android device, i have to run the "activate remote icon" first.Isn't there some way to activate it once for all? :)
Hey all, I am Having an issue with Remote Control On android Enterprise. I am using samsung SM-T307U Tablets. The agent version is 15.3.3.1069. The tablets are on android 11, I have reverted a few to go back to android 10 and same issue. The device do not respond to input on the bottom half of the screen in remote control. If i rotate the screen in remote control, I can interact with the bottom half I was unable to before. The device are on the newest security update.
Hey All, I have tried to enroll Several Samsung A14's because our verizon rep said they cannot sell A13's anymore. When you try to download the mobi control OEM Specific plugin for samsung it says it is not compatible with this device. So I created an enterprise enrollment policy and enrolled it with the AFW#mobicontrol and our enrollment ID. Which does enroll it as a work managed device. However, it does not prompt for knox activation and the MDM API listed is not samsung knox and only shows Remote view. The Release notes show that Enterprise and Classic android are supported for android 13. Is the A14 simply not supported yet?
Hi Community, I have a on premise server with 14.1.8 and my devices have the agent version 14.1.6.We want to use the remote control via plugin. We are using MC92 with WinCE. In the past it worked without any issues. Now if we want to use it the process starts but the remote control don´t appear. You can see the process in the task manager. I already tried:- closing the process in task manager but then I am asked to install the plugin again. - to do a new installation. - to start the process out of the folder C:\Users\*servername*\AppData\Local\Apps\SOTI Remote Control- I also tried to install it into C:\Users\*servername*\ProgramFiles\SOTI Remote Control Do you have any other ideas what I can do? We don´t have SOTI Assist installed on this server. Thanks for your help!
When remoting onto Android 11 devices (Samsung Tablets and Zebra MC930B scanners) I am unable to use my physical PC keyboard to input in text boxes. I can use my mouse to control the touch keyboard on the device but this is a pain. This function was working before our console was updated to version 15.4.3.1012 All devices are running the latest agent/plugin versions Any idea how to get this function back?
HelloWe have new zebra TC26 devices running android 11 with mobicontrol 15.3.3.1065 agent 15.1.3.1071. We are having issue with remote control of the devices. If device lockscreen is active RC is view only. After user unlocks screen we can access .devices.with RC. added screenshot of the screen.
Hello, i have a tricky weird problem. We are managing interactive whiteboards who are running android os. The android os doesnot fully support the android enterprise management. Thats why we forced the installationof the enterprise agent via adb on the device. We set the device owner for the agent andafter that we were able to enroll the device into mobicontrol. So far so good. The downsideof this method was that we could only remote view the device and not remote control. Thanks to the MobiControl 15.0.1 agent udpate we were able to enable the remote controlsupport for those devices. See here: https://discussions.soti.net/articles/remote-control-support-on-android-enterprise-without-requiring-oem-specific-capabilities-or-oem-specific-plugin Now comes the weird part. After giving the permissions in the Accessibility i am able to remote control the device. But after restarting the device i have to give the permission again. I thought first it is because i am trying to manage an unsupported device. But afterfew restarts the prompt for giving access disappears. I can remote control my device rightaway. I checked the logs and i noticed a log that says "Custom log (Accessibility permission hasbeen granted)". This log is shown every time i restarted my device. When it is not shown theni have to give the permission manually. And that makes sense for me. That means mobicontrolis able to set the permission remotely but somehow not always. It is also hard to reproduce thisweird behavior. MobiControl is giving him self the following permissions: Observe your actionsRecieve notifications when you are interacting with an app Retrieve window contentInspect the content of a window you are interacting with Perform gesturesCan tap, swipe, pinch, and perform other gestures So i know i can set permissions with the command afw_set_permission_grant_state but i haveno experience with that command. I tried to find anything useful in the android enterprisedocumentary but i think i could not find anything useful. Does someone know how the command has to look like? I am pretty sure it is possible ormaybe with another command because MobiControl is sending a command to set those permissions after each restart. The device is running the agent version 15.1.3 and am using MC version 15.4.2. The device is a no name brand and is running android 8 with no google services. I hope someone has a clue! Thanks!
Hi everyone, So recenty i am dealing with this issue when doing RC on my devices. Below is the screen shoot : I checked device log and clearly there is no other user start the RC session. Anyone experienced this issue too ? The message above told us to hold down CTRL key to terminate other session, but they method doesn't solve the issue. Most of the time i just restart the RC session until the RC started. Hope anyone can take a look and hopefully have a solution for this. Thanks, Randy Saputra
This issue is similar to https://discussions.soti.net/discussions/zebra-tc21-devices-not-responsive-when-remotely-controlled but the provided solution did not work for me. I reference this link in my text below. I encountered the same issue with my TC26:s recently (essentially the same device as TC21, but with WLAN). The remote screen is black, showing a digital clock and a lock. Sending notify kiosk off did disable the kiosk, but the remote control session did not show this - still black screen. While I did have issues with plugins, the mentioned scripts did not help. At first I was unable to start remote control at all. Web version was only white, legacy version said "Waiting for device" or similar. I had the plugin "RC Virtual Display" and no matter what I did it stayed like this. I had to assign the mentioned plugin to a profile, UNASSIGN IT, and then it worked - now I got "Zebra RC" plugin and remote session started working. However, I now face the black screen issue. To bypass the black screen I have to change the zoom level to Fit Screen, then send the Device Menu action from the RC interface. Now the screen is unlocked and I can view it as expected. Any ideas on how to fix this permanently? Other devices do not have this issue, only my TC26:s. Agent 15.1.2.1075RC Version 1.20.0.100Latest system updates from ZebraSupported APIs "Zebra RC, Work Managed Device, Android Zebra EMDK"Enrolled as COBO, with Managed Google Play
Hello, since AE Agent 15.0.1 there should be Remote Control on all Andeoid 7+ devices. https://docs.soti.net/soti-mobicontrol/android-agent/release-notes/150/android-enterprise-agent-maintenance-releases/ How to enable this ? As on a Pixel 6 with Android 12 enrolled AEDO with Agent 15.1.1 there is just Remote View possible. Martin
Hello, I'm testing out Android 11 on the Zebra MC9300 and I'm unable to see the folders under sdcard\Android\data when using the remote control tool. I have verified the MobiControl application has all the permissions enabled. Any ideas on what I can try? Agent Version: 15.1.0 Build 1045 Active MDM API: Zebra EMDK, Android Plus 1.6, Work Managed Device, RC+ (1.19.0.100) MobiControl Version: 15.3 Thanks, John
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.
