SOTI Pulse Logo

Update Honeywell CT60(XP) to Android 11

Solved
M
MaikStrassmann
KWS SAAT SE

Hello dear Soti users,

we have received information from the IT management that we should please make sure that we are using the latest Android updates.

We are using different Honeywell CT60 and Honeywell CT60XP in one department.
Here the highest version available is Android 11.
We are using Android 9 and 10 devices set up as Work Managed Device.

In your opinion, what is the best and most stress-free (for the user) procedure to distribute the update without a large downtime (at best on the weekend)?

Can I go directly from Android 9 to 11? Do I need any middle steps?

In my last test I had the update file copied to
/sdcard/honeywell/autoinstall/filename.zip
and then rebooted.


This could be synchronized accordingly with a filesync or profile in advance and make a reboot on the weekend, for example, via a scheduled task.

I have so far only 2 devices manually changed, but one of the wifi settings were lost afterwards. That would of course be problematic.

Hope to hear your recommendation.

honeywell
2 years ago
SOTI MobiControl
ANSWERS
MD
Matt Dermody Diamond Contributor
2 years ago

You could start staging the OS update on the devices now via a File Sync Rule. I recommend File Sync rules for large file delivery like OS Update Zips over Packages as the File Sync stores the file in the server file system instead of in the MobiControl DB, which is limited in storage size. 

You could then schedule the update to happen via a one time Task Scheduler script designed to reboot the devices just as you have mentioned. If you don't want the devices accidentally upgrading in the meantime due to organic reboots that might be otherwise occuring then you could maybe even save the file with an alternate name like update.zip.temp and then use scripting to rename it right before the reboot is executed. Otherwise the random reboots that might be occurring in your inventory might lead to early upgrades. 

You also want to take extra care to ensure the applications you're running and configuration you're deploying are actually compatible with Android 11. Android 11 introduces restrictions on scoped storage access which prevents an EMM agent like SOTI from reading or writing from scoped storage directories. Apps currently using scoped storage for configuration or logging have to be rewritten to accommodate the changes in A11+. There can be a potential gotcha in upgrading from a lower Android version to Android 11 in that SOTI could have pushed a configuration file to a scoped storage directory for a particular app while the device was on A9 or A10, but then after the device is upgraded to A11 SOTI will be blocked from doing so. The file will still be there based on it being pushed while on an older version, so the business app may still be using it, but SOTI will be unable to access the directory to make updates to it.

Solution
M
MaikStrassmann
2 years ago

Hi Matt,
thank you very much for your reply.

That's good advice with the file sync rule and the limited file size. I currently don't have permissions on the server to store the files for file sync, but that can be fixed. 

I also like the idea with the temporary name, I hadn't thought about that.

In my testing so far, I've also noticed that our Company App loses the settings. That's a damn good hint for our developers.

Let's see how we approach this.

Maik

M
MNMOD@SOTI
2 years ago

Hi MaikStrassmann,

Thank you for posting on SOTI Pulse!

Did any of the above suggestions worked as a solution for you? If yes, can you please mark that post as solution which resolved the issue.

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net l Discussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter 

M
MNMOD@SOTI
2 years ago

Hi MaikStrassmann,

I have marked the relevant post as solution. If this post did not assist you in resolving the issue and you have additional questions, please do not hesitate to reach out.

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net l Discussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter 

Similar Discussions