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.
Is there a method for disabling Play Protect beyond these two scripts? I have tried both on an AEDO TC52 and neither seem to disable Play Protect. I am running Agent version 13.7.0 Build 1031. writesecuresetting -glo package_verifier_user_consent -1writeprivateprofstring DeviceFeature DisableVerifyApps 1apply featurecontrol
Hi, Is it possible to deploy a kiosk on a device when enrolled using the generic android for work agent? I'm using the Zebra TC77 with agent version 13.6.0 Build 1928. MobiControl version 14.2.3.1069. The error message I'm getting is "Profile version 2 failed to install, because all of its payloads cannot be installed." The only configuration on the profile is the lockdown. Type of profile is Android Enterprise. Thanks Josh.
Hi! I have looked at the different posts about this and also in the documentation and the scripts documentation. I can´t seem to find information about the specific 90 days block that by all the information given by Google and SOTI, should be able to be deployed to the devices running as a Work Managed Device. Is this sent with the set_system_update_policy command or a FeatureControl script command? And is there any way of checking how many days left on the block?
Hello all, I am having an issue that I can't quite seem to figure out. We have a Progressive Web App (PWA) running inside of SOTI Surf that is accessing the tablets camera in order to scan barcodes. When the page comes up, the camera is shown but inside the "Select Camera" dropdown list, it shows (no Permission). Since the Camera was showing, I didn't think much of it. After about a week of just letting the device sit idle, I go to launch the page and where the camera box would normally be, there is a gray box with an X in it like it won't load. Any idea why this is happening? I originally thought it was permissions inside of SOTI Surf but I'm not so sure about that now.
Hi! We have configured the SOTI Surf on several devices but after an upgrade of the MobiControl Agent to one of the latest versions, we got problems with using SOTI Surf. The application won't get past the splash screen but it will also start flickering and head back to the lockdown instead. This seems to be some kind of problems with a permission?? Devices used in this case are Zebra ET50 and enrolled as Android Enterprise Managed Device, and we are installing the application with StageNow XML instead through Google Play or package deployment.
Hello all, I am working on a tablet configuration that will access a website that is being developed by a company that we have hired. The website requires the camera in order to scan barcodes. I have a configuration set up on a Lenovo P10 device which includes AFW and a lockdown Kiosk Mode. We tried to use Chrome as our web browser but we don't want the end users to be able to access the address bar or anything else involved in the top menu. The website works in Chrome though. That is when we decided to use SOTI Surf instead. Now when we navigate to the URL, it says "Camera (no Permissions (X))" but the picture comes up. After about a day of downtime, I will try to access the same website with no picture in the picturebox. It's as if Surf has realized that it shouldn't be allowed and then blocks it. It only starts blocking it after a certain amount of time. (usually overnight). Any suggestions?
Hello, is there any possible way to enroll fully managed android enterprise devices without having the device connect to google services? We do not want to give Networks / Devices direct access to Google-Services, maybe Stagingcradles with Ethernet are possible but the best Solution for us at the moment would be direct enrollment through our on premise mobicontrol server or a dedicated mobicontrol service. And are there options next to the token identifier afw#mobicontrol to install the agent as fully managed except for nfc/barcode etc.?
This post has three main questions. First, I would like to be able to install/update apps automatically on Android+ devices. The majority of these apps are available on the play store. I created an application catalog rule and added apps from both the managed Google Play account and the normal Google Play apps. Google Play store apps are showing on the device, but the managed Google Play apps are not. These are COPE devices so we don't want to use the regular Google Play store method since the users will be able to install any apps they want. Second question involves upgrading MobiControl. Since it's on the cloud I know I'm supposed to contact support and I have done that last Wednesday I think, but still didn't get a reply. But I need more information about the process before starting since it's my first time. Do I have to specify which version I want to upgrade to or do they always upgrade to the latest version? How long does the upgrade take? Is there any downtime or lost data to worry about? Can I take a backup? How will users be affected by the upgrade? Lastly, does Soti MobiControl require some form of root access to the device? I think I know the answer to this but my manager asked me so I figured I'd ask on here. The reason being is I was testing the Android Enterprise agent on one of the test devices and it wouldn't complete the configuration because I kept getting a "custom OS" error. I looked into it and found posts on here saying it's got to do with the device being rooted at some point in time. I dug deeper and read about Samsung's Knox warranty bit which is like a switch that once triggered cannot be switched off. Samsung's official solution is to replace the motherboard which is expensive and frankly environmentally irresponsible, but that's not the issue here. I discovered that our other test device also had this Knox warranty bit triggered and so far, every device I checked has it triggered which means I cannot install the Android Enterprise agent on any of them. So I'm just trying to rule out the possibility that it was caused by MobiControl. Current system info that might be needed: MobiControl version: 14.1.4.1693 (on cloud) Agent version: Samsung ELM 13.5.0 Android version: 7.0 Nougat
I just enrolled 1 Zebra TC52 (DO) with google enterprise profile. I have created a configuration profile to install an apk. Is there any option to force apk installation without the need for user to accept installation ? thx. steve
I just enrolled 1 Zebra TC52 (DO) with google enterprise profile. I have created a configuration profile where I need to block camera (via feature control). The camera stills not blocked despite profile has been applied to device. Any Idea ?
HI Guys, Does anyone know the script to turn off the Print service option on Samsung phones since the last Android update?
Does anyone manage honeywell dolphin devices? I am trying to push out a package containing EZConfig XML settings however the devices (CT60) have to be in provisioning mode to have the settings applied. I assume I can setup a pre and post install script in the package to enable and then reboot the device? Does anyone know the script string to enable honeywell provisioning mode and trigger the update? Seems like "watchsettings on" is not supported on these devices as they are enterprise not plus devices.
I am looking for strategies that others are using with MobiControl for handling the installation of firmware and patches from Zebra (TC77 running Oreo and AE). How do other handle it when you could have multiple patches that need to be installed on shared devices (in a certain order at times). I am managing 6000 devices at 300+ locations in an environment where local management does does not keep an active management of devices, thus a device could be offline for several days or more. Thoughts?
Hi all, I am testing SOTI Mobicontrol 14.3 and testing enrolment of AE smartphones. When testing LG smartphones (K4/K8/K9), the smartphones are encrypted, factory reset or straight out of the box, they are failing to enrol with the following SOTI Agent message; "Enrollment Failed. This device is not SafetyNet compliant. Please contact your system administrator." I know I can simply tick the box to still enrol the devices but that would defeat the point of the SafetyNet feature. Has anyone else hit this yet? I will check this with SOTI later today. John.
Hello, new mobicontrol install and I'm working out the best way to enroll out of the box devices (android enterprise honeywell CT60). If I manually setup with afw#mobicontrol I get the minimal set of installed applications as mentioned in links below. However it looks like the manufacturer camera app "snapdragon camera" (org.codeaurora.snapcam) is removed completely rather than just hidden (can't see it in device details application list) so cannot use the enable system app script for that bundle. If I use the Stage Programmer app to setup a QR code and scan that with an OOTB device, it enrolls and provisions, however it does not seem to hide/remove any default apps. So, I'm left wondering the best way to proceed. I like the simplicity of the Stage app, and would like to keep the OEM camera app, however there are other default core apps I would like to hide - is there a script to hide apps, or can application run control hide apps or does it just prevent launch? Mobicontrol device details indicates both devices are "work managed devices" with same agent versions but with a different outcome re. default core apps visibility/install status. Is this a bug/version issue or caused by the way I've set things up? Kind regards, Similar topics: https://discussions.soti.net/kb/why-are-some-system-applications-hidden-after-i-provision-into-work-managed-device-mode/ https://discussions.soti.net/thread/core-apps-being-removed-android-enterprise/
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.
