What was the version and build numbers of the device agent that had no problem?   If no policy or server change has been made and you can confirm that switching to use the new device agent is the root cause of the problem, open an official support ticket with Soti support team and wait for release of a new device agent that fix the problem. 

Thank you Raymond for your answer.

To be honest, I think that we made the mistake to upgrade everything at once: server, agent and that on all our TC51...

So it will be difficult to confirm that the new device agent is the root cause of the problem... for the moment it's just a guess.

Before this big upgrade, we were using - without problem -  Server MobiControl 14.1 and  Agent MobiControl 13.5.0.1088 (the TC51 were already with Android 6.0.1).

Let's assume the problem comes from the new device agent.  Can you get hold of one device in your hand and reinstall (may need factory reset if  Android Enterprise Device-Owner mode is used) a device agent of version different from v13.9.0.1046 ?

Also, if you use "launch://"  for the web-app  in your lockdown menu, you might try to replace it with launchalways:// to see if there is any difference.

It seems to be quite impossible for us to test a device with an old version of the agent. Despite that, I opened a support ticket with Soti and I'm waiting for their response.

About the configuration of our Lockdown menu, your idea is interesting. We are using "http://" (so we can't replace it with "launchalways://") and I found that "browser://" resolves our issue ! But as we need a kind of "kiosk mode" this simple solution is not acceptable. We keep in mind this option (maybe using Soti Surf) in case we don't find any other.

Thank you very much Raymond for your advice.

If you are using Android Enterprise and need to use an earlier device agent,   you can technically do so with QR code or NFC using special configurations with Mobicontrol  Stage app running on a provisioning Android device.   I believe Soti support team will give you the details  in their reply.   If your company policies or the  device location/logistics make it impossible to downgrade agent, that's another story.

I'm actually surprised that you are using http:// kiosk item,  as I can't think of any special case that make this type of item useful and necessary.   If the primary target is to browse an URL (or run a web app) without exposing any URL address bar of the web browser,  then Soti Surf can achieve that effect and have many extra security options.

Just to keep you informed.

With the help of a SOTI technician we discovered that the problem comes from our side (bad network or server configuration).

would you mind sharing what exactly was the issue in your case?

i faced 1 issue today where this was happening just to 1 device, but i maybe want to be proactive and solve this issue if its getting out of hand in the near future.

thanks

Hello John Doe,

Unfortunately we stopped the investigation because at some point I needed a resource that was unavailable and we plan to migrate in a near future to MobiControl Cloud (which hopefully will resolve our server misconfiguration if any).

To help you, I just can say that we found a workaround (that's also why we stopped the investigation): We keep the WIFI active even when the devices enters sleep mode (this is an Android parameter). Hence, there's no network reconnection -> no check-in -> no return to the home page of the lockdown.

Best regards. 

Frederic