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.
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?
Hi, does anyone know if Soti supports email profile configuration that requires Azure MFA? On our iOS devices, the native email app works no problem if we configure the email account with MFA manually. But it doesn't work if the email account is configured by Soti. Not sure if it is something on our configuration side or Soti just doesn't support it? Thanks.
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.
Hi there, We are using about 30 Urovo DT50 android devices since 2 weeks. We had experienced excessive cellular data transfer on these devices. According to the Telecom Expense rule the net.soti.mobicontrol.androidwork application cause this traffic. It means, 60% of the overall cellular data traffic is the Agent and other 20% is the com.android.vending application. This is about 1.5-2 GByte per device per week! There's no active file sync rule with so much data. What else can cause so much traffic? How can I identify what cause this? Can it be some automatic application update from managed Google Play, package delivery profile or application catalog rule? (None of the related applications are larger than 30 MB.) MobiControl version: 15.0.2.1049 Device Agent version: 14.4.3.1074 Plugin version: 1.16.5.110 Android version: 9 with Managed Google Play Thanks for your help!
Hi, I needed to add the Honeywell's battery optimizer in the lockdown But as the Battery Optimizer is in the device Settings, I believe it has been blocked I have tried with and without the Suppression option in the advance settings but i still receive an error that "activity not found' Bundle ID : com.honeywell.batterymaximizer/.activities.HomeActivity Is there any option I can fix this? Thank you
Hi, how can I collect information in the " Device Information with Custom Data Report ", or better: if I want to see the value of "SSID", wich string need I write in the field "Enter Custom Data 1:"?
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?
Pretty new to SOTI and I am struggling to find a concise step-by-step, super basic guide for updating the Zebra/Android OS through SOTI Mobicontrol portal. Im running Zebra MC930B Android Scanners that are over a year out of date and having issues.
Hi, I'm trying to install Mobicontrol for testing purposes with a backup from a customer database. I restored the database within the SQL Management Studio, but nevertheless the installation doesn't work as I hoped it would. Any ideas what I'm doing wrong or anything that I'm missing? Thanks, Please see some screenshots of the installation procedure.
We're noticing Chrome is slowly changing and introducing issues to local storage and Indexdb, so we want to lock chrome to a specific version and not allow the users to upgrade change (the little red up arrow, top right) Is this possible? Any help greatly appreciated.
Hi, could someone please help us out trying to configure the 24h clock view on our zebra TC21 devices through soti.Already tried creating a package with stagenow setting the "military time" but when pushing the profile not changes. Then tried to send script to set clock format: writesecuresetting -sys time_12_24 24 where script works, but scanner asks for write permissions so we can't to this silently.... Anyone any ideas on how to set this ? simple an silently ? kind regards !
Hi all. We recently started using TC21 Android version 10 (Build 10-16-10-.00-QG-U16-STD-HEL-04). Users noticed that when they are signed into and app, press the home button, open a different app, press the home button, and re-open the original app, it logs them out of the app. It seems that the EHS is not keeping the app open in the background. We are using EHS_040005. I loaded an older version of EHS (EHS_030104_B) and its still happening on the TC21. We primarily use the TC72s and these devices do not have that issue. My test device is running Android 8 (Build 01-30-04.00-OG-U00-STD) Anyone else having this issue or seen this issue?
After upgrade, the MC console to 15.3.0.6713 The agents status is showing connected, waiting for server response and for new enrolling the devices it giving an error Enrollment failed, please retry or contact your system administrator. This issue has happened to the entire production device. Once we disable the file sync rule all the agents are back to normal(agent status-connected) and we are able to Enroll new devices. In our environment, the File Sync rule is used to run the script (enabling the Default application in AE devices).
and also Error sending message (Error sending message (type=22), General communication error) error sending message (error sending message (type=80) general communication error)
hi everyone, so recently i enrolled about 80 Samsung A01 devices, and my client push 1 application to the device. The apps is hybrid, and the user of the devices sometimes face blank screen when open the apps. The apps maker ask if SOTI interrupt the process of the apps. Told him already that SOTI has nothing to do with the apps. We tried on 1 devices that not enrolled to SOTI and the issue still happened (blank screen). We (me and my end user) suggest the apps maker to create a mechinism to kill the apps if the apps idle for 1 hour. We suspect that might be the issue. Just wanna ask anyone here experience something like this when do enrollment with SOTI ? I am sure SOTI won't interrupt any apps, but i feels like to share this here in case anyone experienced same kind of issue during SOTI enrollment. Thanks & regards, Randy
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.
