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.
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
Hi everyone, Currently in SOTI Mobicontrol we have default setting for Update Schedule, usually it's every 2 hours, and everytime the device check in, it will looking for update and do Locate device location. I was wondering if the device location when doing check-in can be shown to us? For now i just can check the log and see that "device located" Is there a way to see the location? Thanks & regards, Randy Saputra
We are migrating from wince devices to android. And the browser we are using in the wince device is behaving different comparing to soti surf. In the webpage there are multiple input txt lines. The end user has to fill this in with nrs.In the win ce browser: the user types and when the field is full of characters the cursor moves to the next field and the user can keep typing.In Soti surf: the user types and when the field is full he can't type anymore and has to select or tab to the next field.Is there a way to configure soti surf so that the user does not have to manualy tab or select the next field? The page consists of a lot of input fields and it would add a lot of extra work for the end users.
Hello, I want to update the Memor K with the newest Android Update. I found the intent: intent:#Intent;component=com.datalogic.systemupdate/com.datalogic.systemupdate.SystemUpgradeService;i.action=2;S.path=/sdcard/MemorK_Update.zip;i.reset=0;i.force_update=0;end; But this intent didn't work. The Device show me a that the activity couldn't be found. I created the intent in the Lockdown. Can someone help me in this case? Best Regards Simon
Hello everyone, I have a problem when enrolling a Samsung A02 device, I have tried to enroll using the AFW and QR CODE methods but the results are still the same, namely ELM status pending, I have tried sending the reset_elm_license script but it doesn't work, Is there another way to solve this problem?
Good afternoon, We have several Zebra TC56s/TC57s that run either Android OS Version 7.1.2 or 8.1.0. Between all of them, I see several different DataWedge versions. I tried looking it up online but I cannot seem to find what determines what DataWedge version is running on these different devices or how to force update them. Is this something I can do manually or is there some sort of process I can perform to get these on the same version? These are Android Plus devices. Device Android OS and DataWedge combinations TC57 - Android 8.1.0 - DataWedge 7.4.44 TC57 - Android 8.1.0 - DataWedge 7.2.5 TC56 - Android 8.1.0 - DataWedge 7.0.4 TC56 - Android 7.1.2 - DataWedge 6.8.50 TC56 - Android 7.1.2 - DataWedge 6.8.54 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.
