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 locking down Android Enterprise phones to a few onscreen buttons. One is for action://CONFIGURE_WIFI We are finding that we are able to get to the settings and manually enter Wi-Fi name, but the scan does not work. Is there another corresponding setting that needs to be configured to allow the scan to work? EDIT: The actual cause of this is that the Wi-Fi scan does not work if location is disabled. Not sure why this is related but have been able to confirm this by testing.
ORIGINAL QUESTION After the reboot the MobiControl starts. Then the MobiControl starts Enterprise Browser. The Product Registration loads up and then a error alert box appears that says "EnterpriseBrowser has stopped" with a Open app again button below the message. Is this a known issue concerning the application loading before a wireless connection can be completed within the scanner OS? UPDATED ON 10/12/2019 Ran the RXLogger app on the MC93, rebooted the scanner and the error occurred. The RX Logger caught the error and logged it. It showed a null object reference error. I got in touch with Zebra and we determined that the issue was in fact due to the MobiControl Lockdown configuration. Zebra suggested that I use EHS (Enterprise Home Screen) but that app is not straightforward at all. Does anyone have any knowledge of using the Lockdown configuration that auto starts Enterprise Browser?
Hello, Our users are using a web app but every time their TC51 reconnect to the WIFI they return automatically to the lockdown screen (and they lose their current work...) We already disabled the "doze mode" as indicated in this thread: https://discussions.soti.net/thread/stop-returning-to-lockdown-on-reconnecting-to-server/ And we also unchecked the "Update when device connects" option as indicated in https://discussions.soti.net/thread/lockdown-closes-open-app-and-refreshes-lockdown-homescreen-when-network-connection-changes-android-8/ After some tests, we discovered that the lockdown screen appears every time there's a "Device (Agent) checked-in" and indeed there is a "Device (Agent) checked-in" triggered when a TC51 reconnects to the WIFI. As I understand, this is a security feature to force the device to return into "user mode". But in our case the device is already in "user mode"... Or maybe I misunderstood ? It seems that this problem started when we updated the MobiControl agent on our devices Zebra TC51. We need some assistance please. How can we avoid this return to the lockdown screen at every "Device (Agent) checked-in" ? We are currently using Server MobiControl 14.4.2.1307, Agent MobiControl 13.9.0.1046 and Zebra TC51 (Android 6.0.1) Thanks for your help. Frederic
Hello all My first post. I want to pair BT headset though NFC pad on terminals with a kiosk lockdown and the 3 notifications - Confirmation of pairing on terminal - Validation of association - access to calls history and contacts aren't displayed Is there a way to permit theses notifications to be display or that bluetooth pairing is done without confirmation ? If someone could help me :) Regards
I´m working with android enterprise in honeywell devices, such as eda71 and eda51, i enabled the kiosk mode and it is working fine in device owner mode, but i want to disable the status bar expansion because if not, the users can turn off the wifi or change other settings, but i need to see the status bar to check the signal and battery status, in android+ this function it´s shown in lockdown settings, but with enterprise configuration i only see status bar in activity supression. Thanks
Is there a possible way to use jQuery Modules (like alertify) in a Lockdown or Kiosk Mode ?
So I can't figure out how to get our app to auto upgrade on kiosk devices. I've got a Google Play store page set up for a private app, and I'm able to issue upgrades through the play store page. Next, I have to go into the mobicontrol cloud and update the application catalog, which isn't ideal, but whatever, I can deal with that, but after updating the application catalog, none of our devices will download the upgrade. The only way I've been able to get devices to upgrade is to remote control into the device in Admin mode, go into the application catalog in the DPC and upgrade the app. Moreover, there seems to be a bug with this scenario because after I upgrade the app with these steps, when I go to set the device back into User mode, the app will be uninstalled! I then have to re-install the latest app and then I will be able to set the device back into User mode. I've asked a sales engineer that has been helping me out some, but he's not very responsive and hasn't provided any information on how to get the app to auto upgrade. There was a Droidcon Berlin talk just last week I think about setting devices up in kiosk mode and through their own setup they were able to get apps to auto upgrade, plsu they were also able to use the test tracks in the Google Play Store. I've been trying to use the test tracks of the private google play store app for a while but Soti doesn't have any information about that either, and that probably deserves another question, but I know it's doable and getting the app to upgrade should also be possible. Is it possible to get these private apps to auto upgrade without having to log into each one and manually doing it? Thanks,
Hello, I'm wondering if there is a good way to query the EMM device details from an Android app in lockdown mode. For example, we would like our Android app, that is launched in lockdown mode, to get the device id, found in the device details in the console, and send it to our backend. I haven't found any good direct way to get this info from our app. The only idea I came up with was to have a script run during enrollment to create a file on the sdcard card with info and then have our app look for and read from this file to get the data stored. I'm not even sure if it's possible to have the script get the device id or device name, or if there are other issues with this process. I also thought I saw that there was a way to broadcast an intent, and maybe we could broadcast the info we want for our app to pickup and parse..? Maybe there is a way for our backend to query the Soti api's and somehow get the info that way? I'm relatively new to Soti and pretty much still in the evaluation stage, so I'm still feeling my way around the features. Any help or pointing me in the way to find the answers would be greatly appreciated. Thanks, Sterling
Hello Can anyone help me with my Problem? I use lockdown page to start soti surf. When i go back to lockdown Screen and open Soti Surf again, Soti surf everytime open a new tab with startpage. Is there a Chance to open only 1 TAB in Soti Surf?
Hi all, Looking for feedback on some best practises regarding the disabling of a device, in this case an MC40 for a user. Current options would be: 1) Factory Reset - this would return the device to it's original state, but leave the device open for the user to connect to WIFI, use camera, change settings etc. Trying to avoid this if possible. 2) Uninstall all apps, apply generic blank MobiControl lockdown profile. This leaves the MobiControl profile active and communicating back to our deployment servers. Not sure if this is what I want to have happen either. 3) Uninstall all apps, set a different device PIN and then uninstall or wipe the MobiControl application as the last step in the process. Option 3 is what I'm currently considering but does anyone have any better recommendations?
Hello all, we have mobicontrol on version 13.3.3454 we have device zebra tc75x on version 6 with agent on version : 13.6.1476 enrolled by android + we have profile with lockdown and authentification. That's work fine. After an audit of security some users can by pass the lock down by just press the COMA on google keyboard. I join a print screen of the step. Anyone has some idea about how to find a solution for this ? what we can do ? thanks for your time
Hi We have a small selection of Samsung Galaxy Tab Active 2 devices that have been upgraded to Android 9 (Pie) (there's another thread asking how I stop the upgrade and that has been resolved). These devices have been enrolled via Android Enterprise and are running agent version 13.7.3.1045 Our servers is on 14.1.4.1693 The devices have Kiosk Mode enabled (it's a legacy thing, don't judge). Can anyone think of a reason why when the user clicks on MobiControl from the kiosk screen it will not open (goes black screen then returns to the kioskscreen). If you administratively remove the kiosk then MobiControl opens as normal when clicked on and the users can access content manager. The app name is set up correctly in the Kiosk Mode settings and works properly on Android 7 and 8.1. All suggestions welcome. Eddie
We are using Zebra TC70x GMS devices running Android 7.1.2 and 8.1 with MobiControl using work Managed device and Lockdown Mode.The devices are connected using WiFi and with Secure Pulse VPN to connect to our network. We use Managed Google Play applications and app config to get the for automatic app installation and configuration. We also have Always On VPN enabled, we have set net.pulsesecure.pulsesecure in Feature Control, Always On VPN settings.We face two issues:- Always On VPNIf we enroll a new device or move a device between groups without and to Feature Control (and Always On VPN) enabled, Always On VPN connects automatically. But if we reboot the device it won't connect and go Always On (manually clicking connect works).After a reboot and the device going into Lockdown Mode, we can see a Secure Pulse icon in the notifications bar showing the VPN service is running. A couple of minutes later another icon is added showing a user certificate error message (unable to access users security certificate). Again, clicking Connect manually works.- Device offline with Always On VPN setting enabled in Feature ControlWe are unable to contact devices in groups with Feature Control / Always ON VPN enabled. In the MobiControl app, Agent status blinking Connected/Disconnected. Switching from Lockdown Mode to Admin Mode works, Agent status is Connected.If we move the device to a group without Feature Control / Always On VPN the device is connected, the same goes even if VPN is manually connected. This to me confirms the offline issue is related to Secure Pulse Always On VPN and MobiControl.We have allowed VPN traffic based on the recommendations below. MobiControl Deployment Server Note: For deployments with multiple deployment servers, for caching purposes. Binary 5495 MobiControl Management Server Binary 5494/5495 Google Play HTTPS 443 Remote Control Binary 5494 MobiControl Console Remote Control HTTPS (web sockets) 443 Agent version: 13.7.2 Build 1015Thankful for any ideas how to approach these issues.
Hi, I'm locking down a Samsung Active Tab 2 with the Andorid+ SOTI agent. Its running SOTI Surf in single app mode and I would like users to be able to change certain settings from the status bar but not others. I'm able to disable the settings I don't want user to turn on with feature control, but I cant find a way to allow users to change the brightness and rotation settings while at the same time not allowing them to turn off the wifi. Is this possible? Thanks
Is there anyway to stop the lockdown screen exiting all apps on reconnecting to the SOTI server? Our devices (TC75) are out on the road, and the users are using an app, which when the device reconnects to the server after losing signal, lockdown closes/hides the open apps and returns the user to the lockdown home screen. This is a pain for the users. I've seen this happen while on remote control, be using the app. the device goes offline and when it reconnects I see the lockdown, and the app has to be reopened - normally remembers where the user was, but sometimes closes the app completely. Thanks for any suggestions. Gary
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.
