I support scientific computing, so depending on the application I will replace w32time with ntpd, which offers better accuracy and built-in support for referenc

I support scientific computing, so depending on the application I will replace w32time with ntpd, which offers better accuracy and built-in support for reference clocks. That said, I didn't realize that the w32time service got a _lot_ better in Windows Server 2016: https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-ds/get-started/windows-time-service/windows-2016-accurate-time https://technet.microsoft.com/en-us/windows-server-docs/iden... It looks like Microsoft added support for NTPv4, and w32time now boasts 1-ms accuracy, which is at least a factor of 10 better than the previous Windows Server release.