What are the brand/models of the devices?  

What about the firmware version and active MDM API's?

And the version and build numbers of the MobiControl server and device agent(s)?

Do the end-users absolutely need to run apps on the device in their workflow? Or is there a possibility that they intentionally have the devices powered off and cellular connection off to avoid any possible monitoring/data-collection from other colleagues?

Hi Vincent 

Thanks for your query. 

I agree with Raymond you need to check if the devices are intentionally powered off or the cellular connection is off.

On a test device, check if the device is connected to the network that is it has either cellular or the wifi connectivity

You can send the script connect-f to the device to force the device to connect to the deployment server.

Please find the usage as : 

connect -f 

Help-Link for script

Or you can set the out of contact policy for the devices which are not online. 

Please note that to make these commands work when the device has connectivity.

Regards

Hi Vincent,

If you have no idea if device user intentionally have their devices powered off and cellular connection off to avoid any possible monitoring/data-collection from other colleagues,  I suggest you consider deploying the following policies to find out:

1.  Data Collection Rule with battery, SSID, cellular carrier and RSSI data collected every 5 minutes.  Battery level data is especially important to know when the device is off.  Make sure you set sufficiently big buffer size to store required data.

2.  Device-side Out-Of-Contact policy in Android profile with script commands to force cellular and/or Wifi on if the device has been out-of-contact after 1 or 2 or 5 minutes.  The following can be used:

   setmobiledata   1

   setradioenable  phone 1

   setradioenable  wifi 1

3. Test the device to make sure that doze mode or other low-power mode that may potentially make the device agent sleep is not enabled/allowed.