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.
Hello, just a little background story: We use certificate based wifi auth., when installing a cert without a device plugin the agent does a "ring tone" and asks the user for permission when there is no pin code set. We set a pincode automatically via script and also the deviceplugin is installed. Now when the device gets to the Wifi-Profile it does the exact same behaviour as without a pin code and deviceplugin for a short period of time untill the device has fully installed the wifi profile and could connect to the wifi network. This ringtone that comes up when the agent asks for permission i.e. cert installation now starts randomly and then device keeps ringing for like half an hour or longer. the thing is that neither wifiprofile or certificate need to be refreshed or reinstalled. Has anyone of you experienced this before and what was your solution? Running on: Agent 14.4.4.1051 MC 15.3.1.1151
Hi all, I'm trying to set a dynamic URL in SOTI surf through a custom attribute. Creating a custom attribute "WachtZaal" in the device settings page, type "Text" + option "send to device". On the device, I fill in the custom attribute with a value. In SOTI SURF, I configure the URL with the custom attribute: device_id=CustomAttr:WachtZaal&token When launching the SOTI SURF app on the device I get the warning: kiosk device CUSTOMATTR:WACHTZAAL not configured wich means the program can't find a device called CUSTOMATTR:WACHTZAAL in his configuration. So it seems that the custom attribute is not being replaced with its configured value. Any advice? Device is a ZEBRA CC6000 with Android 8.1.0 / Agent Version 14.5.1
We have received some A32 to be enrolled in our MC 14.4.4.1045. After we set the afw#mobicontrol it starts to download the MC Agent (now it is 14.5.3.....) At this time we receive a message telling the Operational System is not original. (It is not possible to create the work profile. The security policies denies to create a managed work device, because a customized Operational System is or has been installed on this device). The OEM Version of it looks as original (RP1A.200720.012.A325FXXU1AUF2) The mobile is just out of the box. As it is Android 11, we are enforced to grant permissions individually to the Agent, before it goes on (access any file, manage system and so on). If we go forward the Agent install but at the time to create the google account, it hangs on the PlayStore account requesting to recreate account by identity confirmation: (Confirm who yo are. You log off google account , please log in to continue). On the next screen it does not allow to type in any entry. And Click on next, it fails. After hanging in this screen, we have tried to go by download the MC Agent from the server. Then we have proceed by a factory reset and skip google account. Installed the agent by our server. The issue starts as it comes as Android instead of Android Enterprise(the download agent was Enterprise). And again, it does not create the google account, presenting the screen as pending action to create a work profile in the device. (Work Profile Provisioning. Click Here to configure a work profile). It never creates the work profile as the click had no effect. Has anyone had a good installation for Samsung A32 ?
Hi all, I'm currently using Android Enterprise - Work Managed devices, with Managed Google Play Account... Mobicontrol version 15.3.2 I have a selection of Add device rules set up and all have the Permissions set on the Rule like below: However at enrolment of the device, I'm experiencing a mix of results and not sure why. For example, once the device is staged as AFW - its on the enrolment screen waiting for a code. We use Mobicontrol Stage and scan barcodes created from the Enrolment ID. This then prompts for username and password (we use ldap authentication) and then it prompts for the Password Policy we set and moves onto the kiosk/lockdown. On some devices, this proceeds and there are no further pending actions. All policies, apps, etc download and the device is enrolled and compliant. However on another device, same model, same staging but perhaps a different Rule - with the same Permissions set - we get prompted in Pending actions and have to manually accept each one and toggle Mobicontrol. I have gone over the Rules and aside from the target and ldap groups these are almost carbon copies. All have the tickboxes set but I'm confused if they mean it should prompt, or should auto grant these? Little baffled on why some do it but not all... Is there something at the profile level that has an effect, or maybe something in feature control that conflicts with this that I'm potentially missing? If anyone can help and offer the intended action it would be much appreciated as we may need to update documentation for user enrolment asap. Many thanks Leigh
Hi, It is my first post so apologies if I'll do anything not correct. We're using Mobi Control version 14.4.9.1034 and the query is for Samsung A02s, Samsung A12, Moto G6 and G8 devices enrolled as Android Enterprise. I'm after a post install script on File sync rule to enable 'Allow permission' function within Change system settings for certain application. We will need in near future to update this application every month or so. I have attached a screen shot to provide more details what I'm after. Please let me know if it is possible or if any further details I can provide. Kind regards, Norbert
By starting the enrollment for Zebra MC3300 devices with OS Android 10 the message "Enrollment failed" is displaed on the screen. In the trace files of Mobicontrol I can see the following error message: ****************************************************************************** * Exception: Failed to delete the device 'f375db664e6b050142d25cff8dc60811'. * ****************************************************************************** [FaultException`1: Google.Apis.Requests.RequestError No device was found for the given id. [404] Errors [ Message[No device was found for the given id.] Location[deviceId - parameter] Reason[notFound] Domain[global]
Hi, We've got a large number of android enterprise devices enrolled, which is done through the OEM provisioning process (Honeywell). As part of this enrolment, I target a specific AE SOTI agent version to keep the fleet consistent. I'm struggling to understand why there are devices in our fleet that will upgrade their agent version, passed what's been allowed in the console settings. For example, the current 'compatible' local agent version in our console is 14.4.6.1001. The latest version not yet authorised is 14.5.3.1017. All of the device have Agent Upgrade Enabled set to false, yet some of them randomly update to this new version? I'd like to authorise and deploy the agent version in more controlled fashion as we've run into issues with particular agent versions in the past and am reluctant to just let them always install the latest version (at least until it's been tested by us). I don't believe anyone in our environment (administrators) has ever issued the "Start on update schedule" option within the agent update options however couldn't say for certain. If so, how would that setting be counteracted? I've issued the "Disable Agent Upgrade" command which won't go to any devices that have the new version (regardless of whether the console has it marked as compatible) due to it being the latest official released agent (which seems quite strange behaviour to me). Does anyone have any suggestions? Cheers! Rob
Trying to add approved Google Managed Apps to specific Enterprise Binding and get "Internal Server Error." Logs show Out of Contact policy didn't configure, Connection to %^@@.mobicontrolcloud.com, Device connected to server. I started over and added a new policy (no clone) and get same results.
afternoon everyone has anyone ever seen this message and know how to resolve?
Hello everyone, My Samsung A01 device was running in Android 10, but since there is update, now is running in Android 11, and after update i found out RC become Remote View only. Is there anyone have same experience here? Is it supposed to running Remote View only in Android 11 ? Thanks & regards, Randy Saputra
Hi, We've just recently provisioned another large quantity of Android Enterprise devices into SOTI and our current preference is that the devices are named in the console with the companies asset ID. Normally we'd have to go through and manually use the scripting command to send the 'devrename' command with the new name to each device individually, however this is time consuming and very labour intensive to do for large quantities. Is there a way to send a bulk script to update these? Currently these devices are enrolled with their serial number as their name, so the script would contain device serial and new name as a mapping. Does anyone know if this is possible? Cheers!
We would like to command the lock and unlock device directly into the MC Console as also to install and enable the Knox Guard with no end user interaction. So far, we send a link by script that is opened in Surf and end user has to click next and accept on it. Is there a way to install Knox Guard and activate it directly from MC Console ? In positive case, where should I find a guidance to it ? Is there a way to define the lock command from MC Console to be propagate to konx guard console, releasing the tasks to do it on both console ?
Why is it that some applications do not get removed from Windows Desktop Classic Device?
After updating to Android 10 from 9 on my CK65 devices I've noticed I can't swipe up from the bottom of the screen to do an administrative unlock from the Lockdown screen anymore. If I go into Remote Control I can force it to administrator mode from there, but not directly from the device. Did something change with this?
Hello, I manage our field team's Samsung S20 devices and some of our current applications require us to remain on Andriod 10 as there is currently some incompatibility with Android 11. We will be wanting to upgrade when this is solved for security reasons but ideally, I would like to be able to limit user's ability to upgrade and instead push safe updates out to the field when they are tested. I am hoping there is a new solution to this but so far I have not seen anything. Other than moving over to the Samsung Knox suite that does appear to have this functionality. So for now I have been using this script to stop the updates. "writesecureprofstring DeviceFeature BlockOsUpgrade 1" Up until now, this solution has been working, however, if any changes are made to profiles assigned to the devices the fix is undone requiring me to send the script again. If this is not caught, then the device is left vulnerable for the automatic updates to start downloading. Once they are downloaded we have to factory reset the phone in order to avoid it asking to start the update every day. Any ideas why this is happening? I am not making any changes to the feature control, even moving devices between groups will reset the OS upgrade block. At device enrollment, I have also set a task scheduler to send the script but this seems to be ignored, not sure why this is but it means enrollment has 1 extra manual step. I have considered are using a task scheduler to send the feature control script every couple of minutes but this seems like overkill and I would rather a cleaner solution. Does anyone know of any other workarounds? Thanks in advance
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.
