Zabbix server time not in sync with Windows environment.

[TWSLB]

Our on-prem environment is largely Windows 2016 servers. All servers and endpoints get their system time from the DC which in turn uses the Windows Time service (W32Time).

The issue I have is that the Zabbix server will not sync to this time by default (obviously) so I keep getting "System time is out of sync (diff with Zabbix server > 60s)" on all the Windows servers I'm monitoring. Can I point the Zabbix server at the Windows Time service instead of NTP? I've looked at other forum posts but whilst they're in the ballpark of my issue they don't really address it entirely.

[Markku]

The simple reason for not finding the answer in Zabbix forums is that Zabbix doesn't do any time synchronization, it just uses the time the underlying platform provides.

What is your Zabbix server OS and version? You need to search the answer with those, and maybe someone can help you still here as well. And, AFAIK, Windows server still provides the time syncing with NTP.

For example, this is how I've used to reconfiguring systemd-timesyncd on Debian (I don't usually use ntpd or chrony):

sudo mkdir -p /etc/systemd/timesyncd.conf.d
echo -e "[Time]\nNTP=timeserver1.example.com timeserver2.example.com" | sudo tee /etc/systemd/timesyncd.conf.d/local.conf
sudo systemctl restart systemd-timesyncd.service

(Basically that additional file overrides the Debian-default configuration so future OS upgrades won't overwrite my custom config)

Markku