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 are on V15.0. Does anyone know if there's a way to turn on certain values without having to visit each device? We are using Zebra VC80x's (Android 7.1.2) and we recently changed from 2.4 to 5 ghz. We noticed that not all the channels we want are turned on by default in Wifi / Advanced settings on the Zebra device. Am I able to turn these on with a script or another way with Soti? Any help would be greatly appreciated. Thank you for your assistance.
When will be there an update to the SOTI Agent to solve following problem (Android 8 and maybe above): From Matt Dermody: Granted, this assumes that writesecuresetting is even working on your Android 8 Zebra devices which has been somewhat of a crapshoot recently. The SOTI Agent needs to have the permission granted in order to have the ability to apply secure settings. That permission is seemingly granted by the installation of the OEM Plugin which from experience seems to be inconsistent in doing so. SOTI staff has indicated that version 1.16 of the plugin is needed in order to truly resolve the issue of having that permission silently granted but as of now only version 1.6 is hosted on the downloads page and 1.12 is hosted within the Plugin Service of newer MobiControl instances. We need that fix, for a zero-touch rollout.
Hi, our devices seem not be able to update the android mobicontrol agent (yes, i activated Agent-Upgrade and send agent upgrade). We got the information that an upgrade is not possible because the actual agent is still compatible. I mean, i know it, because it's running!?! -.- Now i tried the following way: 1. send the apk to the device filesystem 2. send script: install /mnt/sdcard/GoogleMobiControl1400_1579.apk 3. A prompt is shown on the device, which has to be confirmed with OK. 4. Update success Is it possible to do this without user prompt?
Hello, we set up Android 9 devices as BYOD with an Android Work profile. We do the following steps: Setting up the device but skip the Google account setup (because the user of the device should add their personal Google account later) Now the Work profile should be added Is there a better way than now downloading the MobiControl agent apk, install it on the device and enter the enrollment id to set up the Work profile?
Good day all For some reason I am able to view certain devices especially the branches with 20 devices and less in a group. However when trying to view devices from groups with more than 30 devices I am getting an error message 'the server could not complete your request' - an internal error occurred. It suddenly happened from yesterday.
I am using Samsung devices on the Android Plus platform, would like to capture on the same. Mobicontrol Version: 13.4.0.5003 (Running on the Cloud)
Hello, we work with mobicontrol on version v13.0.3454 with a lot of devices zebra tc75x (android 6) under mobicontrol agent on version 13.3.2.1014 Actually I test a procedure for to upgrade to android 7. I meet some problem about it. Here is it the step I follow for to upgrade: a) download os android 7 to zebra site and copy zip file on device b) start the upgrade by a rule of mobicontrol the result, device is well updated to android 7 but If i do some test -> reset / remote control / reset / and so on .. At a moment, the device can't response ..I reboot device and after the device is broken ! Still rest on main screen with message -> start up android …. and nothing happen ... We have few TC75X under android 7 buy there are several month. The device agent on these device aren't the same Ok i can understand. For to avoid to brake device when I upgrade to android 7, I would like to install the agent I have on android 7 to my android 6 and see the result with my test. My question is how i can install the soti agent with mobicontrol ? I remember it's not recommanded to install the mobicontrol agent by a profile ? thanks for all
Hey Guy's, we're actually working with Zebra Devices on Android Nougat (7.1.2) very successfull. All new Devices and also the old one's had to be upgraded to Oreo in the future in Case of security Updates etc. Unfortunately we're not using a PIN or Pattern so far and on Android Nougat it works great. But when I join an Oreo Device, it has to be set up with a Device PIN or Pattern to work correctly. In our specific Case no Certificate for Wifi e.g. can be pushed to device. Also other stuff like mxconfig Things wont work until we set up a PIN on the Device. Is there any Chance to get Oreo running without the need of a PIN on the Device? many thanks PS: Were using MobiControl 13.4.0.5074, Agent Version 14.0.0.1579 in DoA Mode, Zebra TC20 & TC51 / TC52 Devices
I have a weird issue. I cannot uninstall mobiecontrol. It seems to be stuck in a weird loop. Mobicontrol is installed through the afw#mobicontrol option. But on this handheld it didn't remove all the excess apps like it should have. Mobicontrol works as it should otherwise on this handheld. But I cannot remove it at all. If I factory reset the handheld it tells me mobicontrol is still installed and then rebuilds the profile up to the home screen with all of the apps it shouldn't have still there. I've tried going through as much SOTI documentation I can find on how to uninstall mobicontrol and it all seems to stem from turning off the device admin under settings/security/device admin. I do not have the option to turn that off. It's grayed out for me. I've tried this in admin mode and user mode. I've tried various forms of wiping the handheld reset /w and /e. At first I thought /e was going to work because it acted like it was completely wiped and actually brought up the google login screen to where I could type afw#mobicontrol. But when I did this it appeared that the app was already installed and continued to do the same thing. **Edit** This is a Zebra TC20 my mistake I thought I added this.
several of our employees have figured out a loophole in our Kiosk. We are trying to have them use Soti Surf as their browser. The loophole is when they go into adobe and select print - they can click on all services and it will open up a google chrome browser window. we have blacklisted com.android.chrome and have also tried the disable script. So far we have not found a solution. i found this solution https://discussions.soti.net/thread/how-to-fully-blacklist-a-browser/ i have tried the manualblacklist and no avail. our devices are ATT and Verizon Tab A's Model: SMT387 android 9 enrolled with android + can anyone provide further advice? if needed i will open a ticket.
Hi, We are encountering enrollment issues as of today. Environment is AEDO, with managed play store, Zebra TC56. Worked fine for almost 2 years. The NFC part of the process is working fine, we get an error when the MC Agent tries to enroll to the server, it fails. Server version : 13.4.0.5203 The DSE Log says something like that : Corresponding AfW device was not found while processing the device xxxxxxx with afw id yyyy. Anybody already experienced that kind of issue ? I'm mainly trying to find out where I should focus my investigations. Seems like an issue matching a device on the google part, with a deviceid on mobicontrol Thanks
Hello! I'm struggling with the installation of APKs into the work container of Android Enterprise (work managed profile on Samsung S9, Android 9). Installation via package in a profile doesn't work as well as the installation via Application Catalog (Enterprise Application). How can we install APKs into the work container? The log shows following errors: 8:47:32ErrorProfile "Test_AE - Pre-installed Apps" version 4 failed to install, because all of its payloads cannot be installed.8:47:32ErrorPackage "XXXXXXXXX" version 1.0 failed to install. File IO error on device. Check Storage/Permissions.8:47:32ErrorError message received from device (Installierung der Anwendung XXXXXXXX von Paket XXXXXXX.pcg Fehlgeschlagen)
I am wondering if anyone has found a way to not only "ungray" the setting under Settings > Google > Security > Google Play Protect so that it can be toggled, but also actually toggle it OFF. SOTI provided two methods for doing the first item, to re-enable the setting so that it can be manually toggled. The methods are actually the same thing (a feature control) done two different ways: (1) Send script command: writesecureprofstring DeviceFeature DisableVerifyApps 1 apply featurecontrol (2) Create / assign a Feature Control that has "Disable Verify Apps Enforcement" checked. In my experience, these have the effect of re-enabling the toggle on the GPP setting, but leaving the setting toggled ON. It then has to manually be toggled OFF. I have certain apps that are mission-critical and mass-deployed, so touching each device to turn off GPP scanning for first deployment and subsequent app updates is absolutely not a feasible option. So far, SOTI Support has been unable to provide a means to programmatically toggle that option OFF. My other rather large challenge with this is, under AEDO, I've found that a Lockdown Screen profile has the side effect of toggling GPP back on, and graying it back out again so that it once again cannot be toggled off. SOTI says that this is the "expected behavior," to which I respond, WHY? Perhaps I am missing a pertinent concept here, but to my mind it is ridiculous to have a lockdown screen profile that also has the effect of locking GPP scanning on. These corporate users need app installations and app updates -- and those need to happen while the lockdown screen is in place. I've found that if the lockdown profile is already applied, the above two methods will have the effect of "ungraying" the GPP option so that it can manually be turned off. BUT if the lockdown profile ever is re-applied, or refreshes itself due to an editing change (such as perhaps adding an entry for whatever new app(s) are intended to be applied), then GPP is again turned on and the toggle is grayed out. This is very frustrating. I need a way to turn GPP scanning off, and KEEP it off, until I (and only I) tell it that it can turn back on again, Any advice would be appreciated. Thank you, Mark
Hello Everyone, I am attempting to utilize scripts to alter screentimeout and change the screenlock to none. I have tried the below: writeprivateprofstring –sys screen_off_timeout 600000 writesecuresetting -sys Screen_lock_type_Nonewrite_setting -sys Screen_lock_type_Nonewrite_setting -Screen_lock_type_None I am working on Tab A, OS 9, enrolled via Enterprise. Any help would be greatly appreciated! Thank you! Monique
I'm running 14.4 and using a AE device in DO mode, can a script turn on NFC?
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.
