No Matches Found!
Try with a different search term
Hi everyone,
What is the best way in SOTI MobiControl to ensure Android Classic devices always have the correct date, time, and time zone?
Thanks!
How you mean and in which state?
And i don't see a dependency to the "classic" enrollment.
Hi Rafael,
We want to ensure that packages (deployed from the profile) are only installed between 23:00 and 23:59.
To achieve this, we've looked into the 'Custom Package Installation Schedule' option, but we see a few drawbacks:
If we use the UTC Time option: How can we guarantee that it will work on devices in Spain and Portugal, both in winter time and summer time?
As a summary of the impact:
In Spain (Mainland): 23:00 UTC would mean the installation runs at 01:00 local time in summer and 00:00 in winter.
In Portugal: 23:00 UTC would mean it runs at 00:00 local time in summer and 23:00 in winter.
If we use the Device Time option: How can we guarantee that the device always has the correct date, time, and time zone configured?"
Regards.
So, we speak about already enrolled devices ;)
So, you can define in Mobicontrol a general NTP:
A second option would be to provide NTP via OEM config app of the relevant manufacturers oem app, if available.
In addition check that your devices might have auto time synchronisation from network on in their date/time settings. If that's not the case, you need to investigate the manufacturers oem config app if you can set it there but by default this should be on.
But in general, at least from our side, the devices should do that by default if you don't block that from network side.
I understand what you mean, and we already have it configured according to the documentation you attached. However, I understand that this does not guarantee in 100% of cases that a device will always have the time correctly configured, correct?
On the other hand, I'm not sure if you've had a chance to look into what I mentioned regarding the "UTC Time" option, but we would appreciate it if you could give us a hand with that configuration. We believe this option would guarantee in 100% of cases that nothing is executed outside the scheduled time.
Sorry, i may miss your problem here.
If devices are always having a data connection (no matter if Wifi or mobile data) they should sync with an NTP server (if not turned off in settings).
This means, as long devices are on and online, they will sync and should have their correct local time.
With the settings i mentioned above (see 5. and oem config app) you could also force devices to a timezone you prefer.
For me, i would keep the default NTP, which never caused timing issues from my end.
We provide devices with execution on local device time, trusting that NTP works fine as you want to execute tasks outside working hours which makes local device time the one to rely on best.
If NTP wouldn't work, most likely devices have issues connecting to internet via Wifi (we see this for long offline devices without SIM sometimes which then needed to be touched manually but this is a different story).
Ofc you need to test your setting before you put in production.
Hi @Rafael Schäfer,
Yes, what we need is to guarantee that installations are only performed outside of working hours. We are concerned about using the Device Time option in scenarios where the device loses its time configuration, which is why we want to check if UTC Time can cover our use case.
Are there other clients using the UTC Time option? How do they manage to cover both winter and summer time changes (Daylight Saving Time)?
Hello Enric,
Thank you for posting on SOTI Pulse, and a big thanks to Rafael for their valuable input. Your expertise and willingness to help are greatly appreciated!
From the MobiControl console, the scheduling options use UTC time and Device time.
Since UTC is not affected by Daylight Saving Time (DST), the local execution time of the scheduled task may shift when DST begins or ends. If you are using UTC scheduling and want the task to continue running at the same local time after a DST transition, you will need to adjust the schedule accordingly.
Alternatively, you can configure the schedule using Device Time. This uses the device's local time and allows the task to continue running at the configured local time, even when DST changes occur.
If you have any further questions or concerns, please don’t hesitate to reach out. We're here to support you every step of the way.
To register a case, you can use the following link: Log a Case Webform.
Regards,