MobiControl Upgrade to 15.0.2.1049

JH
Jonny Hill
Paragon Fleet Solutions Ltd

We have recently upgraded MobiControl from version 13.4 to 15.0.2.1049 as we are now procuring Android 10 devices and version 13 doesn't support SHA2 certificates for enrollment. Since the upgrade, we have come across a number of issues, one of which is mentioned below. We have a support case open with SOTI, but I thought I'd also reach out to the community to see if anyone else can help.

Yesterday, we attempted to assign an updated profile to an existing set of devices (around 150) and around 15 of them stayed in an “Installed Partially” state, with the remainder installing successfully. The devices are all Samsung, but different models on different OS versions. On the devices themselves, a message is displayed on a blank screen stating “unable to load application menu please contact your administrator”. We attempted to retry the profile installation, but this did not work.

We found that the only remedy for this was to uninstall the agent on the device, re-install it and then re-enrol. Once re-enrolled, the profiles installed correctly. These devices are remote all over the country and in their current state, we can’t remote control them, so are having to recall them back in to be able to re-enrol them.

Before we tried to assign an updated profile to them, everything looked fine from the console. The agent had upgraded correctly, the devices were showing online and checking in and all profiles that were installed before the upgrade were still showing as installed correctly. Only once we have tried to assign a new/updated profile to the devices has this issue become apparent. It looks as if the agent has corrupted somehow during the upgrade, but this wasn't visible to us until we tried to assign a new/updated profile.

I’m now fearful that we have a larger number of devices in this state within our estate, but we will not know until we try to assign a new/updated profile to them. At which point we’ll then need to manually re-enrol.

5 years ago
Android
ANSWERS
TG
Tashi Genden
5 years ago

Hi Jonny, 

This is concerning and sounds like we will run into a similar issue. We recently upgraded from v13.2 to v15.1.1 and have a major app update that will be pushed out within a month (using an existing Profile). 

Are you using Android Classic or Android Enterprise for the Samsungs?

JH
Jonny Hill
5 years ago

We are using Android Classic - Samsung ELM. Sounds like you may be in a similar situation to us. After upgrade, everything appears fine, the devices upgrade their agents ok, are showing online and checking in ok. Only once you assign either a new profile or an updated existing profile to it, do you find the issue.

We have a package profile which only applies packages to devices, then a separate device profile which has other configurations such as application run control, lockdown, feature control etc. It is this second profile which appears to be having the issue currently, not the package-only profile. Certain elements of the profile stay in an "Installed Partially" state and the device itself is locked into a blank screen stating "Unable to load application menu".

As mentioned, we have a support call open with SOTI which is under investigation. If we get a resolution, I will post it here.

MB
Marcus Breitenthaler
5 years ago (edited 5 years ago)

Hi 

can it happen that a Fix is Implemented in 15.1.2?

 

MCMR-22303 Fixed issue that limited the total enrollment of Android Enterprise Managed devices to 10
JH
Jonny Hill
5 years ago

Just an update on this. We still have a support call open with SOTI and investigations are ongoing. However, we did find that when we upgraded our instance to 15.0.2.1049, we had Samsung ELM Agent version 14.0.0.1579 added into our agent set (Global Settings>Manage Android Agents and Plugins). Therefore when we initiated an agent upgrade on all of our Samsung devices, they upgraded to 14.0.0.1579. This agent is outdated and was potentially the reason why we had an issue installing profiles correctly to devices.

We have since updated the Samsung ELM Agent in our instance to the latest version which is 14.3.1.1050 and subsequently upgraded all of our device agents to this version. I have yet to set up a non-production area though where I can assign profiles to some of these devices to see if this is actually the issue.