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.
After Upgrading to Agent-Version 15.1.5 Build 1049 all devices show system message "Update google play services" (Mobicontrol is only executed when updating Google Play Services) (freely translated from german message). We think there is no chance to skip the update because the message apears periodically. So we want to know if there is a chance to perform the update of Google Play Services automatically. The devices (>900) are enrolled as device Family "Android Plus" and are currently not assigned to a Google account. Thank you in advance.
Hi! I know it has been discussed before but with how fast they add features in android, I was wondering if there is already the possibility of changing this name through a script or something similar
Hello, We have some devices that were originally enrolled using an enrollment rule that did not have Managed Google Play enabled. Is there a way to enable this without having to unenroll each device and reenroll?
I read another thread that indicated there is no script to automatically log users out of shared device mode after a period of inactivity. This should be in a future release, but is not yet available. As an alternate solution, we have planned downtime with the units and I would like to schedule an auto-log-off event. Is there a way to schedule this log-out event? (e.g., 1900 every day?)
Hi. We're moving from windows mobile to android. I created the default enrollment profile and have connected the TC52 Android 8.1 to it successfully. When I try to enroll a TC52 Android 10 devices it fails. I can see it in MobiControl webconsole logs that shows it being added. Any idea what is different for enrollment for a version 8.1 vs 10 ?
We've been able to deploy our iOS App to App Store Connect but the process is very strict and we fear that it will be a mess when we will have to fix some bugs. When I'm using XCode, I see it is possible to choose Entreprise as a method of distribution : If I understand it correctly, the users can download directly the IPA file stored somewhere on a server with this method,. I'm wondering if SOTI is able to download that IPA file and deploy it on our devices using this method ? I ask because in the SOTI documentations, I've found this : https://soti.net/mc/help/v14.1/en/console/data/sotihub/hub_deploy_app_packages.html Where I can read that : Note: This procedure is only applicable to Android (4.1+) devices. While the SOTI Hub app is available on iOS devices, Apple's security restrictions prevent SOTI from providing an .ipa file outside of the Apple App Store. So, is it possible to find an easier solution than uploading the app to App Store Connect ?
Does anyone has experience with rolling out Macs via Soti? We managed most things, i think but we have some programs not deployed via app store which need a installation script. There's no way like on android to create a package and deploy it to MAC devices, so does anyone knows a possibility to do so?
Hello all, We have migrate to mobicontrol v14.3 to version 15.5.1 there some days all seems to be good ... But, yesturday for one ticket help desk we need to find a device (localisation) enroll into android + (zebra tc75x device android 7). We try to modify the rule and applies to the device ..but every time we receive server error on admin console ! And when i go to the server utility and try to read the log now i have application not found.. Any one have idea about how to read log ? log is normally place on c program data soti perhpas it's just a problem about the path .. Before to migrate it was possible to read the log. For the rule of location, if you have some idea don't hesitate .. thanks for all christophe
Hi everyone , Running on a strange issue right now. Maybe it's happening for a while...not sure, as Support Team only reported this one to me earlier this week. We Work on Mobicontrol 15.5.1.1010 Using Memor 10 Problem is here, it seems that périodically some of them just keep Connecting / Disconnecting every minute ...and this can keep going for hours... I've tried to retrieve some log from logcat , the only thing that seems redundant is this part of the log. 06-16 08:45:16.156 E/DevicePolicyManager( 977): Not holding DPMS lock.06-16 08:45:16.156 E/DevicePolicyManager( 977): android.util.Log$TerribleFailure: Not holding DPMS lock.06-16 08:45:16.156 E/DevicePolicyManager( 977): at android.util.Log.wtf(Log.java:299)06-16 08:45:16.156 E/DevicePolicyManager( 977): at android.util.Slog.wtfStack(Slog.java:98)06-16 08:45:16.156 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.ensureLocked(DevicePolicyManagerService.java:528)06-16 08:45:16.156 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.getActiveAdminForCallerLocked(DevicePolicyManagerService.java:2612)06-16 08:45:16.156 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.setTime(DevicePolicyManagerService.java:10086)06-16 08:45:16.156 E/DevicePolicyManager( 977): at android.app.admin.IDevicePolicyManager$Stub.onTransact(IDevicePolicyManager.java:2526)06-16 08:45:16.156 E/DevicePolicyManager( 977): at android.os.Binder.execTransact(Binder.java:731)06-16 08:45:16.157 E/DevicePolicyManager( 977): Not holding DPMS lock.06-16 08:45:16.157 E/DevicePolicyManager( 977): android.util.Log$TerribleFailure: Not holding DPMS lock.06-16 08:45:16.157 E/DevicePolicyManager( 977): at android.util.Log.wtf(Log.java:299)06-16 08:45:16.157 E/DevicePolicyManager( 977): at android.util.Slog.wtfStack(Slog.java:98)06-16 08:45:16.157 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.ensureLocked(DevicePolicyManagerService.java:528)06-16 08:45:16.157 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.getActiveAdminWithPolicyForUidLocked(DevicePolicyManagerService.java:2677)06-16 08:45:16.157 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.getActiveAdminForCallerLocked(DevicePolicyManagerService.java:2615)06-16 08:45:16.157 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.setTime(DevicePolicyManagerService.java:10086)06-16 08:45:16.157 E/DevicePolicyManager( 977): at android.app.admin.IDevicePolicyManager$Stub.onTransact(IDevicePolicyManager.java:2526)06-16 08:45:16.157 E/DevicePolicyManager( 977): at android.os.Binder.execTransact(Binder.java:731)06-16 08:45:16.158 E/DevicePolicyManager( 977): Not holding DPMS lock.06-16 08:45:16.158 E/DevicePolicyManager( 977): android.util.Log$TerribleFailure: Not holding DPMS lock.06-16 08:45:16.158 E/DevicePolicyManager( 977): at android.util.Log.wtf(Log.java:299)06-16 08:45:16.158 E/DevicePolicyManager( 977): at android.util.Slog.wtfStack(Slog.java:98)06-16 08:45:16.158 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.ensureLocked(DevicePolicyManagerService.java:528)06-16 08:45:16.158 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.isActiveAdminWithPolicyForUserLocked(DevicePolicyManagerService.java:2707)06-16 08:45:16.158 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.getActiveAdminWithPolicyForUidLocked(DevicePolicyManagerService.java:2689)06-16 08:45:16.158 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.getActiveAdminForCallerLocked(DevicePolicyManagerService.java:2615)06-16 08:45:16.158 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.setTime(DevicePolicyManagerService.java:10086)06-16 08:45:16.158 E/DevicePolicyManager( 977): at android.app.admin.IDevicePolicyManager$Stub.onTransact(IDevicePolicyManager.java:2526)06-16 08:45:16.158 E/DevicePolicyManager( 977): at android.os.Binder.execTransact(Binder.java:731)06-16 08:45:16.258 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:45:16.283 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:45:16.284 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:45:16.290 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:45:16.290 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:45:16.291 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:45:16.292 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:45:16.293 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:45:16.301 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:45:16.302 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:45:17.375 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.SIG_STR flg=0x10 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver06-16 08:45:42.967 I/chatty ( 977): uid=1000(system) ActivityManager identical 5 lines06-16 08:45:48.093 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.SIG_STR flg=0x10 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver06-16 08:45:50.400 E/storaged( 573): getDiskStats failed with result NOT_SUPPORTED and size 006-16 08:45:53.214 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.SIG_STR flg=0x10 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver06-16 08:46:03.456 I/chatty ( 977): uid=1000(system) ActivityManager identical 2 lines06-16 08:46:08.576 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.SIG_STR flg=0x10 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver06-16 08:46:12.973 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:46:12.999 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:46:13.000 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:46:13.000 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:46:13.004 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:46:13.005 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:46:13.005 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:46:13.005 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:46:13.005 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver06-16 08:46:13.006 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver06-16 08:46:13.289 W/BroadcastQueue( 977): Background execution not allowed: receiving Intent { act=android.intent.action.SIG_STR flg=0x10 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver06-16 08:46:13.343 E/DevicePolicyManager( 977): Not holding DPMS lock.06-16 08:46:13.343 E/DevicePolicyManager( 977): android.util.Log$TerribleFailure: Not holding DPMS lock.06-16 08:46:13.343 E/DevicePolicyManager( 977): at android.util.Log.wtf(Log.java:299)06-16 08:46:13.343 E/DevicePolicyManager( 977): at android.util.Slog.wtfStack(Slog.java:98)06-16 08:46:13.343 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.ensureLocked(DevicePolicyManagerService.java:528)06-16 08:46:13.343 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.getActiveAdminForCallerLocked(DevicePolicyManagerService.java:2612)06-16 08:46:13.343 E/DevicePolicyManager( 977): at com.android.server.devicepolicy.DevicePolicyManagerService.setTimeZone(DevicePolicyManagerService.java:10098)06-16 08:46:13.343 E/DevicePolicyManager( 977): at android.app.admin.IDevicePolicyManager$Stub.onTransact(IDevicePolicyManager.java:2543)06-16 08:46:13.343 E/DevicePolicyManager( 977): at android.os.Binder.execTransact(Binder.java:731) But for some reasons...if i make to get a remote control on the device, it's stop connect / Disconnect problem for few time. Did thought it have something to do with a sleep mode or so, but none of that is activated ? and as all our devices share the same config, it would impact everyone at the ame time (no one works on night) But basically i had only a bunch that triggered the alert this night for example.. ?! Any adivce would be greatly appreciated. Thanks in advance ,
Hello, We are trying to ensure our Zebra TC56's can not be factory reset. If I add the SOTI factory reset protection to a device, and then do a reset I can easily get around the prompt by scanning a barcode to skip the google setup. So this seems pretty pointless. Is there any other way to lock this down in SOTI? I've seen some MDM's display a constant pop up and force shut down even after a factory reset. Thanks!
Good morning, I have a client using Android tablets with warehouse management system. We are running into an issue where the file sizes of the images are much too large. I believe it is not possible to change the default camera settings with MobiControl, but does anyone know of a third-party camera app for Android that would do this? Even if we had to push down a config file via StageNow, that beats manually changing the settings on 30+ devices every time there is an update... Thanks in advance for any suggestions. Jeff
Basic question After the installation of SOTI Agent (DO) When deviuce show sthe agent and requires the Enrollment ID Is there any method to stop enrollment process if the enrollment failed ? eg due to Firewal blocking 5494/5495 or 443 ports ? what I mean is : is it possible to fully stop the enrollment process and be able to reset device to factory ? thx.
Good morning, it is impossible to access the internal memory through the remote control. If I enter the "sdcard", I see a blank page and not the usual folder structure. Plus I can't transfer any files, even with any file sync rule which always returns a sync error. I'm absolutely sure the privileges to access the internal memory are granted to the MobiControl agent, I double checked in the Settings/App/MobiControl/Authorization page too. I'm also sure the correct plugin is installed, since I can remote control the devices. What could be the problem? Is there any script I may try to fix this? Below some information: MobiControl version: 15.5.0.1021 Agent version: 15.1.5.1049 Manufacturer: Emdoor Model: RD86QE (EM-Q86) Android version: 10 Enrollment type: Work Managed Device Below some screenshot where you can see the impossibility to access the internal memory, both from remote control (web and plugin) and file sync rule: Thank you
I am currently trying to programme a little toolbox for our technicians (i don´t want to give them access to devices and or webconsole directly). Hence its just a small tool i didnt want to host it as a webservice / server somewhere either. The issue with using fetch in any modern browser no is that unfortunately the mobicontrol api answers POST-Request´s withouth CORS Information. < Access to fetch at '' from origin '' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. > With mode: 'no-cors' it works but the browser only returns opaque data
Hi SOTI Users, I'm new to SOTI and using the scripts, but I've tried several referenced here: Script Commands for Android Plus Devices (soti.net) and am able to trigger messages, but not actually "Sign out" of Soti or log off of the device. I've tried "disconnect" and "shutdown" and "turnoff". What I'm trying to accomplish is for a device to log out of SOTI if there is no activity for a long time to make sure that someone new picking up the device will need to log in again. Any help is appreciated.
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.
