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.
Hello,When I click on the SOTI MOBICONTROL agent menu button, the menu does not appear.I Use ZEBRA VC8300 terminals under Android14.Issue is the same on all devices.If I click on the 'Profiles' tab it works, I can see the list of installed profiles.Do you have any idea how to authorize access to the agent menu?Regards
We are currently attempting to develop an image for a Dell Lattitude 7350 to send to Dell so our machines come pre-imaged. In the past we would just manually install the agent then run sysprep but now we'd like to get the agent installed either on the image on have it set to run on first login. Has anyone installed the agent via an unattend or script that runs on first logon and preferably in quiet mode?
Hi, I need to factory reset one of my devices, but it's not in my office and I cant configure it personally. Is it possible to make a factory reset without losing the Agent, so I can configure it again remotely? All my devices are SUNMI L2S PRO. Thanks in advance
Hello, I have a trouble. After agent update from 2024.1.0 to latest 2024.1.1.1125 all of my lenovo' devices deleted. Server Version: 2024.0.1.1020 I requested agent update(not delete) and this happend: Model is: Lenovo TB-X505F, A10 others devices worked without problem. I lost almost 300 devices from soti right now. Any idea how should I return devices back into soti please? thank you
Hi all, A bit of a strange and niche request here but I am hoping that I can access the "Content Library" part of the SOTI MobiControl app directly from a lockdown mode on Android. Very similar to how you would launch the notifications part of the application by using action://net.sotimobicontrol.VIEW_NOTIFICATIONS - we use this for notifications and it works very well. My reason for this is we want to issue this device to drivers as part of our fleet and although we aren't concerned about them accessing the rest of the SOTI MobiControl app, the Content Library is the most useful part of it for them so i'd like to make it the "default" view when they launch it via the lockdown mode if possible. I know it's unlikely and I have opened a case with SOTI as well, they are investigating but asked me to post here incase anyone had done similar. Thanks, Mike
Hi Everyone, I did an update of MobiControl OnPremise Server.From Version 14.4.9 to 15.6.4 Everything worked as expected and I had no issues. Now I have one question. MY devices Zebra MC3300 with Android 10 still have MobiControl Agent Version 14.5 installed. I can't upgrade the Agent to the latest. Under the global settings I can only manage the plugins and the agent is not shown to me.Can someone explain to me why? The server doesn't have managed google play so this isn't a option for me to update the MC agent. Whenever the support did an update for a cloud server I was able to update the agents afterwards. Thanks for your help!
Just after some advice if possible. We're trying to enrol and start using Samsung Galaxy Tab Active 3's using Android Classic enrolment (we have good reason currently but will opt not to go into any specifics on this). Those devices are running Android 13 on February 2023 security patch. We have only one live user currently and one test device in hand. The test user has periodically complained that the lockdown has crashed with a message saying that the menu could not be loaded and to contact an administrator. This is happening at awkward times and often when support for the individual isn't available. It can only be fixed if the lockdown is revoked and then re-applied. Agent version 15.3.1 Just wondering if anyone else has experienced this and has a work around? Not sure if this is a bug, whether the lockdown itself is at fault or whether something in the OS is corrupting the menu? I notice in Android 13 that you can select the default home screen between MobiControl and One UI - you can set it to MobiControl but on reboot I don't think its always retaining that setting and I have noticed periodically One UI gets set again. Not sure what the default should actually be and if this impacts the agent/lockdown at all. At a bit of a loss really and not wanting to go fully live until the problem is worked out. I was going to set something to maybe get the agent to log some more debug information to see what the culprit may be but have forgotten how to set up more logging via the agent for Android Classic. Thanks
Is it possible to start the agent on an Android before a user logs in ? Or how do I get onto an android when it has only been switched on ?
Hello. I have some Samsung Galaxy tablets that were unenrolled from SOTI in the past because they were not being used by our company. We have found a use for these and re-enrolled them back into SOTI. When we go to assign the profile, we have them checked but the tablets have not received the profile yet. These are android plus devices and the profile we are wanting to assign is also android plus configuration. Could someone please help me figure this one out? are the devices too old or not compatible anymore? Is there an issue with using devices that were previously enrolled, unenrolled and factory wiped and enrolled again? all help is greatly appreciated. \
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 ,
Hi According to the release notes in 15.1.2 there has been added some new scripts but you did not specify what the scripts are. Could you please describe how to use these?
Hi All, Accidentally deleted my original post when trying to post a fix... so apologies to all that was following my other post Quick Background Since upgrading MobiControl to v15.4 we notice an issue with direct downloading the agent when trying to enroll a device. We would constantly get the following error when we hit the download button on the mobile device when enrolling and it would fail This is a fix for that issue that worked for me. So use this at your own risk. I will summarise the fix, so if you need a bit more info let me know as it can get technical For this fix, you will need to be able to access and edit your SQL database for MobiControl
Good Morning. I am trying to upgrade the agent on several of our Android Enterprise devices. I have not been able to upgrade using the button. I will select upgrade and upgrade now instead of start on schedule. I will get a message that says "Upgrade Agent Action has been sent to device" The message is a success message. When I go to check the agent version, it remains the same. Is there an extra step I need to do in order to upgrade the agent? Soti Cloud version 14.4.6 Current agent on tablet: 14.1.4.1010 Trying to update to Agent Version 14.5.4.1016 Settings Manager app 15.0.1 requires to have Agent 14.4.7 or higher to use. I have been able to upgrade it using a profile package. But I need to be able to upgrade one specific device. What is the best way to do this?
Hello, has anyone encounter the issue where the backbround service & agent only start if the device was once unlocked after a restart?
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.
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.
