This article describes the support boundaries for the Windows Time service (W32Time) in environments that require highly accurate and stable system time.

Applies to:   Windows Server (All supported versions) including Azure Stack HCI, Windows client (All supported versions)

High accuracy support for Windows 8.1 and 2012 R2 (or prior)

Earlier versions of Windows (prior to Windows 10 1607 or Windows Server 2016 1607) can't guarantee highly accurate time. The Windows Time service on these systems:

• Provided the necessary time accuracy to satisfy Kerberos version 5 authentication requirements
• Provided loosely accurate time for Windows clients and servers joined to a common Active Directory forest

Tighter accuracy requirements were outside of the design specification of the Windows Time Service on these operating systems and weren't supported.

Windows 10 and Windows Server 2016

Time accuracy in Windows 10 and Windows Server 2016 has been substantially improved, while maintaining full backwards NTP compatibility with older Windows versions. Under the right operating conditions, systems running Windows 10, Windows Server 2016, and newer releases can deliver 1 second (s), 50 milliseconds (ms), or 1 ms accuracy.

High accuracy requirements

The rest of this document outlines the requirements that must be satisfied to support high accuracy targets.

Target accuracy: 1 second

To achieve 1 s accuracy for a specific target machine when compared to a highly accurate time source:

• The target system must run Windows 10, Windows Server 2016, or a newer version.
• The target system must synchronize time from an NTP hierarchy of time servers, culminating in a highly accurate, Windows compatible NTP time source.
• All Windows operating systems in the NTP hierarchy mentioned above must be configured as documented inConfiguring Systems for High Accuracy.
• The cumulative one-way network latency between the target and source must not exceed 100 ms. The cumulative network delay is measured by adding the individual one-way delays between pairs of NTP client-server nodes in the hierarchy starting with the target and ending at the source. For more information, review the high accuracy time sync document.

Target accuracy: 50 milliseconds

All requirements outlined in the sectionTarget accuracy: 1 second apply, except where stricter controls are outlined in this section.

The other requirements to achieve 50 ms accuracy for a specific target system are:

• The target computer must have better than 5 ms of network latency between its time source.

• The target system must be no further than stratum 5 from a highly accurate time source.

  Note

  Runw32tm /query /status from the command line to see the stratum.

• The target system must be within six or fewer network hops from the highly accurate time source.

• The one-day average CPU utilization on all stratums must not exceed 90%.

• For virtualized systems, the one-day average CPU utilization of the host must not exceed 90%.

Target accuracy: 1 millisecond

All requirements outlined in the sectionsTarget accuracy: 1 second andTarget accuracy: 50 milliseconds apply, except where stricter controls are outlined in this section.

The other requirements to achieve 1 ms accuracy for a specific target system are:

• The target computer must have better than 0.1 ms of network latency between its time source

• The target system must be no further than stratum 5 from a highly accurate time source

  Note

  Runw32tm /query /status from the command line to see the stratum.

• The target system must be within four or fewer network hops from the highly accurate time source.

• The one-day average CPU utilization across each stratum must not exceed 80%.

• For virtualized systems, the one-day average CPU utilization of the host must not exceed 80%.