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 trying to update Chorme on Zebra TC7* devices. I have enrolled the devices in an account with Google Play. I setup Chrome and Adobe Acrobat to be updated by Google Play Acrobat updates..... Chrome does not. Device : Zebra TC75x OS: Oreo 8.1 Enrollment: AEDO Agent Version: 15.1.3.1071 Console Version: 15.3.3.1065 I have opened a ticket with SOTI and have not received any valuable information towards resolving this. Has anyone run into this. Thanks, Jim
Hello everyone, We have a lot of equipment with soti mobicontrol, these devices are tablets with android 10/11. Is it possible to extract a report that shows the name of the devices connected to these tablets? I appreciate your help, best regards
We leverage MobiControl to manage our CK65s and CT60s. We also leverage Staylinked SmartTE and have historically pushed the staylink.ini file located in "%sdcard%/Android/data/com.staylinked.AndroidClient" using a MobiControl package so that it can establish the initial Staylinked sever connection.As of Android 11, MobiControl can no longer push files to the "../Android/data" directory. I had come across this on the Honeywell support site: https://support.honeywellaidc.com/s/article/Android-11-permission-required-for-Workspace-One-Agent-SotiAgentBut this doesn't seem to work for the CT60 or CK65.Staylinked allows you to manage the SmartTE config once connected, but we need to be able to pusht he server address via the staylink.ini file prior to it taking control.Soti is currently working a case on this.I have a ticket into Honeywell.I have a support request with Staylinked.I also have some help coming from a VAR we purchased the equipment through.So now I'm reaching out to the community to see if anyone has had any luck with this at this point?One of the issues is that when the Honeywell firmware package is pushed to upgrade the devices from 10 to 11, it seems like the SmartTE config is also wiped out as the application is updated.Unfortunately, I'm running out of ideas short of a firmware rollback, which isn't something I want to worry about later since 80 of these devices have yet to be deployed. It'd be incredibly helpful to get them on the latest version of Android for the device prior to deployment.
Hi, I need to manage dual sim device as follow Sim 1 should only use for take calls Sim 2 should only allow to use for Internet access (all applications should access Internet via this sim only) user should not able to enable the Internet on Sim 1 or disable the Internet on Sim 2. Device model Samsung A12
Hi, does anyone know a way/script to write into an existing ini file? I tried several things regarding javascript but i'm not familar with javascript, so i don't know where the Problem is. The file is located in the /sdcard/ folder and we are working with 15.5.1 and the latest agent versions.
I'm new to Soti Mobicontrol. Would like to know if someone can point me how to do this. I found documentation that Soti can execute intents on Android: https://soti.net/mc/help/v14.3/en/scriptcmds/reference/sendintent.html I first want to deploy an uploaded Android app APK, then together with or after the app deployment, execute an intent on that device. I kind of got the 1st part, but not the 2nd part for executing intent on a device after the app is deployed to it. Someone help me connect the dots. For the intent, adapting the command syntax we estimated/derived for AirWatch, the AirWatch command would have been something like mode=explicit,broadcast=false,action=android.intent.action.MAIN,package=com.mist.marvisclient,class=com.mist.marvisclient.MainActivity,extraString=MOBILE_SDK_SECRET=TheSecretValueHere what's the equivalent translated command for Soti sendintent command?
Hello Guys, We wanted to display information about use the SOTI surf instead of our core app which on lockdown screen. How we can add this information on lockdown? like html form adding information. so when user click or try to open that app so they will get information about they need to use SOTI surf instead of that app.
Hello all, we have imported configurations to the device on a number of Zebra TC52x using the Velocity file Assistant app (The app will sync/copy all the velocity configuration files from /sdcard/com.wavelink.velocity folder to /sdcard/Android/data/com.wavelink.velocity/files folder after starting velocity). Unfortunately, due to a change in the profile name, we are now seeing two profiles. Due to Android 11, we cannot simply delete the files via the file browser. In the Ivanti community we came across the following article:https://forums.ivanti.com/s/article/Android-11-Non-Android-enterprise-Method-to-deploy-files-from-MDM-using-Velocity-File-assistant-app?language=en_US Here it is shown that with the following intent the files/profiles can be deleted: Intent intent = new Intent(Intent.ACTION_VIEW); intent.setComponent(ComponentName.unflattenFromString("com.wavelink.velocityfileassistant/.FileUpdate")); intent.putExtra("com.wavelink.velocityfileassistant.extra.CLEAN", true); try { startActivity(intent); } catch (ActivityNotFoundException e) { // Velocity File Assistant was not found Unfortunately, this does not seem to be the correct syntax for MobiControl. Do any of you have an idea how the intent has to look exactly so that we can delete the profiles? We would be very grateful for any help! Kind Regards Keno
Good morning, We have to deploy a new application on some devices and we have a problem accepting permissions silently. We are going to deploy the application using the policies/apps method because we have to configure some information (Device ID & connection code) it works fine, and the app connect to the Sophos console automatically and the device appears with the name of our soti console what was the goal. But the problem is that we have to grant some permissions manually before the process ends. We are trying to grant these permissions remotely via scripts and we have tested these scripts with no result: afw_set_permission_grant_state com.sophos.smsec android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS allow afw_set_permission_grant_state com.sophos.smsec android.permission.PACKAGE_USAGE_STATS allow We have tested this script too: request_appops_permission android.permission.PACKAGE_USAGE_STATS We are running Versión: 15.5.1.1010 of Soti Mobicontrol . The device I am using to test is a Samsung SM-T510 with android 9 and agent version 15.2.0.1025. Is it possible to silently deploy these permissions? Is there any other test or way to silently grant these permissions on these devices? Thank you for your help!
Hi there, we have updating Soti Mobicontrol to Version 15.5 and after this we can't go to the Serverpage (old console view). We got only a blank page and nothing happens. We test different browser, cleare the cache and try other users. On the Testsystem with the same update it works fine... Has anyone the same problems? Best regards Franko
Hi, Customer has TC26 devices on Android 11. Enrolling via Zero Touch into Mobicontrol 15.5 Enrollment is fine and Mobicontrol works well, however, when I send a wipe command to the device, I expect it should wipe, start back up and re-enroll with Zero Touch. However, the behaviour seems to be that the device thinks it's already managed by Mobicontrol but still goes through the Zero Touch setup screens. This then fails and asks be to restart the device. So alternatively, I tested factory resetting the device with Zebra Factory reset file and script. This however leads the device to not follow Zero Touch at all until the device is at the Anroid Homescreen, at which point the device gets the normal Zero Touch message about being managed and needing to factory reset in 1 hour to get the device under managment. In Summary, wiping an enrolled TC26 on Android 11 does not show a desired or expected behaviour. Has anyone else experienced this who could advise what I should be doing differently? Happy to provide more info where required. Cheers
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 ,
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.
Hi, At least a couple of our users are experiencing a sudden increase in battery drain om their Android phones (Samsung A5's). The battery drain appears to be due to MobiControl and potentially linked to it accessing location too readily. The only reason for assuming location is that the location icon is now constantly appearing at the top of their screens and when you look at what is using location mobicontol appears as using it "just now". I've observed mobicontrol being the highest contributor to battery usage at 28% (towards the end of a working day) but the same user stated it was at 90% the day before.We've recently upgraded our environment so I wonder if that's related.Users have rebooted their phones but other than checking everything looked normal on the phone we haven't done any other debugging.Any thoughts?
Hello everyone, here with a subjet that i just saw only few topic about here. We use a internal dev. app in our company , but this one need few permission to work correctly and return some state I did try to use the following Script but seems with no success , maybe typo...maybe something else... anyone to help? Devices are Memor 10 We run on Mobicontrol 15.3.1.1151 Agent are up to date on devices Agent Version 15.1.5.1049 afw_set_permission_grant_state com.trafic.nosmprod android.permission.READ_PHONE_STATE allow afw_set_permission_grant_state com.trafic.nosmprod android.permission.READ_PRIVILEGED_PHONE_STATE allow afw_set_permission_grant_state com.trafic.nosmprod android.permission.ACCESS_WIFI_STATE allow afw_set_permission_grant_state com.trafic.nosmprod android.permission.ACCESS_COARSE_LOCATION allow afw_set_permission_grant_state com.trafic.nosmprod android.permission.ACCES_FINE_LOCATION allow afw_set_permission_grant_state com.trafic.nosmprod android.permission.ACCESS_NETWORK_STATE allow
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.
