v15 agent on v14.4

MC
Martin Cunningham
Advanced Manufacturing Control Systems Ltd

I have upgraded the agent on a test device to v15.0.1.1051 (Samsung ELM). I have a lockdown on it that was working fine before the upgrade. By working fine I mean it worked as expected, I can also press and hold on "back" and I would be prompted for a code and I could disable the lockdown.

Since upgrading to v15.0.1.1051 when I long press on back I get a pop-up "Actions" with "Administrator" and "Refresh". I would expect pressing "Administrator" would prompt for the passcode and would allow me admin access to the devic. However when I press "Administrator" I get a pop-up at the bottom with the heading "Complete action using" and in a white block below that it says "No apps can perform this action". I am then unable to disable the lockdown while on the device.

What is going on and how do I fix it. I'm guessing I need to assign an app that will work when I try to disable user mode but I can't see where or how to do it.

4 years ago
Android
ANSWERS
RC
Raymond Chan Diamond Contributor
4 years ago

It's good that you test such upgrade on a test device only, as this is one of  best practices to follow when upgrading anything.

If your MobiControl server was v14.4 and lockdown was working fine with the old agent, why did you upgrade the device agent to v15.0.1.1051?  Did you expect the new agent to fix your existing problem(s) or support some new feature(s)?

MC

For no reason other than a new version came out and I wanted to try it.

We will be upgrading the server to v15.x soon enough and it would be good to know about these issues before hand and how to deal with them.

RC
Raymond Chan Diamond Contributor
4 years ago (edited 4 years ago)

As you have a plan to upgrade your server to v15.x soon,  you need to test whehter your device running your exisitng v14.x device agent works fine on your targeted v15.x server.  If so, and you cannot find solution with v15.0.1.1051 or other v15.x device agent,  you have the choice to still upgrade your server without upgrading device agent of the enrolled devices.   The above test flow is also true for EACH device brand/model of specific firmware/agent version already enrolled onto your current v14.4.x server.

To find any possible solution for device agent v15.0.1.1051,  you'd better open an official support case at support@soti.net and provide them with more detailed information, so that they can follow up whether the problem is related to the device agent or device firmware, or even do some tests using your server.     Soti moderators on this forum are unlikely to do this for you, and you will be very lucky if you can hear any solution from other forum user who has the same problem on the same device model/firmware version as yours.