Hello Paul

Greetings

Thanks for requesting an answer from SOTI!!

Kindly let us know if this issue is still happening on your end and if it's not resolved then kindly let us know following

1. Can you test by removing all  profile configuration(mainly feature control and app run control)  and try to reboot again.

2. Kindly confirm Mobicontrol version and Mobicontrol agent version.

3. In last , if you can confirm , this issue is happening to only on OS 10 devices and reproduceable on Multiple OS 10 devices too.

4. Can you try to test without any screenlock and see if agent connect automatically after reboot.

Regards

If a device has "secure startup" configured either manually or automatically (i.e. mandatory), it of course cannot be controlled by MobiControl until the correct unlock password is input and Android system restrated.  The only solution is to check if the device Settings supports disabling such "secure startup" feature.

Thank you for the reply I will post the answers to your questions as soon as I can

@Raymond Chan

Thank you for your reply but The devices are not configured for Secure Startup

When you said in your post that ' ... even though the device has powered back up, it is not until someone unlocks it that one get the message "Android is Starting" ... ' , your device is actually in "secure startup" or "strong-protection" mode. 

I don't know whether you found no such options on your device Settings or you find some "smart startup/stong-protection" Settings tab and confirmed that they are not turned on.  If it is the latter case, then please show scereenshot of corresponding Settings tab on your device.

Actually, all Android 10+ devices should have File-Based Encryption enabled, and only "Direct-Boot" capable app can have some functionalities run before the  encryption password is correctly input.  However, I don't think Soti MobiControl agent, nor most of the apps on your device, supports Direct-Boot. So, the end result is the same as what you will get for device using Full-Disk-Encryption (i.e. those with "Secure Startup/Strong-Protection" enabled).

Thanks for the reply Raymond, From your first post I thought you meant Secure Startup when you need to enter your password top power the device up, Which I know is not configured.

However I will search the device for the setting you mentioned and see if it indeed configured

Thank you

1. Can you test by removing all profile configuration(mainly feature control and app run control) and try to reboot again.
- This made no difference

2. Kindly confirm Mobicontrol version and Mobicontrol agent version.
Server - 15.3.0.6713
Agent - 14.5.3.1017

3. In last , if you can confirm , this issue is happening to only on OS 10 devices and reproduceable on Multiple OS 10 devices too.
All V10 Devices

4. Can you try to test without any screenlock and see if agent connect automatically after reboot.
- Without the screen lock MobiControl agent connected to the server

It would appear that the Screen Lock is connected to issue, but I cannot see anything within the settings where I may change that
I would expect MobiControl Agent to start as soon as the device is powered up

@Raymond
I have searched all the settings, I cannot find anything about Secure Start Up, or Strong protection within the devices settings.

We have the same problem with our tablets (Samsung Galaxy Active Pro) and Android version 10. After a soft reset, the tablets are offline until a user enters the pin code. This is a very undesirable situation for us where we can no longer provide sufficient remote support. Has a solution been found for this yet?

Is yours the pin code to allow the tablet to restart or the pin code to unlock the screen once it has rebooted?
If it is to restart, this can be switched off. 

If it is once the tablet has started then this is the issue I have

Thanks mate, that was the trick