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.
Greetings, We currently have Zebra TC52's and Samsung Galaxy Tab A that we enroll with no issue and use our Managed Google Play store, but our Zebra TC70's were AOSP devices and were unable to take advantage of the Managed google play store. I have upgraded a TC70 to Android 5.1.1 and switched to a GMS build, following Zebras release note instructions. When I try to use the AFW#mobicontrol tag in the device setup I am prompted with "Android version on this Device is not compatible with work accounts." Everything I can find says that this version of Android should be supported. Is there another avenue to getting these devices on our Managed google play? Are specific devices potentially not supported? Greatly appreciate any insight, and please let me know if I can provide any additional information. Thanks!
Hi We're using SOTI Mobicontrol on Zebra TC56 and VC80X with Android 8.1. I have the devices locked down and only allow one custom app. This app uses a USB camera and a USB RTK GNSS receiver. The problem is, every time the Zebra is rebooted, it asks if I want to allow the app access to the USB devices. Checking the box "Use by default for this USB device" doesn't help as the camera gets a new ID on every reboot. Is there a way to auto allow access to USB devices, or to disable the USB security completely so the user don't see any dialog boxes? Also, it asks if I want to automatically open the app when the USB device is connected, It would be nice if I could get rid of this dialog box as well.
I already installed the latest RC Hawkeye plugin but still the RC control is not available. I tried multiple times to send some legacy script based from other discussion like below but with no avail. _resetfailedrcdetectionflagSleep 2restartagent and __switch ENTERPRISE_41 VIRTUAL_DISPLAY_resetfailedrcdetectionflag The device is currently running the latest update from Zebra, 02-32-04.00-OG-U07-STD I also tried installing the legacy RC plugin but the installation fail. The same also happen to one MC93 device we have running 8.1.0 with 01-23-18.00-OG-U00-STD. But the MC33 we have work perfectly fine with the RC plugin, this run 8.1.0 with 02-32-04.00-OG-U07-STD Agent Version is 14.4.0.1028 for all 3 devices.
Hello everybody I have a problem to enroll devices under android 10I have a message that says "failed to connect to the server. SSL negotiation failed. And i have one message on my server who said me this: Can you help me please?
I found this option but it needs to be done to a whole folder and when I put a unit in the folder it does not work I am Using Zebra tc56 and Android 7 to 8
Hi What's the correct path for a classic application? In the configuration screen I can add Classic and Modern apps but the application path is always invalid. Same happening for all classic application I trying to add. Even the AUMID path for a classic app don't work PowerShell: get-StartApps Name AppID Microsoft Teams com.squirrel.Teams.Teams Zoom zoom.us.Zoom Vieo Meetings
I would like to know if there is a need of a "Maintenance Mode" to be set on devices via SOTI MobiControl? I was working remotely on some devices (Android) the other day and suddenly someone was fiddling around with the device causing challenges to perform some needed activities. These activities were not time consuming however due to the user interaction on that specific site we couldn't finish a task to check an issue on the device. - And I was thinking, why on earth can I not lock this device down for the end-user... Other scenarios would be if we from an central perspective ask for a short change window in a certain site to e.g. deploy one or more application updates or an longer activity in terms of updating an operating system version on devices. What do I mean by Maintenance Mode? Displaying a message on the display saying that this device is undergoing "Maintenance" and that it should be put back docked/inserted to the Charging Station if not being there already This mode shall present somewhat of a locked down state to the user in order to block the end-user to select or press any buttons to use applications that was present with or without a locked-down screen in order for the maintenance to be processed without any interruptions It shall; a) take over or be placed over a current locked-down screen b) prohibit an end-user to interrupt an administrator c) allow an Administrator remotely to check devices with the "Maintenance Mode" still being active for end-users How shall we as administrators activate Maintenance Mode? Possibility to right-click and set maintenance mode on; a) single devices b) selected several devices c) on a folder Maybe there is a solution for this already "out of the box" within Android. Then please let me know! Feel free to add to this topic. If SOTI cannot resolve this I guess they have to work with Google to resolve it in a joint operation when it comes to the Android operating system.
In our driver app, our drivers hear notification sounds for tight turns and other dangerous parts in the neighborhoods.We are using Soti as a trial now on 1 location and we see that these notifications don't play. For us its really important that these notifications do play as drivers are being judged on their driving behavior.We are using Version: 15.2.1.1094And the devices are in a lockdown profile with only maps, the dialer and our driving app.Is there a way to make this work.We see that this only happens on devices with SOTI
I am operating a Zebra TC75 running a lockdown configuration. There is an application that we need to be able to pair to a bluetooth printer from within the lockdown mode. However, when the TC75 attempts to pair with a bluetooth printer, the android system pop-up to verify and accept the bluetooth pin does not appear while in lockdown mode. The pairing function has been tested and the pop-up does appear when in admin mode, but it appears as if the pop-up is not allowed to appear during lockdown. The audible chime is still happening to signify that the pairing process has started, and there is even a notification banner at the top of the screen signifying the process needs interaction, however, the android dialog does not appear over the application like it would when not locked down. Are there any scripts or permissions that need to be granted to allow this to appear?
Hi, We have a device that's been used in kiosk mode, but sometimes the application is faulty which can be fixed easily if we clear the soti surf cache. Is it possible somehow to let's say run a task that clears the cache daily? Thanks
Dear Soti community, since about 2 weeks I have trouble to install new devices. I use the same WiFi settings since about 6 months. I also talked to my colleagues from the internal IT network department - "They changed nothing at the WiFi infrastructure." My setup: Test-System - SOTI MobiControl 15.1.3.1021 - Agent: 14.1.5.1059 Prod-System - SOTI MobiControl 14.3.2.1171 - Agent: 14.1.5.1059 Here are some infos about my test devices:- Honeywell CT60 (Brand new device and already existing device9- Android 8.1 Build 129- Android 8.1 Build 180 Device Config (both staging profiles): As I said - I use this settings for about 6 months. After scanning my barcode, my normal device settings are applied first. After that a "Wait for network" task is running. Here is the problem: Sometimes the CT60 device use the connection for about one second and disconnect form the WiFi connection. Then the device is retrying to download the device agent again and again... 2nd scenario: The WiFi connection will be not established. In both cases the WiFi symbol is briefly displayed in the upper right corner and then disappears. However, as soon as I manually configure a device and also manually enter the WiFi settings, I can easily authenticate to WiFi and the connection remains established. I hope somebody of you had such a problem before and can help me. Of course the colleagues from the network department say that it is because of MY barcodes and configurations. But I can't imagine it, because these settings worked without problems for more than half a year now.
Hi. I have a trouble with enrolling devices to my SOTI server. Here is a screenshot with messages which I can't get rid of and enroll any device, using google mdm account in SOTI. Device: Samsung J5Android version: 9Knox version: 3.4Playstore version: 22.4.25-21Soti Server version: 15.1.0.3413 Soti mobile version: 14.1.4 Build 1010 At the beginning, there were any problems with enrolling device. I've could enroll more than 50 device in the same day.Later, only 10 a day. Next day there were no problems to continue enrolling.After few weeks, only one device a day.Now, I can't enroll any device. Sometimes, I need to wait few days, sometimes more than a week to enroll.This problem started from June and still persist. There is no any problems with SOTI license or Samsung ELM, because device is always succesfully enrolled without google account. What i've tried:- create a new rule with another mdm google account and enrolling device: success.- enroll device without google account: success.- reboot server, reboot device: still not working.- check if hash for mdm google account is the same. Are the same, but device still stuck in same message. - enroll devie in another server and without google account: success.Is there any google account limitations for how much devices you can enroll via MDM? Thanks.
A problem has been identified with your MobiControl environment. SOTI services are not available at present. How can I get pass this error ? From the server itself, I'm able to telnet to the required SOTI services via port 443.
Is it possible to change the default remote view from Portrait to Landscape in MobiControl?
Hi, Hopefully a simple one.Running Mobicontrol Version: 14.4.9.1034Device = Samsung Tab Active (Android 9) - Agent version 14.4.0 Build 1028When creating an Enterprise profile and adding an Application Run Control configuration there is no option to create a whitelist. The drop down is greyed out and not available. Is there a reason for this?If the profile type is set to Android Plus the whitelist option becomes available but is ignored when pushed to an Android Enterprise device as part of an Enterprise profile. 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.
