This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Time synchronization in Windows 10 and Windows Server 2016 is enhanced. Under optimal conditions, these systems can be configured to achieve and maintain an accuracy of 1 millisecond (ms) or better with respect to UTC.
Warning
Windows Server 2012 R2 and previous releases doesn't meet the same high accuracy objectives. These operating systems aren't supported for high accuracy. In these versions, the Windows Time service satisfied the following requirements:
Greater tolerances on 2012 R2 and previous releases are outside the design specification of the Windows Time service.
While we support accuracy up to 1 ms on Windows 10 or Windows Server 2016, most customers don't require highly accurate time.
As such, the default configuration is intended to satisfy the same requirements as prior operating systems that:
Time accuracy entails the end-to-end distribution of accurate time from the authoritative time source to the end device. Anything that adds asymmetry in measurements along this path negatively influences the accuracy achievable on your devices.
For this reason, the Support boundary to configure the Windows Time service for high-accuracy environments is documented outlining the environmental requirements that must also be satisfied to reach high accuracy targets.
High accuracy configurations require Windows 10 or Windows Server 2016. All Windows devices in the time topology must meet this requirement including higher stratum Windows time servers, and in virtualized scenarios, the Hyper-V Hosts that run the time-sensitive virtual machines. All of these devices must be at least Windows 10 or Windows Server 2016.
In the following illustration, the virtual machines requiring high accuracy are running Windows 10 or Windows Server 2016. Likewise, the Hyper-V Host on which the virtual machines reside, and the upstream Windows time server must also run Windows Server 2016.
Tip
You can run the winver command in a command prompt or through PowerShell to view the OS version and build number:
Reaching high accuracy targets requires system configuration. There are various ways to perform this configuration, including directly in the registry or through group policy. More information for each of these settings can be found in the Windows Time Service Technical Reference: Windows Time Service Tools.
To ensure the Windows Time service (W32Time) runs continuously, set its startup type to Automatic.
Measurement uncertainty and "noise" increases network latency. As such, it's imperative that a network latency be within a reasonable boundary. The specific requirements are dependent on your target accuracy and are outlined in the Support boundary to configure the Windows Time service for high-accuracy environments article.
To calculate the cumulative one-way network latency, add the individual one-way delays between pairs of Network Time Protocol (NTP) client-server nodes in the time topology, starting with the target and ending at the high-accuracy stratum 1 time source.
For example: Consider a time sync hierarchy with a highly accurate source, two intermediary NTP servers A and B, and the target machine in that order. To obtain the cumulative network latency between the target and source, measure the average individual NTP roundtrip times (RTTs) between:
This measurement can be obtained using the inbox w32tm.exe tool by performing the following steps:
Perform the calculation from the target and time server B.
w32tm /stripchart /computer:TimeServerB /rdtsc /samples:450 > c:\temp\Target_TsB.csv
Perform the calculation from time server B against (pointed at) time server A.
w32tm /stripchart /computer:TimeServerA /rdtsc /samples:450 > c:\temp\Target_TsA.csv
Perform the calculation from time server A against the source.
Next, add the average RoundTripDelay measured in the previous step and divide by 2 to obtain the cumulative network delay between target and source.
Configures the smallest interval in log2 seconds allowed for system polling.
| Description | Value |
|---|---|
| Key location | HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config |
| Setting | 6 |
| Outcome | The minimum polling interval is now 64 seconds. |
The following command signals Windows Time to pick up the updated settings:
w32tm /config /update
Configures the largest interval in log2 seconds allowed for system polling.
| Description | Value |
|---|---|
| Key location | HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config |
| Setting | 6 |
| Outcome | The maximum polling interval is now 64 seconds. |
The following command signals Windows Time to pick up the updated settings:
w32tm /config /update
The number of clock ticks between phase correction adjustments.
| Description | Value |
|---|---|
| Key location | HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config |
| Setting | 100 |
| Outcome | The number of clock ticks between phase correction adjustments is now 100 ticks. |
The following command signals Windows Time to pick up the updated settings:
w32tm /config /update
Configures the poll interval in seconds when the SpecialInterval 0x1 flag is enabled.
| Description | Value |
|---|---|
| Key location | HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient |
| Setting | 64 |
| Outcome | The poll interval is now 64 seconds. |
The following command restarts Windows Time to pick up the updated settings:
net stop w32time && net start w32time
| Description | Value |
|---|---|
| Key location | HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config |
| Setting | 2 |
Note
To learn more about the W32Time registry settings, see Windows Time registry reference
Training
Module
Explore common configuration options - Training
This module discusses configuring and customizing some of the common default settings in Windows clients.
Certification
Microsoft Certified: Windows Server Hybrid Administrator Associate - Certifications
As a Windows Server hybrid administrator, you integrate Windows Server environments with Azure services and manage Windows Server in on-premises networks.