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 would like to download the latest 14 agent but I can't using the soti.net or other websites suggested earlier. We are on 14.1 and I have tried the newest version 15.1 but there are some bugs I am not comfortable with in the Webconsole (APIs aren't reporting currectly, etc). 2nd question is the easiest upgrade path for the agents either on Soti WebConsole or Honeywell EP (Honeywell devices of course).
Good afternoon, I am wondering if it is possible to upgrade one of my test devices to agent 14.4.7 and how I could go about doing so. I recently downloaded SOTI's newest APKs for SURF and Settings manager. I deployed it to a single test device with a test profile first in order to ensure the app will function properly before deploying to our 600+ devices. I noticed that the Settings Manager app is giving me a message that says "Update agent. You need MobiControl Agent 14.4.7 or higher to use this feature." I would like to update my agent on my test device so i can make sure the apps and remote capabilites funtion properly. we are currently on agent 14.1.4.1010. samsung tab a 2017-2020
Hi, We've got a large number of android enterprise devices enrolled, which is done through the OEM provisioning process (Honeywell). As part of this enrolment, I target a specific AE SOTI agent version to keep the fleet consistent. I'm struggling to understand why there are devices in our fleet that will upgrade their agent version, passed what's been allowed in the console settings. For example, the current 'compatible' local agent version in our console is 14.4.6.1001. The latest version not yet authorised is 14.5.3.1017. All of the device have Agent Upgrade Enabled set to false, yet some of them randomly update to this new version? I'd like to authorise and deploy the agent version in more controlled fashion as we've run into issues with particular agent versions in the past and am reluctant to just let them always install the latest version (at least until it's been tested by us). I don't believe anyone in our environment (administrators) has ever issued the "Start on update schedule" option within the agent update options however couldn't say for certain. If so, how would that setting be counteracted? I've issued the "Disable Agent Upgrade" command which won't go to any devices that have the new version (regardless of whether the console has it marked as compatible) due to it being the latest official released agent (which seems quite strange behaviour to me). Does anyone have any suggestions? Cheers! Rob
I am planning to update a group of Samsung Galaxy Note 10+ phones from Android version 9 to the latest release of Android 11. As part of this I tried performing the update on a test phone. Currently a restriction is configured in SOTI to stop Android updates, so I created a test group for the phone and removed the management profiles. After the profiles were removed the OS update proceeded and all that went fine, however, a message started appearing on the screen saying: "Connection to server failed; SSL handshake failed" which I assumed was coming from the MobiControl app trying to reach the SOTI cloud server. This seems akin to the following discussion: SSL handshake failed but there does not seem to be a clear resolution to this issue. Checking the applications list it seemed I had two versions of MobiControl - the current one and a previous version, likely the one that existed from when the phone was running Android 9. I deleted the older version; however, the newer version could not talk to the server with the Agent Status, within MobiControl, showing "Disconnected." I deleted this version of the app and tried downloading the version from the Play Store but, after entering the Enrollment ID and trying to enrol, the process eventually timed out saying: "Enrollment failed. Please retry or contact your system administrator." I tried using the OEM download from the soti.net/oem page and choosing Samsung ELM, however, once installed I had the same result. I really don't know how to fix this issue as I am new to SOTI and the existing configuration was already in place before I started. Any guidance on how to resolve or troubleshoot this problem would be greatly appreciated! Thanks for your help.
Hello dear Soti Team,We are currently experiencing some problems with some Android 9 (Android Plus) Honeywell CT60s. We noticed that many devices are displayed as offline in the web view. We then noticed that the Mobicontrol Agent can no longer be opened on the devices and that the agent takes up the entire memory space of the device (15GB). The device can therefore no longer be administered.I read in the forum that this could be a bug in the SQL database on the device:https://discussions.soti.net/kb/android-enterprise-and-oem-specific-agents-are-crashing-after-agent-upgrade/Agent 14.3.4.1006 is currently installed on all affected devices.It is possible to copy a new agent via USB and install it over the device. I was able to install the following version: HoneywellMobiControl1442NewGen_1039.However, the problem persists, presumably because the defective and cluttered SQL database is still present in the background.Unfortunately, we have the feature control with "Disable removal of Mobicontrol Agent" active, which is why we are unable to completely remove the agent beforehand.Is there any way we can remove the complete Mobicontrol Agent installation in order to start a fresh installation of the agent? Unfortunately, Mobicontrol is still functional enough to prevent us from uninstalling it.It would be very bad for us if we now have to reinstall devices worldwide. Cheers Maik
This might not make sense. The devices we are going to deploy will not be easily physically accessible once they are out in the field. Is it possible to update the MC agent remotely? If so, how is it done? Since we plan on setting up the devices in Kiosk mode, will I have to unlock them all first before I do an upgrade? Is it necessary to upgrade the agent each time there is a new version?
Hi, there's a problem by enrolling new devices with Android Enterprise and the new client 14.4.1.1064 on a 15.1.0.3416 server. (a server update not possible - Windows Server 2012R2...) No Remote Control: No Enterprise Binding:
Hello, We just upgraded our on prem MobiControl server from 14.1 to 15.2 Under the device actions for each device, I am not seen "Enable Agent Upgrade" when I AM seeing "Disable Agent Upgrade" I have verified that I am in the correct Admin groups and have full control on all device groups What do I need to do to see this device action?
Hello. We have MC 14.4 OnPremise and some Samsung Tab A6 (Android 8.1.0, AE, COBO, afw#mobicontrol) enrollment. For a few days we have realized that all devices have "Agent Outdated (Upgrade Required)" icon.The agents version are between 13.7.5.103 and 14.1.8.111 If we start the agent upgrade from the web page, the warning "Invalid device software version (Device is not allowed to upgrade)" appears. All devices allow remote control, but we can't manage any profile/package (Install/Removal Pending). I can't even remove LockDown. I have a deployment out of control completely. Any idea, please.
Hi SOTI Support team I have some issue when I want to Update Agent in "Manage Android Agents and Plugin" I got error "Failed to send UpdateCompatibility Request" My Client Device is ZEBRA ET50 Android os 5.1 SOTI Agent version 14.x How to fix it and upgarde agent
Hi! We have started seeing a weird behavior on some of our XCover 4s devices. When we do a restartagent or for example an upgrade of the agent when the screen is locked, the agent is stuck on splash screen and won't start until we unlock the screen. Have anyone else seen this problem? I have tried to disable Doze Mode, upgrade to the latest agent. eg. Android+ devices (DA)
Hello everyone! I'm having problems enrolling devices in my MobiControl server, the kind of devices I'm enrolling is: Android Plus. Without Google Account. Models are: Samsung G532M, G532MT, J320M. After they are enrolled to the server, they're agent are not compatible with my actual version of MobiControl, even after I checked the version that has been configured with the device add rule. How can I fix this?
Hi guys, In our environment we are using Soti MobiControl 14.4.2.1307 and updated the Android agent via the global settings and Manage Android Agents and Plugins. We are using the Zebra Android Agent. The last few weeks this was working fine. Now we installed a new deployment server in a DMZ so we got two deployment servers. Now if I try to update the Android agent again, there is always an error message shown in the browser. I want to ask if anyone has an idea why this error occurs. I guess it's ehter a temporarily probem with the Soti Update Servers or the new server in the DMZ isn't able to contact the servers above, so the update keeps failing because of the Firewall settings. Any guesses? Thank you for your help. Stefan
Hello, we work with mobicontrol on version v13.0.3454 with a lot of devices zebra tc75x (android 6) under mobicontrol agent on version 13.3.2.1014 Actually I test a procedure for to upgrade to android 7. I meet some problem about it. Here is it the step I follow for to upgrade: a) download os android 7 to zebra site and copy zip file on device b) start the upgrade by a rule of mobicontrol the result, device is well updated to android 7 but If i do some test -> reset / remote control / reset / and so on .. At a moment, the device can't response ..I reboot device and after the device is broken ! Still rest on main screen with message -> start up android …. and nothing happen ... We have few TC75X under android 7 buy there are several month. The device agent on these device aren't the same Ok i can understand. For to avoid to brake device when I upgrade to android 7, I would like to install the agent I have on android 7 to my android 6 and see the result with my test. My question is how i can install the soti agent with mobicontrol ? I remember it's not recommanded to install the mobicontrol agent by a profile ? thanks for all
Hi Samsung XCover 4 running Android 8. Android Enterprise build Server version 14.1.4.1693 Agent version 13.6.0.x being upgraded via Play Store update to 13.7.2.1015 I've had 3 cases in as many days where people have updated the MobiControl agent via the play store - it's been amongst other updates like Maps so they have updated them all - and it has wiped the configuration settings of another app. The affected app is installed from the Play store via Application Manager but that's the only link between the two. Has anyone ever come across a scenario like this before whre updating the agaentand is there anything that can be done to mitigate against it? This app is about to be rolled out to 2000 devices over the coming months and I don't fancy the idea of dealing with issue on a larger scale.
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
