Have you checked whether your problematic devices have their "Time Synchronization" Advanced-Configuration poicy configured to synchronize time with a malfunctioning NTP/SNTP server (e.g. time of the server itself inaccurately set/frozen to this magic time "f 05:18AM 19/3/2020")?

Hi Raymond

The time sync policy is on the deployment server so unless this keeps on dropping out I still cant see why this is happening

Thanks

Ricky

In such case, you have to check

1. if the device time get regularly synchronized back with the DS time correctly according to the synchronization policy schedule (e.g. by first intentionally setting an incorrect device time manaully)

2. how the server system-time is set/synchronized in the MS Windows-Server hosting your MobiControl deployment server.

Hi Raymond

I have tested by going into admin mode changing the time and putting back and the time does correct itself. We use  s109409.mobicontrolcloud.com so do not have a deployment server

Thanks

We only see this happening if devices have been offline a long time, coming online and then their internal time is not correct (internal clock seem not so accurate). And just before they got the correct time from network, they are "logged in" to mobicontrol console and show this wrong time in the console. But here it's always a time in the future.

Hi

The device was off line for 2 hours, the time is pulled from the server and not the network

2 hours shouldn't be so bad even for the internal clock

Hi Ricky,

As you are using MobiControl cloud instance s109409, any tests/checks on the MS Windows server have to be done by Soti cloud support team.  I suggest you to email support@soti.net directly to open a support case and ask them to check sytem time configurations and MobiControl server log  files for suspicious entries related to your mentioned magic time of 05:18AM 19/3/2020.

Under normal circumstances, the drift of device real-time-clock time from DS/NTP/SNTP server time should be in order of seconds or minutes even if the devices have been offline for a few weeks, and the device time will definitely not be offset to a fixed erroneous time of "05:18AM 19/3/2020", which is more than a year drift from the current time.  So, you can ignore what Rafael said in his last two posts in this discussion thread.

You might also need to check the device's Settings to see if there is any improperly configured time-syncrhronization feature in the Honeywell device firmware enabled.

Hi Raymond

Thanks for the update ant I have raised with Soti Support