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.
Hi everyone, we are currently staging some AE devices with Honeywell Enterprise Provisioner with enrollment ID. In contrast to the staging method with INI file during the staging process we have to click on "Next" and "OK" while the device is preparing for WorkManaged device. Why? What is the difference to the AE staging method with INI file? Is the device connecting to google? If yes: Why does it connect to Google at this point of the staging process?
When taking the device out of the box, the device has a wedge app that can able you to test it out. You can also take any app that will accept a scan and it will work. When I install the Mobicontrol agent, it strips away all apps that enable the scan function. Now when i go to a test app to scan something, no laser will show when the side buttons are pressed. Why would the agent strip that function away?
Hi!, Problem: - I have a problem with google account identities status is "Account Activation Pendding" after successful enrollment. - At MobiControl WebConsole show log "Error message received from device (Managed Google Play Account Status:'EMPTY_TOKEN Got response but there was no token!')" - At device show "Pending Actions" Google account Completing configuration for your Work Profile *** Before that, I had a device that was successfully registered. Without any problems * Addition detail - I set up device and install Mibicontrol from "afw#mobicontrol" before final success set up device complete
Hello, has someone already experience with the new Version 14.3.3.1004 of the AE Agent ? It is offered since some days in the MobiControl Agent Updates, but in the online release notes there is still just the 14.3.2.1050 Version available. Till now I found one new feature, on Zebra Android 8 and up Devices it displayed the MX version in Device Details, already before the Zebra Device Plugin is installed. GreetingsMartin
Hello, I seen some topics on this subject but I haven't found an answer. Is that possible to disable the Airplane Mode on a version 14.3.3.1111 of MC (AE Device Owner) so if users accidentally click on it when they want to power off the device it has no impact. Thank you
I'm looking for an easy, ad-hoc method to remove a file from an Android Enterprise device using scripts. In the past, the "del" command was supposed to work, but no more. http://www.soti.net/mc/help/v15.2/en/scriptcmds/reference/androidplus_enterprise_do.html
Hi all We are currently testing a Honeywell CT40 for a possible deployment. Is it normal that when we enroll android devices as enterprise managed, there's several system apps that disappear ? (i.e: camera, gallery ...) Now we have to retrieve the exact bundle ID and install the apk Any inputs ? Thanks,
Hello, maybe you can help me out here even though i am almost sure its a limitation of mobicontrol / device at this point. i want to set the timeout before the display gets locked to 30 minutes and the powerbutton should only turn of the screen. on an android+ device i found the following with watchsettings so far: Lock Screen After Timeout: Custom log (URI:content://settings/secure SETTING:lock_screen_lock_after_timeout VALUE:1800000) For the powerbutton option i sadly got no result. Using the following script on an aedo device got me no result: writesecuresetting -sec lock_screen_lock_after_timeout 1800000 I then tried to find something with adblogs on the aedo device and found the following settings triggered: security.screenlock.ScreenLockSettings/lock_after_timeout|1800000 security.screenlock.ScreenLockSettings/power_button_instantly_locks|false i tried multiple combinations of the settings with writesecuresetting i.e.: writesecuresetting -sec lock_after_timeout 1800000writesecuresetting -sec power_button_instantly_locks false writesecuresetting -sec lock_screen_lock_after_timeout 1800000writesecuresetting -sec lock_screen_power_button_instantly_locks false None of them worked. Any Ideas would be appreciated.
Hi,has anyone encountered an issue where when other app is trying to access SOTi issued user certificate and android is asking to set pin or password to access credential storage? Android 7 enrolled as Android + worked, but after upgrading device to android 8 and enrolling as Android Enterprise this issue appeared. Is it fault in new security settings in android 8 or soti app permissions? Would it be possible for SOTI to allow access to credential storage without PIN for some apps? Device TC51 running 02-32-04.00-OG-U01-STD OS 8.1.0Agent 14.3.0.1000A+ Service for Zebra - 1.6.0.102 SOTI Version: 14.3.4.1087
Hi all, We using Enterprise devices. Around 8 apps download from the Managed Play Store. All are set to mandatory. The issue we are seeing now after updating the server to 15.2 is that on the first two devices staged. One did not install WhatsApp and the second did not install Soti Surf. The Agent Version is 14.1.1 Build 1050 Any Suggestions would be grateful. Regards Martin Doyle
Hello, Is there a script to set a default launcher for AE Samsung devices? I see there is MX configs for Zebra, but not seeing anything for Samsung.
Last year it looked like a solution for deploying DataWedge profiles/configs to Android devices in Device Owner mode was discovered. I'm trying to perform the exact same action on a Zebra TC52 running Android 8.1 and higher. I've followed the thread above and official documentation from Zebra, but something is off somewhere. I've tried both the Android Enterprise and legacy Device Admin (just for giggles) commands to no effect. __chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db AND execute_shell chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db The device logs even show the file was successfully downloaded to the device, but for whatever reason DataWedge is failing to pick up the file and import it. Even FCing the app before or after a sync and a device reboot nothing gets imported. What am I missing here?
Hi, I have a odd new issue on our MobiControl server related to enrollment. We use version: 13.4.0.4167 The issues is that we cannot enroll new devices as the process does not complete on the client side. We have tried both Android Enterprise (afw#mobicontrol + QR code) and Android Plus. The devices does pop up in mobicontrol, but the install is not completed on the devices - therefore they kind of errors with a re-try option and in the end you come back to the page asking for Enrollment ID. Not sure how to fix this, as it suddently occured this morning. Anyone experienced something similar and what did you do to fix this? /Dan
Hi, We have Zebra TC77 devices with our customers and the users have been able to activate the "Talk back" functionality. I believe they have been able to do this as the accessibility shortcuts are turned on. To activate this, I believe you press and hold both the volume up and down. Is there a way to switch the ability to be able to do this across the whole estate as we have many of these devices out in the field and some in different countries. ThanksJosh.
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.
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.
