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.
We're currently using MobiControl v15.4.1. Devices are AE enrolled. We have a couple TC57's that are on Android v11 that we'd like to bring back down to v8.1. In the past, we've been able to use the "install_system_update" to push OSUpdates to devices (worked with downgrades as well), but now we receive a "failed to install" error on the device: and the RX logs show this error: OSUService: Can't perform update package: This API has been deprecated for OS downgrade. Kindly use new API (DOWNGRADE_PACKAGE) to enable downgrade (CODE:1103) Is there a way to call the "downgrade_package" via Mobi (com.symbol.intent.action.DOWNGRADE_PACKAGE)? Thanks! -Aaron
Hi, I would like to know more about using SOTI to deploy mass iPadOS... The iPadOS size is around 5.5GB, it brings concern as we have to update 90 units of iPad in one go... If we are to issue "Update OS" command via SOTI, the following questions come to mind (sorry I cannot test now as I cannot afford to update any of my iPad's OS now): 1) Will SOTI spread the update across a specific time frame to avoid congesting the whole bandwidth? 2) When issuing the command, will it force the iPad to update? Or will it prompt a box and ask for user's consent first? 3) We have set to defer OS update for 90 days, after that period, will iPad be forced to update regardless of its current status? 4) Is there a difference between "scan for OS update" and "update OS"? Thank you for your time.
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, 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
I would like to Upgrade my enrolled devices with SOTI from Android 7.1.2 to Android 8.1.0 I downloaded the follow files. Full image version: 02-32-04.00 LifeGuard update14 version: ATLAS_DELTA_UPDATE_02-32-04.00-OG-U14-STD How can I manage a zero touch OS update? I need a Work Managed Device with Device Owner enrollment type, because the Remote Control and the default apps are necessary. I think with Android 8 I have to use Enterprise Agent, so if the upgrade done I don't know what gonna be hapen with original Android Classic OEM agent. I'm afraid the device will no longer be available via SOTI. My enrolled device, environment parameters: Zebra MC3300 Android 7.1.2 - FPU_ATLAS_02-07-08.00-NG-U00-STD Enrollment type: Android + MC Web Console version: 15.2.4 MC agent version: GoogleMobicontrol1441_1064 Thanks in advance.
Im trying to force my Android devices to auto update using the following script set with a scheduled task In the log I get the error Custom log (missing ; before statement (Auto Update OS.js#1)) My Auto Update OS.js is just writeprivateprofstring SystemUpdatePolicy SystemUpdatePolicy 1apply SystemUpdatePolicy If I open send script on a device,select JavaScript and send the same script above I get the same error. If I select legacy I get the notifications. Script was sent to device (writeprivateprofstring SystemUpdatePolicy SystemUpdatePolicy 1 apply SystemUpdatePolicy Feature is not supported (SystemUpdatePolicy) So my question is do I have to set the script to legacy somehow to make it work on a scheduled task? And is it actually supported? I have tried on Android device versions 7 and 8.1 running SOTI agent 14.4.1
I am currently in the process of updating the OS on 100 radios. For the most part is has been pretty smooth. I created a package that includes the HE Full update, as well as the incremental update. I have a script included in the package to install the HE Full update, since that needs to be installed first. Then I have a task scheduler profile set up with the script to install the incremental update the next day. The HE Full update installed successfully on each device. The incremental update successfully installed on almost all of the devices but a few (I think they were disconnected from the WIFI). So I sent a script manually to install the incremental update on those few devices. I had no issues with the installation on those few, except for 1 of the devices. For the 1 device that is having issues, I keep receiving an error message stating "OS Update has failed to install. Please assure you have the correct package". I am positive I have the correct package, and it says the profile and package are installed on the device. All 100 devices are the same model, Zebra TC8300. Any suggestions would be greatly appreciated!
Hi, we have some Samsung Galaxy A40, which must be run on Android 9 for a while. With which script can i dissable the automatic download from new updates? Thanks!
I read a couple of post on SOTI discussion takling about OS Manager. Is it a SOTI application? How can I get this application? Thks JJC
Hi everyone, We recently deployed 30 Android devices. They have been enrolled while being on Android OS 9. Some end-users updated their devices and now Mobi app doesn't connect anymore to our DS. The reason is that our mobicontrol server have a self-sign certificate with SHA1 and Android 10 doesn't support it. We have an inventory of Windows Mobile CE 6.5 (which don't support TLS 1.2) and we don't wanna update this certificate yet because it would disconnect all those PC pockets. I've pushed a script to disable the system OS update but I believe this script only last 30 days on Android Enterprise devices. Is pushing the script again after 30 days will extend the policy ? Thanks for your help,
I am trying to update our TC70x devices to the latest Oreo LG patch. I used file sync to get the ZIP on all the devices and then scheduled the script (install_system_update %sdcard%/mdm/CFE_ATLAS_02-13-15.00-OG-U20-STD.zip) to install outside of production hours. When I woke up I saw that this failed. I went to one of the devices and just sent the script through the script button on SOTI and the device updated fine. So I am not sure what I am doing wrong here.
Is there a way to update the OS on a device? I have pushed the OS over in a .zip file but I can't find a way to initiate the installation of the new OS. This device is in Android Enterprise mode and isn't a Zebra device.
Is there a macro that would report back the current Android OS Version (8.1.0) for use in a script file? Specifically looking to create an IF statement that calls the current OS Version and then calls a specific MX XML file depending on if an upgrade or downgrade needs to be performed to get the device on a specific BSP. For example: IF %OSVersion%==8.1.2 mxconfig /sdcard/OSUpdate.xml IF %OSVersion%>=9 mxconfig sdcard/OSDowngrade.xml
Hello all, it's always me :) I hope you're well. We work with zebra tc75x under android 6 The server is on version v 13.3.0.3454 Actually, i'm testing and writing a procedure for to upgrade our parc of device to android 7. the step is -> place zip file and send a mxconfig script (stagenow) If I start an upgrade to android 7 has no production profile all is ok (hour / date / language / enroll MDM / APN / Wifi / ….) Now, I have installed on a device under android 6 all our production profile and also the zebra keyboard. I start the upgrade but after reboot I have two problems and I'm still block .. a) after upgrade, the hour it's not correct -> there is 20 minutes left ! Why and How i can make hours correct ? I've try sync file / disconnect ,connect again client / reboot device .. but nothing work we don't have a server time; the time is managed by soti when I enrolled a new device a see in the log -> time sync configured b) after upgrade, the zebra keyboard disapears ! I can't understand because our program is still there (apk) / lock down / soti surf and a lots of thing.. Ok i can install again zebra keyboard but I would like perhpas to find a better solution. Someone has perhpas an idea. thanks for all
What is the easiest way to push a Android OS update to a device over the air? Script? please let me know what everyone has used.
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
