Mobicontrol upgrading from 13.3.0.3454 to 14.1116

Solved
JN
Jeffrey Nemusombori
South African Container Depot

Good day,

I have been tasked with upgrading our MobiControl(hosted locally) from V13.3 which is hosted in windows server 2008 R2 to the latest (being V14.something) which i will have to upgrade windows as well to 2016.i am very nervous not knowing what is on the otherside.

When reading on some soti documents they advise that you first upgrade from v13.3 to v13.4 then finally to v14,has anyone ever just upgraded from v13.3 to v14 secondly has anyone migrated Mobicontrol soti from windows server 2008 r2 to windows server 2016.

7 years ago
SOTI MobiControl
ANSWERS
J
JMOD@SOTI
7 years ago

Hi Jeffery,

Thank you for your question.

When upgrading MobiControl, it is always recommended to follow the upgrade path to insure that the upgrade can be completed without any issues.  Please see upgrade path below.

v 13.0.0 (GA or MR), v13.1.0 (GA or MR), v13.2.0 (GA or MR), v13.3.0 (GA or MR) or v13.4.0 (GA or MR)

|

v 13.4.0.(latest MR)

|

v 14.1.6 B1113

When upgrading MobiControl, we recommend our clients to create a backup image of your server, and also create a backup of your database. This is so that in case there are any issues with the upgrade, you would still have the option to revert your server to a working state.


After each upgrade of MobiControl, it is best practice to upgrade device agents as well. When upgrading device agents, please apply upgrade to 1 or 2 devices first to see if it is successful before applying the upgrade to a group of devices.


In your scenario, it is best practice to perform the agent upgrade process twice. One for 13.4 and another for 14.1.6.


Hopefully this is helpful,

Solution
MR
Matt Rogers
7 years ago

We just had our Cloud test instance upgraded and the SOTI techs performed it in just the way you described-- they upgraded to the intermediate version (13.4) before proceeding to 14.1 (I logged in during the process and found myself in the "old" console and checked the version).

It seems that they follow their own recommendation, so there must be a good reason for it. My guess is that there is a database upgrade between 13.x and 14.x, hence the two-step process. 

Or maybe it is due to the deprecation of Webroot, I read in the release notes for 14.1.6 Build 1113 under "Upgrade Observations":

  • The MobiControl installer will warn on upgrade if it detects Profiles with the Webroot powered "Web Filter" and/or "Antivirus" device configurations. Future upgrades will not be allowed unless all "Web Filter" configurations are transitioned to "SOTI Surf", and all Android device agents are upgraded to v13.5 or higher to continue support for Antivirus.

So possibly the added step is to move from Webroot to BitDefender?

A
AJMOD@SOTI
7 years ago

To provide clarification to JMODs post, the agents only need to be updated mid-upgrade if the customer is upgrading from a version prior to 11.03 to anything above it.

The reason for this is because prior to version 11.03 our device agents did not use SSL certificates and after it was added it became necessary for our devices to connect to the MobiControl.