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 demoing a Zebra VC8300/VC83x that shipped with Android 11. I can't say it's going as well as any previous new device. I've used StageNow to generate barcodes and xml files to adjust screen time outs, wifi preferences etc and NOTHING is changing. If I send this legacyt script things do change immediately - do I need to migrate EVERYTHING to writesecuresetting on Android11 or is this device just acting up. To match the fun, if I type the wifi password wrong during initial setup, it boot loops for almost 3 hours before it recovers itself - so it's possible the OS build on this device is just not right - and there are no updates available for it since May 2021. Here is what is working so far. writesecuresetting -sys SCREEN_BRIGHTNESS_MODE_MANUAL 1writesecuresetting -sys SCREEN_BRIGHTNESS 255writesecuresetting -sys screen_off_timeout 1800000
Hi, We have a customer who will be running Remote Desktop in Kiosk mode to a machine and a workspace. Our intention is to add kiosk menu items that launch said PC and Workspace directly rather than presenting the Remote Desktop app itself. Normally, without Kiosk, the user would 'pin' the remote desktop widget to the Android home screen and launch from there, but I believe the kiosk screen doesn't support widgets. how would I go about creating this solution? Has anyone done this before? I've seen mention of an rdp file type with intent on another discussion but I have no experience in this so cannot look to implement. Thanks
Hi! A new day, a new question from my side.We have set the feature control to allow installation from unknown sources.Now we distribute a self-written app to the devices via the app policy.However, when we start the app for the first time, we are still asked whether or not we want to allow the installation of unknown apps. Is there any way to automatically "allow from this source"? After a little searching in the forum, I had already tested the following commands. enable_system_app app_nameafw_set_permission_grant_state app_name android.permission.REQUEST_INSTALL_PACKAGES allowafw_set_permission_grant_state app_name android.permission.INSTALL_PACKAGES allowafw_set_permission_grant_state app_name android.permission.RESTART_PACKAGES allow Best regards and have a nice weekend!
Hi I was hoping to avoid creating a heap load of app rules / app policies by using custom attributes (%CustomAttr:attr_name%) to fill in text depending on the device group. Unfortunately it's not working. I can use standard macros (%ENROLLEDUSER_USERNAME%), so I was hoping to be successful using the macro from custom attributes too. Different device groups are pointing at different servers which is defined in the managed app config. Any ideas to accomplish this? Br Thomas
I have a working profile created from Zebra Stage now.I have exported this for MDM and loaded it into SOTI. This all works fine on an MC9300 running 8.1 apart from the device not rebooting at the end I have upgraded an MC9300 to android 10 and the Enterprise home screen does not work. I am using EHS_4.0005.apk I have also tried EHS_040119 Has anyone got a solution for this, please? I much prefer EHS that using the SOTI lockdown
Hello Soti Team, I am currently trying to further automate our installation of Honeywell CT60 devices. I have used the wizard "Soti Android Enterprise Enrollment Ethernet/WWAN" via the Honeywell Provisioner. I have set the address (http://soti.net/apk/ae2) for downloading the agent and our enrolment ID. The agent should then be downloaded, installed and connected, shouldn't it?Unfortunately, we can only get as far as the installation. When I start the Mobicontrol Agent, I have to enter the enrolment ID manually.I also have to confirm Google Chrome afterwards and agree that it is not a secure connection. Then I have to click continue (the button doesn't look right either). The agent should then connect. But it doesn't always, sometimes the agent crashes and I have to try 3-4 times. So the question: Why doesn't the device connect automatically with the QR code?And what can we do so that the warning that it is not a secure connection no longer appears?
Hello there I’ve just got the question from a customer, if SOTI MobiControl or SOTI Assist is vulnerable to the new Spring4Shell Vulnerability. On the SOTI Central and Community I din’t found any statement. But if I dig deeper I see that JDK 9 and above is affected. https://www.kaspersky.com/blog/spring4shell-critical-vulnerability-in-spring-java-framework/44034/ As we have installed JDK 11 in the latest Version of Mobicontrol, this would be affected. How can we eliminate this issue or are the mentioned Products not affected? Thank you and best Regards Beni
Hello, I was told from SOTI Support to open a new thread here, so that the question can be forwarded to SOTI product management. Basically, I need a SOC 2 type 2 Report regarding our SOTI Cloud Instance. It is planned that a customer will integrate their devices into our Instance, and the customer asks for that Report in order to finish their Security Assessment. The issue is somewhat urgent, so I hope for a quick turnaround. Thank you very much in advance!
We have some data hosted on GCP (Google cloud) and a API is published for the same. Can SOTI get that data and create a alert for all the devices in that network? If you can you please guide me to any samples or a documentation on the same. I am using Soti Cloud (version. 15.2.3.1033)
I am using a Honeywell CT60 with Android 11 with MobiControl 15.4.2.1020.Supported APIs: RC Virtual Display, Work Managed Device, Advanced Android Plus 1.18, 1402 The latest version of Wavelink Velocity is installed, together with VelocityFileAssistant to have a workaround of the Android 11+ restriction to access /sdcard/Android/data/ folders.This tool will copy files from the /sdcard/com.wavelink.velocity folder to the /sdcard/Android/data/com.wavelink.velocity/files folder.Now, this tool requires external storage permissions which can succesfully set over ADB as follows: adb shell appops set --uid com.wavelink.velocityfileassistant READ_EXTERNAL_STORAGE allowadb shell appops set --uid com.wavelink.velocityfileassistant WRITE_EXTERNAL_STORAGE allowadb shell appops set --uid com.wavelink.velocityfileassistant MANAGE_EXTERNAL_STORAGE allow However, when using the following legacy script, the permissions are not as expected, and a user does still need to move a slider to grant permissions in the Velocity File Assistent when started for the first time. afw_set_permission_grant_state com.wavelink.velocityfileassistant android.permission.READ_EXTERNAL_STORAGE allowafw_set_permission_grant_state com.wavelink.velocityfileassistant android.permission.WRITE_EXTERNAL_STORAGE allowafw_set_permission_grant_state com.wavelink.velocityfileassistant android.permission.MANAGE_EXTERNAL_STORAGE allow What am I missing here? Regards,Henk
Soti device licenses are expensive as we all know, and to limit the needed amount in our environment, we're tracking the "Agent Check-In time" and pulling devices from production that are not being used. However, an online device hooked on usb power that no one is using, will not be caught by monitoring the agent check-in time. Is there a way to track/monitor some custom data like, touch screen used X times, power button clicked X times, specific app openend X times the last X days? Or does anyone have a better idea? My environment:Android devices running Android Enterprise profiles.½ of my devices are used in warehouses meaning tracking the gps for activity wont give the data I need.Thanks in advance.
Hi, As the SOTI 14 end of life is near, we decided to initiate the process of upgrading our server. But first step (upgrade from Windows Server 2012 R2 to Windows Server 2016) resulted in non-working environment, and we were forced to restore our backup. The errors after server OS upgrade were following: We decided to clone our server, in order to test the whole upgrade (Server OS upgrade, SQL upgrade to 2016, and finally MobiControl update to version 15), but again after the first step we are receiving error. It is only one error this time: Please, advice how to proceed!
We have an alerting app on the Samsung SM-G525F devices, which displays the message: "Please allow novalert to break the 'Do Not Disturb' mode" Does someone know how I can I set this permission by scripting on the devices?
I have TC52x devices running Android 10 that are utilizing a custom Lockdown screen. I have a request to add a new link on the lockdown screen to an ordering website (not app) and it requires a new datawedge configuration. I've noticed the lockdown opens the website in what I'm guessing is a proprietary Mobi browser. Does anyone know the mobi browser app name so I can add it to 'associated app' in my datawedge profile?
Hello dear Soti Team, We are currently still optimising our installations for the Honeywell CT60 with Android Enterprise. We have two things that we currently have to do manually on each device and I wanted to ask if we could somehow automate them. The users don't like the standard Honeywell Enhanced Keyboard very much and prefer to use the Gboard keyboard, it's not clear why.We therefore have to deactivate the Honeywell keyboard in the settings on the device which will enable the GboardCan we automate this? And probably the harder part:We have created a custom attribute in Mobicontrol.There we maintain the so-called ME number, which is a number that is needed for registration within a software.At the same time, it is part of the PIN code of the device.To not confuse the users, we will display this number as a lockscreen message on the device.Each device has its own number, which we maintain both on the device and in the web console. Is there a possibility that we only have to maintain the web console and the device gets the information from the custon attribute and somehow inserts it into the lockscreen message? Thanks a lot and have a nice weekend Maik
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.
