There's a new home for Articles. Find Articles on Our Product Support Page.
Hello, I have to set with the help of MobiControl to get the same result as doing manually with system->language->virtual keyboard->not use system language->set required language. Devices are Zebra TC52 with Android 10 and AEDO. Also in the Zebra Enterprise Keyboard API/MX I didnt find a way to do that beside creating a whole new custom keyboard layout, but for just one setting doing a new layout is hugh effort. Martin
Recently I started moving from iOS devices to Android for retail handheld mobile computers and enrolled them into Device Manager. Starting August 1st with the latest update of Device Manager that Meraki released I have had all of my apps continuously install and uninstall. I submitted a case with them and the most I have gotten is that it is a known bug and that there is no timeline for a fix, this has been 2 months now. I think it is important to call out Cisco for their extremely poor development practices with Android, I found this "bug" within an hour of Device Manager updating, there is no way that Cisco tested this app before releasing it. I am heavily considering moving to SOTI MobiControl. Has anyone else had any similar experiences with Meraki MDM?
Adding new devices and when it pops up with the pending actions menu and I click on "work profile provisioning" I get the following error:Oops! Work profile can't be created because you've reached the maximum number of users on your device. Remove at least one user and try again." I am not sure what users they are referring to. I am the only one on the device. I have setup one device without issue and 2 other devices are getting this error. I would ignore it if I could, but it pops up constantly making it useless for my end users. I noticed on the Device Details within MobiControl, the device that is working properly says "Device Kind Android Enterprise" and the devices that are having issues both say "Device Kind Android Plus". I find this odd as I used the same APK for both of them (GoogleMobiControl1430_1000.apk) and they are the same make and model devices, Honeywell CK75. I am new to Mobicontrol so any help would be appreciated. If I need to post more info, please let me know and I will do so.
Dears, I am trying to enroll Samsung Mobile A01 Android 10.1, the steps i did is: - Brand new mobile, Start, set the link on google email, AFW#mobicontrol (Android Enterprise) and it install the agent with no issue, and when you go to my SOTI License , you can see that it took a license, and you can run the application and add the enrollment id, until this point everything is fine, but after enrollment id success, the Soti Mobicontrol agent open and it give a msg, Your License is not Activated, this could take until hours sometime foe it to find the license and work and some time it dont. Mobile Samsung Galaxy A01 Version 10.1 Android any support on why its takes long time to work ? and the cure for it.
We have devices where we want to install a lot of profiles. My problem is, that the lockdown is installed before the other profile installations are finished. So the user cannot finish the other actions at the device, because it is in the lockdown mode. I hope u can understand my problem. Can i prioritize the sequence of the installation on the device, for example: First --> Authentification Second --> AppInstall Third --> Lockdown Thanks for your help!
Hello, We are finding some of our Android Zebra TC56's occasionally end up with incorrect times/timezones. We force time sync to our deployment server through Advanced Configurations, but we still have some devices where the time is wildly off. Is there a way to run a report on this in SOTI to find troublesome devices? At the very least I could push a StageNow profile to them forcing clock settings. Thanks!
Hello, I have a few devices that i can enroll as a work profile but not as an enterprise device. We require the enterprise solution so we can remote control the devices if and when they need some troubleshooting. Our MobiControl server sits on xxx.xxx.53.53 and the Zebra MC93s are situated on a closed WiFi Network that gives the device xxx.xxx.55.124 Both IPs are reachable from both sides. I can ping the server from the Android device and i can ping the device from the 53 subnet. The WiFi that the scanners are has no internet connection and is an internal network. I asked the question before if anyone has come across being unable to enroll devices and i was told that there should be no issue enrolling these scanners on a network that is on our own WAN with no internet connection. We are unable to give the devices internet connection due to security policies in the warehouses we are located. Our enrollment server address that the rule generates is xxx.xxx.53.108 but when i try the server address on the enrollment part of the MobiControl app on the device, it throws a "Invalid URL" prompt. When using the Enrollment ID i just get an "Enrollment Failed" message. Does anyone have any pointers i can try?
Hello, we work with soti mobicontrol on version v13.3.3454 We have the device zebra tc75x with client version mobicontrol on 13 6 0 1476 I have a profil who have some authorized number and not authorized numbers I have deploy this profile yesturday and only on two device that doesn't work .. It's work on many device ... SAME Zebra TC75X under android 7 when driver try to call some phone number it's not possible ... Profile is on status -> installed Any idea ? I've try to reboot the device but nothing work... thanks for your time
hey, i have a small problem with the battery percentage of Symbol TC75. the battery percentage on PDA doesn't match with the percentage on Mobicontrol. have you an idea how to fix this issue? thanks, Mohammed
Hello, Using MobiControl 15.1, Zebra TC70 running 5.1.1 and TC70x on Nougat 7.1.2. We have been able to track an issue where our team members are using Enterprise Browser and they are "kicked out" of what they are doing and presented with the Mobicontrol lockdown screen, requiring them to re-login to websites, etc. to continue. Obviously, this is very frustrating for our team members. This coincides with an Information event in the log file stating: Custom Log (This device has been switched to user mode) The device agent log gives this information at the time of occurrence:2020-07-22 13:03:54.773|injector|E|N/A|[net.soti.mobicontrol.df.q] injector| DUPLICATED subscription - class: net.soti.mobicontrol.email.b.b|2020-07-22 13:03:54.941|injector|E|N/A|[net.soti.mobicontrol.df.q] injector| DUPLICATED subscription - class: net.soti.mobicontrol.featurecontrol.eg|2020-07-22 13:03:55.763|injector|E|N/A|[net.soti.mobicontrol.df.q] injector| DUPLICATED subscription - class: net.soti.mobicontrol.script.ab|2020-07-22 13:03:55.906|injector|E|N/A|[net.soti.mobicontrol.df.q] injector| DUPLICATED subscription - class: net.soti.mobicontrol.admin.DeviceAdminNotificationManager|2020-07-22 13:03:55.987|injector|E|N/A|[net.soti.mobicontrol.df.q] injector| DUPLICATED subscription - class: net.soti.mobicontrol.wifi.bl|2020-07-22 13:03:56.032|injector|E|N/A|[net.soti.mobicontrol.df.q] injector| DUPLICATED subscription - class: net.soti.mobicontrol.admin.DeviceAdminNotificationManager|2020-07-22 13:03:56.066|injector|E|N/A|[net.soti.mobicontrol.df.q] injector| DUPLICATED subscription - class: net.soti.mobicontrol.wifi.bl|2020-07-22 13:03:56.310|injector|E|N/A|[net.soti.mobicontrol.df.q] injector| DUPLICATED subscription - class: net.soti.mobicontrol.email.b.b|2020-07-22 13:03:58.116|execution-pipeline|E|N/A|[dy][handleApplyException] - applying - [DisableCellularData]|java.lang.NoSuchMethodError: No virtual method setMobileDataEnabled(Z)V in class Landroid/net/ConnectivityManager; or its super classes (declaration of 'android.net.ConnectivityManager' appears in /system/framework/framework.jar) at net.soti.mobicontrol.featurecontrol.feature.application.u.a(SourceFile:38) at net.soti.mobicontrol.featurecontrol.lr.setFeatureState(SourceFile:102) at net.soti.mobicontrol.featurecontrol.cm.changeFeatureState(SourceFile:63) at net.soti.mobicontrol.featurecontrol.cm.changeFeatureState(SourceFile:18) at net.soti.mobicontrol.featurecontrol.fj.apply(SourceFile:52) at net.soti.mobicontrol.featurecontrol.dy.a(SourceFile:32) at net.soti.mobicontrol.featurecontrol.eg$3.a(SourceFile:220) at net.soti.mobicontrol.featurecontrol.eg$3.a(SourceFile:217) at net.soti.mobicontrol.fn.a.b.d.b(SourceFile:8) at net.soti.mobicontrol.fn.a.a.c.b(SourceFile:295) at net.soti.mobicontrol.featurecontrol.ee.a(SourceFile:92) at net.soti.mobicontrol.featurecontrol.eg.d(SourceFile:195) at net.soti.mobicontrol.featurecontrol.eg.doApply(SourceFile:106) at net.soti.mobicontrol.dx.b$1.executeInternal(SourceFile:43) at net.soti.mobicontrol.dt.k.execute(SourceFile:8) at net.soti.mobicontrol.admin.AdminTask.execute(SourceFile:22) at net.soti.mobicontrol.dt.o.run(SourceFile:29) at net.soti.mobicontrol.dt.e$5.run(SourceFile:141) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) at java.lang.Thread.run(Thread.java:818)|2020-07-22 13:03:58.349|injector|E|N/A|[BaseApplicationControlManager][enableApplications] - error while enabling package com.android.settings/.DeviceAdminAdd : com.android.settings/.DeviceAdminAdd blocked by ManualBlacklist, do not enable it|2020-07-22 13:03:58.706|mobicontrol-service|E|N/A|[net.soti.mobicontrol.df.q] mobicontrol-service| DUPLICATED subscription - class: net.soti.mobicontrol.fr.f|2020-07-22 13:04:00.552|execution-pipeline|E|N/A|[net.soti.mobicontrol.featurecontrol.feature.tethering.a] Bluetooth is not tetherable ..|2020-07-22 13:04:00.559|main|E|N/A|[net.soti.mobicontrol.featurecontrol.feature.tethering.a] Bluetooth is not tetherable ..|2020-07-22 13:04:01.371|main|E|N/A|[net.soti.mobicontrol.lockdown.dw] View=net.soti.mobicontrol.lockdown.dw$a{b9cce2c V.E..... ......I. 0,0-0,0} not attached to window manager|2020-07-22 13:04:01.382|main|E|N/A|[net.soti.mobicontrol.lockdown.dw] View=net.soti.mobicontrol.lockdown.dw$a{b9cce2c V.E..... ......I. 0,0-0,0} not attached to window manager|2020-07-22 13:04:01.433|execution-pipeline|E|N/A|[net.soti.mobicontrol.lockdown.au] Failed to disable app!|net.soti.mobicontrol.appcontrol.ApplicationControlManagerException: Cannot find net.soti.settingsmanager at net.soti.mobicontrol.appcontrol.PlusApplicationControlManager.doEnableApplicationLaunch(SourceFile:54) at net.soti.mobicontrol.appcontrol.Plus50ApplicationControlManager.doEnableApplicationLaunch(SourceFile:40) at net.soti.mobicontrol.appcontrol.BaseApplicationControlManager.enableApplicationLaunch(SourceFile:62) at net.soti.mobicontrol.lockdown.au.b(SourceFile:105) at net.soti.mobicontrol.lockdown.ah.a(SourceFile:134) at net.soti.mobicontrol.lockdown.ah.b(SourceFile:82) at net.soti.mobicontrol.lockdown.ah.d(SourceFile:77) at net.soti.mobicontrol.lockdown.au.a(SourceFile:62) at net.soti.mobicontrol.lockdown.ak.f(SourceFile:204) at net.soti.mobicontrol.lockdown.ak.s(SourceFile:329) at net.soti.mobicontrol.lockdown.ak.b(SourceFile:416) at net.soti.mobicontrol.lockdown.ak.doApply(SourceFile:307) at net.soti.mobicontrol.dx.b$1.executeInternal(SourceFile:43) at net.soti.mobicontrol.dt.k.execute(SourceFile:8) at net.soti.mobicontrol.admin.AdminTask.execute(SourceFile:22) at net.soti.mobicontrol.dt.o.run(SourceFile:29) at net.soti.mobicontrol.dt.e$5.run(SourceFile:141) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) at java.lang.Thread.run(Thread.java:818)Caused by: java.lang.IllegalArgumentException: Unknown package: net.soti.settingsmanager at android.os.Parcel.readException(Parcel.java:1550) at android.os.Parcel.readException(Parcel.java:1499) at android.content.pm.IPackageManager$Stub$Proxy.getApplicationEnabledSetting(IPackageManager.java:3464) at android.app.ApplicationPackageManager.getApplicationEnabledSetting(ApplicationPackageManager.java:1519) at net.soti.mobicontrol.appcontrol.PlusApplicationControlManager.doEnableApplicationLaunch(SourceFile:42) ... 19 more|2020-07-22 13:04:02.375|execution-pipeline|E|N/A|[dy][handleApplyException] - applying - [DisableCellularData]|java.lang.NoSuchMethodError: No virtual method setMobileDataEnabled(Z)V in class Landroid/net/ConnectivityManager; or its super classes (declaration of 'android.net.ConnectivityManager' appears in /system/framework/framework.jar) at net.soti.mobicontrol.featurecontrol.feature.application.u.a(SourceFile:38) at net.soti.mobicontrol.featurecontrol.lr.setFeatureState(SourceFile:102) at net.soti.mobicontrol.featurecontrol.cm.changeFeatureState(SourceFile:63) at net.soti.mobicontrol.featurecontrol.cm.changeFeatureState(SourceFile:18) at net.soti.mobicontrol.featurecontrol.fj.apply(SourceFile:52) at net.soti.mobicontrol.featurecontrol.dy.a(SourceFile:32) at net.soti.mobicontrol.featurecontrol.eg$3.a(SourceFile:220) at net.soti.mobicontrol.featurecontrol.eg$3.a(SourceFile:217) at net.soti.mobicontrol.fn.a.b.d.b(SourceFile:8) at net.soti.mobicontrol.fn.a.a.c.b(SourceFile:295) at net.soti.mobicontrol.featurecontrol.ee.a(SourceFile:92) at net.soti.mobicontrol.featurecontrol.eg.d(SourceFile:195) at net.soti.mobicontrol.featurecontrol.eg.doApply(SourceFile:106) at net.soti.mobicontrol.dx.b$1.executeInternal(SourceFile:43) at net.soti.mobicontrol.dt.k.execute(SourceFile:8) at net.soti.mobicontrol.admin.AdminTask.execute(SourceFile:22) at net.soti.mobicontrol.dt.o.run(SourceFile:29) at net.soti.mobicontrol.dt.e$5.run(SourceFile:141) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) at java.lang.Thread.run(Thread.java:818) Can anyone explain to me what is happening and how to fix it?Thank youZachary Taylor
Hi together, we will use Nokia 5.3 in future. There's only RemoteView available for now. I think because of no plugin. Will be there a plugin coming for Nokia 5.3 or is there another Nokia-Plugin which will work (tested "Nokia and Nokia 5.0, both can't be installed because of incompatiblity)? Or must i do a request at a different place?
Hi All, We have a problem with Remote Desktop. When we are trying to connect to a device, we can see only a black screen, and we cannot open the device screen with the power button. This what we have checked / tried: "Disable screen capture when browsing" in SOTI Surf settings is unchecked _resetfailedrcdetectionflag + restartagent does not help "unlock" does not help If somebody unlocks the device physically, then it's working fine for some time, we also can lock screen, and unlock it for a few hours, but after about a day, it's the same again. Do you have any idea what is the problem? Agent version: 13.6.0.1257MobiControl version: 14.1.0.1152 Thank you in advance,Csaba
Hi everyone, possible silly question of the day. Due to an acquisition I've just inherited a few devices which don't seem to support Android Enterprise. These are Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285 running Android 5.1.1. Is there anyway to get Android Enterprise to work on these so that we can implement lockdown?
Hi, I have spent the last few days speaking back and forth with support and am now looking for if anyone else has had these issues. When I run through the initial setup of the Scanners (Zebra MC9300) I am told by the MobiControl guide to use the afw#mobicontrol when asked for a google account. This works, and MobiControl is installed. This issue then is when trying to enroll the device into our MobiControl server the enrolment fails, using the SSID we use for all the scanners on our estate. Using the Enrolment ID or URL does not allow us to enroll. The SSID we use for our scanners is locked down from internet usage because of where they are situated and internet access on any device is prohibited. Now the fun part. I am told that the devices NEED internet access to contact the deployment server to enroll the devices, BUT when I skip all of the initial setup and install the APK from the MobiControl Agent site, I can enroll the device, it comes into MobiControl and I am able to configure profiles and such. The only issue is we can only remote VIEW the devices. Now most of these devices are on remote sites (we are in UK, Warehouses are in France) therefore we need to be able to remote control the device to troubleshoot any issues that may arise. I am told that the devices need to be enrolled as enterprise devices in order to be able to remote control them and even when manually installing the APK it should enroll as a enterprise device rather then just a work profile.I tried also to set up the StageNow application but was unsuccessful to get it to stage using a barcode. Has anyone got any ideas or scenarios that are similar? TIA
Hi,we have a customer where on several EDA70 devices the soft buttons are not working from time to time. The solution so far is factory reset, afterwards it's working again. They are enrolled in SOTI. The solution: factory reset is not the preferred solution for the customer so far. Do you have any idea why this is happening with the devices? I don't have any idea so far, this doesn't happen on a "regular" basis, it just happens. 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.
