Cut down on relying on network time servers for synchronization!
Cut down on relying on network time servers for synchronization!
Previously I thought it was just a difference between UTC and time zones or daylight saving adjustments, but I don’t often use Windows, so I rarely had to deal with it.
On internal networks I install an open source time server on my main Windows or domain controllers. This allows devices such as cameras or non-domain members to receive time updates independently of the internet. Only the master computer handles synchronization. I seldom encounter devices drifting more than a minute. For tighter sync beyond a minute, it’s not typically necessary.
We selected the available software. How often do you check upstream connections? What time should servers be set as the upstream source? The NTP pool group is strained and requires more nodes to meet rising demands. I’m aiming to start with a simple topic—time synchronization—and explore its impact on our usage. Should we aim for minute-level precision, or are monthly or even shift-based updates sufficient for DST versus standard transitions?