Hi Stephan,

Thank you for posting in SOTI Central.

I suggest you raise a Support Case via support.eu@soti.net, then a Technical Support Specialist can look at the issue with you efficiently and aim for prompt resolution.

In the meantime, you could try sending this to an affected device:

elm_awaken 1

If no changes observed then:

writeprivateprofstring DeviceFeature DisableDozeMode 1
apply featurecontrol

Then again if no changes observed:

foregroundmode enable

If the issue gets resolved, look into Disabling Doze Mode via a Feature Control and then observe the new behavior.

Regards,

Hi Stephan,

All the Android script commands mentioned are related to sleep/doze mode of a device.  However, as it's mentioned that the connection of all your devices seem to be flipping every 10 second or so, I doubt the appropriateness of trying out those script as I don't think any Android device firmware will be so aggressive to force the device to sleep/doze after 10's of low/no activity.   I believe you are likely to be wasting your time trying those script out.

Instead, I believe it will be more fruitable to open an official support case with Soti support team, then change your DS/DSE/MS log level to information or verbose, and capture the corresponding log files for Soti support team to look into.

Update:

As suggested I have opened a support ticket. Without any research the support advised me to do a rollback to a snapshot, as the problem was caused by windows updates.

Anyways, after a rollback our devices seem to connect properly and can keep the connection to our server. We also able to enroll our devices again.

Not sure what happens next time we do windows updates, but for now we will skip this version (KB5003646).

Did you upgrade your host operating system  from MS Server 2016 to MS Server 2019?   

I personally advise my own customers, especially those in whose devices are used in mission critical operations within their organization,  to stick to MS Server 2016 for some more time, as MobiControl's support for MS Server 2019 is still relatively recent.      

Our host system is running MS Server 2019 since day one (installation date November 2019). We install windows updates frequently, but this was the first time we had some problems.