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, 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
Hello everybody, I wanted to make the following query about the Android update system through SOTI. We are implementing a system, in which, during several days of the week, the update file would be copied to the various terminals, and on a different day the update would be installed. The problem is, that during the tests we had a mishap, according to the logs of the SOTI rule that is responsible for copying the files to the terminals, this file had been copied correctly in all the terminals, but on the day of execution, We checked that only a certain number of them had been updated, we checked the terminals and to our surprise, they did not have the update file copied but in the rule logs it appeared the opposite. At this point, I thought about using an .xml file to create a custom data, so that it would be downloaded together with the update file, but when redirecting the custom data to the xml information, it did not detect it and in SOTI The field does not appear, the name of the custom data does appear but without information. Has something similar happened to someone else? What update systems do you have implemented for android terminals? Do you have any ideas or suggestions about how I could solve the custom data problem, or any improvement for the update system? My SOTI version is: 14.1.5.1284 and the terminals are mostly TC52 and WT6000. Thank you very much to all.
Hello, We are currently testing some Firmware update OTA. The FOTA is working fine on one of our devices. Now, we would like to target all the ~2000 devices that are currently enrolled on our server. --------------- MC version : 14.3.3.1111 Device Manufacturer : Coppernic Device Model : COne2 Management Type : Work Managed Device AE Agent Version : 14.4.1.1064 --------------- I tested the following script : writeprivateprofstring SystemUpdatePolicy 1apply SystemUpdatePolicy You can find the documentation here No error message in the device logs but the script does not work. Does the script look OK to you? Is there any need for additional elevation like WRITE_SECURE_SETTINGS for writesecuresetting? Is there maybe any other way to process? Many thanks for your help and advice !
Hi, Since https://developer.zebra.com/community/home/blog/2017/11/06/access-zebra-lifeguard-patch-version-in-soti-mobicontrol does not show the screenshots anymore because they are not available anymore, I am looking for someone who could show me how to set up the custom data rule to extract the PATCH_VERSION out of the patchver.ini file created by GetPatchVer.apk
Hi, I have some Samsung Tab Active 2 devices currently on Android 8.1 which will start to receive updates for Android 9. I don't want them to do this as our app (loaded via package & profile) has not been tested on this version. The question of how to block an OS update has been asked before via this link and an example was given for set_system_update_policy , which I have applied. My question is: didn't there not used to be an option within Feature Control to stop all firmware updates? And if anyone has any other tips to stop the updates through MobiControl I'm all ears. Eddie
Hello Is it possible via MobiControl create a Schedule Task which start the distribution of the IOS update to the IOS devices Powershell ? Script ? Task ?
What is your preferred MobiControl driven OS / Firmware update method for Zebra Android devices, and why? I am trying to validate the best deployment strategy given the regular release of Lifeguard updates, sometimes in the 30-50MB range, and the occasional release of full size updates in the 200-300MB range. I am considering multiple aspects including, but not limited to, minimizing impact to the network and minimizing impact to the end users. Do you have users self-serve the update? Do you schedule them to all occur at the same time? Do you preload the update files and then execute the installation separately? Delivery Mechanism Options - File Sync Rule - Package - MX Profile that points to an FTP server or other download location. - Other? Application Mechanism Options - install_system_update as a post install script in the package - install_system_update as a standalone script applied on demand - install_system_update in a script in a package that is applied via a Self-Serve package - MX profile for applying the OS update applied as a package - Zebra custom app for applying OS Updates. - Other?
I'm just wondering if this is possible through SOTI Mobicontrol.
In some cases I need to push out 300mb+ files to Android devices to perform firmware updates. Is there any way to get visibility into the percentage downloaded from the the SOTI server? I often don't know how much of an update has been downloaded until it actually starts executing.
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
