There's a new home for Articles. Find Articles on Our Product Support Page.
Hello i am trying to utilize speed control on a tablet, the lockdown mode is working correctly but i want the speed control to active and allow 3 apps to run while it is active. main one is google maps but the two others need to be active in the background or able to be switched to. when the speed control activates it only shows google maps, there is no option for me to move to the other apps. does anyone know if i need to add these 2 extra apps to the template in order for them to work during speed control. below is the configuration of the speed control and im using the default dynamic template Thanks Noah
Hello, We use iOS devices and have set up various profiles on the devices (application run control, feature control, web clips). If we activate DDM so that we can use the more robust iOS update management, will this have any impact on the hisotric profiles that are installed? I think it should be fine, but I'm finding the information online around compatibility reactive and declarative management a bit confusing.
Hi all, First time posting but I've been soaking up knowledge in here for some time and appreciate the expertise found in here a lot! We've deployed an app through the managed play store on our AEDO enrolled devices. We opted to deploy the apps with the "postpone" updating cadence, so as to not receive a potentially unstable version immediately. But now we've run into the opposite issue instead where we need to perform a bulk update. Any ideas on how to send out a bulk update to apps deployed by app policy & managed play store? If anyone is sitting on a script that they've used for this I would appreciate that a ton! We're on MC 2024.1.2 and are running various Zebra devices, all on Android 13.
I've installed it on the device with an app policy, I can see licenses being consumed in my KPE but no settings will apply. I've set it up both using OEM configs and with managed app configs, yet neither will work. I am doing this on a Samsung A9+ and I want to configure battery protection, which this device should support per this article. https://docs.samsungknox.com/admin/knox-platform-for-enterprise/knox-service-plugin/kbas/kba-1151-policies-not-applying-after-installation-on-device/
Hi everyone, with mobicontrol and Zebra TC53 device with both Android 13 and 14, I update some display configurations (manual rotation button) trough Zebra Oem Config 14.2.0.1 using App Policy and managed configuration. Before that, this Policy was already applied to all devices. I have only modified the Display configurations parameter. After that as of when the policy as been updated and applied, the log of each TC53 device reports the "Error sending messag (error sending message (type=22), General Communication error)" every 9 - 10 seconds. Please note, other zebra devices on the same network and same istance of Mobicontrol that are not involved with this policy does not reports this error. Can everyone help me with some suggestions? Thank you
SOTI have any method or android script to force enable installed app on Accessibility Settings ? Agent Version : 2025.2.2.1085Android OS : 9-15SOTI Console Version : 15.3 (on-premise)Device Kind : Android Enterprise
Hi, We’re experiencing an issue with Zebra devices (TC57x) running Android 14 during a OS update from A11 to A14 and re-enrollment into SOTI MobiControl. To get the device to connect to MobiControl, we’ve had to remove the lock screen PIN before updating. Once the PIN is removed and the lock screen is bypassed, the SOTI agent starts and connects automatically after OS reboot. However, when the PIN is re-enabled after enrollment, the agent does not start until the user manually unlocks the device. This creates a problem where devices may restart, and users are not always available to unlock them. Is there a known workaround or configuration that allows the SOTI agent to start and connect automatically even when a PIN is set in Android 14? Any advice or experience with similar setups would be greatly appreciated. Regards JH
For testin purposes i've made 2 kind of settings for our mobile terminals Device inactivity, this triggers a script wich kills some applications after a certain time (approx 1,5 hour). I'm aware this is only working when the devices are not attached to a power source. The second settings is a signal policy, to cover this when attached to a powersource (event is-charging) to trigger the same script after the same time. I'm noticing that (mainly) the Device Inactivity triggers random during the day. Sometimes 2 or 3 times within an half an hour. Sometimes the Signal policy won't start
Hi all Just wondering whether anyone has found the reported activity for Samsung devices running Android 14 for the Task Bar option? When enrolled via Android Classic, the Task Bar button becomes greyed out and can't be interacted with by the user unless it's in admin mode. I have tried using identify_activity to try and locate what the command is to try and write a script that might work for our admins to send over to the devices in a group as aposed to having to revoke the lockdowns applied but all this is returning is the activity for the settings page being opened and settings sub menu. It will not idenfity me turning the option on or off for the Task Bar. I am not sure if there is any other way. Does anyone have any idea? Agent versions are anything 2025 and above. Thanks
What is the simplest way to setup a PowerBI report on the lockscreen? The report cannot be published to the web The report must be set to open directly through the PowerBI application App must launnchwithout constant login Report must be displayed in the mobile display version within PowerBI This would be for a Samsung Android tablet running latest versions of SOTI and PBI. I have used locked down actions of intent, browser, http, launch, custom, etc as well as the basic template html, but do not hit all four criteria above.
I’m upgrading Zebra devices from Android 13 to Android 14 via SOTI. However, after the upgrade, the devices are factory reset and get unenrolled from SOTI. Is it possible to perform the upgrade without resetting the devices — to upgrade directly without a wipe?
A few months ago, we manually enrolled majority of our Samsung devices into the Samsara Driver beta program for testing out new features & giving feedback to Samsara. Now that we are the end of the beta period, we are advising the on-site teams to go through all of their phones manually to unenroll the phones from beta program. On each of the phones, they have to go into the Google Play Store on each phone to remove it from the program, same what they had to do for enrollment. In my testing of removing a phone from the beta program, uninstalling and reinstalling did not automatically remove it from the beta program. Does MobiControl, and I guess Android as a whole, allow IT administrators to either enroll or unenroll devices from application beta programs? All of our Android phones are enrolled into MobiControl as Work Managed if that makes a difference.
Is it possible to map a shared folder from user computers to Samsung Android devices via SOTI?No restrictions will be applied. The only requirement is for the devices to be able to access the shared folder to upload and download files.
Hi, Could you please suggest or any solution to add the javascript as below as a shortcut on kiosk mode mobicontrol.agent.enterAdminMode(); setTimeout(function() { const ACTION_CALL = "android.intent.action.CALL"; const URI_CALL_NUMBER = "tel:*933%23"; var intent = mobicontrol.android.createIntent() .withAction(ACTION_CALL) .withData(URI_CALL_NUMBER); mobicontrol.android.startActivity(intent); },5000); mobicontrol.agent.enterUserMode(); **Mobicontrol Server Version : 15.3****Device Kind : Android Enterprise**
Hello, Is the original_Date & Time Format from Location Collected Data - Andriod Device's CSV file export in UTC time or the Date and Time of the original_Latitude and original_Longitude Time Zone? Thank you for clarification.
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.