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 am writing some scripts with the help of the SOTI Android Agent JavaScript API Reference. With the help of the examples in the documentation I have always reached my target. Only with the commands "mobicontrol.network.IpAddress" or "mobicontrol.network.Network" I did not be able to read the data. Is there a simple example how this works?Thank you
Within Global Settings / Manage Android Agents and Plugins, we currently have just about every single Android Agent added to our instance (by a previous Administrator). As part of a clean-up exercise, I was looking to reduce this list down to only the ones we require but there is no "Remove" button within these screens. Although having all the agents installed is not detrimental to our instance, its a constant annoyance receiving the Update notification, for agents we will never utilise. Does anybody know of any method to remove/reduce this list? Thanks.
Hello, I was looking for information about the campatibility of (Android Enterprise) device agent with Mobicontrol servers. I can't find this in the release notes of agents or Mobicontrol. Is this information available? Are newer client always fully compatible with older Mobicontrol servers? F.e.: When I using Mobicontrol v15.1 and want to upgrade to v15.3, is it good pratice to first update the agents on my clients, so that after the Mobicontrol upgrade the device are compatible with the server? Regards, Mark
Hi all, Recently I've seen an increase in devices which fail the SafetyNet Attestation failure during enrollment with the Android Enterprise agent. These are brand new devices right out of the box including Samsung SM-T515, Zebra TC26 and Zebra TC57. The Android Enterprise agent is version 14.3.3.1038. The Android version is 8 and 10. I've already maintained the necessary setting in the add device rule to enroll on attestation failure. But why are these devices failing when they are straight out of the box and unmodified? Robert
Hi! The next days we would like to upgrade from MC 14.4.1 to 15.2. We are running some Android devices with MC Agent version 13.7.x. After upgrading: What will happen to these devices? Are they still manageable or are they forced to install a higher version of MC agent? Does anybody know? Thank you!
Trying to enroll some Amazon Fire 7 (2019) tablets into Mobicontrol, however the "Amazon" agents both install but error out afterwords saying they are not compatible. Is there a compatible agent for these devices?
Hi! I got some Elo Touch(Model: Elo-i2-10Val) where it was wanted that I enrolled these into SOTI MobiControl and enrolled some software on them. First of all i tried setting up a rule which included the Elo Touch in the "MobiControl Agent Selection", with this is seems like it don't find an Agent(which is logical for my next observations). Futher I tried a couple of the Agents from https://docs.soti.net/mobicontrolagentdownloads/ and when enrolling with one of these the unit gets enrolled(so it passes the HW-check), but in the Device Groups it appears as "Agent not compatible". Any which have any ideas regarding this? Might it be that it isnt compatible to the server-version? I see that the current server-version running is: 14.2.2.1170 Br. Anders Kvisvik FARA
Hi all I am aware based on 2 previous postings of this issue and noticed that Soti themselves responded saying it would be fixed in a future agent version update, however since then for the above devices (SM-T395) running Android 9.0 when switching between apps whilst in lockdown the apps are being killed when switched meaning the user is logged out and has to start afresh. This is causing issues with some of our apps and our users are growing frustrated and is causing more support calls to us. The last time the issue was reported was back in August with someone asking what the issue was and was there any update to the fix? Can anyone advise when this is going to be fixed as we currently have in excess of 150 people using this model of tablet with this issue that have further issues caused by Soti killing the apps. Any ideas when this will finally be fixed? Agent versions ranging from 14.0 to 14.1 currently on our tablets. Thanks
Hi, I'm currently creating some new 'Add devices rules'. The device which is going to be used here is a device that currently don't have a device agent on server, but is on the https://docs.soti.net/mobicontrolagentdownloads/. How could new agents from this list be added to the server? I want that there should be as few manual steps as possible, and therefore don't want that the user should be needed to manually install the .apk themself. The current version of MobiControl used is: 14.2.2.1170 For me it seems like there was an possibility in v11 (through: https://www.soti.net/mc/help/v11/en/Content/Manager/AgentMgr.htm), and also now a possibility in 14.3(through: https://www.soti.net/mc/help/v14.3/en/console/devices/managing/enrolling/update_device_agent_android.html). In 14.3 we got some problems with some other things, so we don't have the possibility to update the server right now. Thanks in advance! Br. Anders Kvisvik FARA
Hi all, I am still experiencing the problem where Android Enterprise devices (SOTI Agents) are asking for manual agreement of the usage stats permission. This is on all makes and models of smartphones and tablets that I have. (e.g. LG/SONY/Samsung/Zebra) I also use the latest agents and plugins with SOTI v14.3.4 (on-prem). I have with testing found that there are triggers which seem to force the agent to request the permission are; - Various items in a Data Collection Rule - A script / profile using manualblacklist Has anyone found any other triggers or how to automatically approve the permission? The info at https://discussions.soti.net/kb/unable-to-obtain-usage-access-permission-silently-on-android-enterprise does not help unfortunately. I am moving to Zero-Touch and so I need to reduce the complications that end users will have. John.
https://docs.soti.net/mobicontrolagentdownloads/ I'm after 13.4 for testing purposes.
Hi We have a small selection of Samsung Galaxy Tab Active 2 devices that have been upgraded to Android 9 (Pie) (there's another thread asking how I stop the upgrade and that has been resolved). These devices have been enrolled via Android Enterprise and are running agent version 13.7.3.1045 Our servers is on 14.1.4.1693 The devices have Kiosk Mode enabled (it's a legacy thing, don't judge). Can anyone think of a reason why when the user clicks on MobiControl from the kiosk screen it will not open (goes black screen then returns to the kioskscreen). If you administratively remove the kiosk then MobiControl opens as normal when clicked on and the users can access content manager. The app name is set up correctly in the Kiosk Mode settings and works properly on Android 7 and 8.1. All suggestions welcome. Eddie
Hello, We are using MC Server Version 14.2.3.1069 Where can I manage the Andriod Device Agents used in the Add device rule? I need to add a different Agent and cannot find any wrench icon beside Manage Android Agents in the Global Settings tab. (mentioned in the help file) There is no such menu entry for manage agents. Downloaded the agent form Soti Website and need to assign it to add device rule. Using Google Play is not an option, the devices are not allowed to connect to google play store.
When downloading the latest Android OEM agent you get version 13.6.0 Build 1664 (tried downloading a Zebra and Elo OEM agent). But the latest release notes are for 13.6.0 Build 1476. Are there any release notes for 13.6.0 Build 1664?
Hi I want to set up support details for our Service Desk on the Support screen in the MobiControl agent. We did it years ago when we hosted version 9 on Windows CE devices (those were the days), but now on cloud hosted v14.1 I cannot find a setting to do this. Hopefully it's me missing the blindingly obvious. Eddie
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.
