If you are just talking about upgrade path, then you are right that you miss something.  You should have upgraded to latest v13.4.0 first, before going to v14.2.

Of course, I can't rule out that are many other things you need to consider and prepare beforehand to avoid other upgrade problems even if you follow the above upgrade path.

We did follow the upgrade path from v14.0 > v14.2 for SOTI MobiControl.

Is there a seperate upgrade-path for the 13.3.3-Agent for Samsung devices?

Oops!  Sorry.  I misread what you had written and thought that your server got upgraded from v13.3.3 to v14.2.

Well. If your device running v13.3.3.1034 agent worked fine with v14.0 server, I think your device icon should still showed a small triangular yellow mark, indicating that you should upgrade the device agent.  If so, you should have upgraded the device agent first (possibly to some build of v13.5.0 or v13.5.1 at least).   Confirm that the device and all policies work fine with the new device agent.    If you have other device brand/model in other platform(s), you might need to carry out similar procedure. 

Then you can perform your server upgrade to v14.2.  You might need to upgrade device agent to say v13.6.0.x  after that.

As I am not from Soti and know very little about your particular implementation, the above is just the general logic or path, and may not be totally applicable to your case.  There might be many other factors (technical and non-technical) that need to be considered and tested before you upgrade.  Create back-up and prepare to fall back.  Be warned that if something serious go wrong and your deployed devices become out of control, falling back the server might not get your devices back in control.  In that case, you need device recalls and much extra work.  That is why a separate UAT platform may sometimes be needed to verify the upgrade steps and feasibility for some complicated/risky scenario.   Consult Soti support or professional service team directly beforehand if you have doubt.

Hello Elling, 

Can you try another more up to date agent on one of your devices?  You can accomplish this by accessing the full list of agents on our site Soti.net/oem and installing the most applicable agent for your device and trying to re-enroll the device into your MobiControl environment, to see if the agent is compatible. 

Also please note the MobiControl installer comes with the most recent agent at the time the build was created and may not contain any updated agents with fixes that you may injected into your DB.

Assuming the agent from the OEM site works well we can assist you to get that agent into the DB as we have now verified that that agent is compatible.

I would have to do some more research and testing to see why your MC installation, device, OS version, and agent combination are giving you an incompatible error message but this should help get you back on track.

Cheers