There's a new home for Articles. Find Articles on Our Product Support Page.
I have android 7.11 devices being enrolled onto MobilControl 14.1 via Android Enterprise Required (non-default) apps are applied via Application Catalog, all well and good All pre-installed apps (most notably the camera and Gmail) are being uninstalled (or at least hidden) The profile initially used did not have Application Run Control enabled. I have since tried setting that up to no avail. I can force enable the camera via the enable_system_app script command but I don't want it to be gone in the first place. What am I missing please? Gmail could go in the App Catalog but it's already installed. And that does not solve the loss of the camera. Cheers
i enroll windows 10 ,but is eror : this setings have not been aplied properly due to other related seting failure a privisioning failure has ocured
Here are a few suggestions I have for improvements to the forum. Please feel free to post your additional suggestions below, maybe this post could be stickied? "Sticky" Posts if those are not already supported. A knowledge share / repo area to share your favorite scripts and script combinations A shared repository of custom lockdown HTML where people can show off some of their creations and get tips from others Community contributed articles Polls. I'd like to poll the community to query things like Device Owner vs. Device Admin. Zebra vs. Samsung vs. Honeywell,. File Sync for Firmware Update or Package Distribution?, etc. Specific sections. Tagging is good, but having an Android Enterprise section separate from Android (Legacy/DA) would be valuable.
Hi, We have a couple of users experiencing battery issues recently, which they believe is related to MobiControl. Are there any known issues? We are using the latest agent version. The phones in question are Samsung Galaxy S5 Minis Their MobiControl runs automatically every time they turn on the phone, is there a way to stop this and only have it running when manually opened? Thanks
Is there a way to disable this notification? it even pops up in a new window when performing certain actions like editing an enrollment rule and is very intrusive. The application's use case is often to manage a set number of devices, no more and no less. Of course the max number of licenses are being used, who would pay for more license they wouldn't use? Can i disable this notification/announcement? Also, i have seen a popup asking me how likely i would be to recommend SOTI to a friend, which while i understand the purposes of that feedback, is not exactly appropriate in a professional enterprise device environment. I hope there are some options around the notifications that are allowed/disallowed that i have not found yet.
In the Android Plus Profile creation there exists an option in Feature Control to Block OS Upgrade. However, in the Android Enterprise Profile there is no such option in Feature Control. I tried issuing an Android Plus profile along with the Android Enterprise ones, but it doesn't push down to AE activated devices at all. So, am I somehow missing this feature control option, or is it something in development to be added at a later date?
Using Soti 14.1.2 and enrolling Zebra Android TC8000 devices, when enrolling the devices using the naming convention i specified (Device %AUTONUM%) in the enrollment rule, but the autonumber seems to increment in twos or sometimes threes instead of ones. Has anyone else seen this issue?
Error sending message (Error sending DEVICE_SCRIPT_MSG (Connection not established)) (Error sending DEVICE_SCRIPT_MSG (Connection not established)) in deployment server multiple time I am getting
I'm struggling to find an answer to this. Is there a document or list that outlines the different functionalities of Mobicontrol for iOS and Android.
Does Soti have the ability to restrict profiles and packages from being applied over cellular? We have a bunch of Zebra TC-56's and we want them to be able to contact the server when they are out on the road via cellular so we can remote control and locate them, but we do not want them applying packages because it chews up cellular data. Instead we would like the devices to wait until they are back at our buildings on wi-fi to perform package installations and updates. Is this possible via built-in Soti functions or even some scriptable work around?
When we manufacture our Android devices, one of the steps is enrolling the device in the Soti MDM. This enrollment is done via an Ethernet connection. We have recently modified the agent version that is bundled in our OS image from 13.0.0.33835 to 13.5.0.1088 and there appears to be a behaviour change. We are now seeing all devices attempt to enroll with a device id of 00904c112233. If we instead connect the device to Wi-Fi before enrolling, then the device id appears to be unique for each device. Has there been a change in the algorithm that the Android agent uses to generate the device id when enrolling? If so, I have two additional questions: is there any way to ensure unique device ids without connecting to Wi-Fi? is this behaviour the same in more recent versions of the agent (if there are any)? Steve...
With which version of Soti MobiControl can we have this operation
Hi All, about this thread https://discussions.soti.net/kb/mobicontrol-in-countries-using-decimals-as-commas-cannot-locate-devices-issue, I don't see the fix on release notes v14.1.2 how suggest by the same thread. Thank you,Filippo
Hello! Who knows, which security rules are responsible for viewing assigned profiles on devices? Have 1 added directory Security Group, what in another Mobicontrol Security Group, and don't know which global permissions should be added for viewing assigned profiles.
Hello, Is is possible to disable the automatic updates of apps installed as mandatory from Google Play for Work ? Thank you
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.
