The following command signals Windows Time to pick up the updated settings: w32tm /config /update UpdateInterval The maximum polling interval is now 64 seconds. The following command signals Windows Time to pick up the updated settings: w32tm /config /update MaxPollIntervalĬonfigures the largest interval in log2 seconds allowed for system polling. The minimum polling interval is now 64 seconds. HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\Config Next, add the average RoundTripDelay measured in the previous step and divide by 2 to obtain the cumulative network delay between target and source.Ĭonfigures the smallest interval in log2 seconds allowed for system polling. Perform the calculation from time server a against the source. W32tm /stripchart /computer:TimeServerA /rdtsc /samples:450 > c:\temp\Target_TsA.csv Perform the calculation from time server b against (pointed at) time server a. W32tm /stripchart /computer:TimeServerB /rdtsc /samples:450 > c:\temp\Target_TsB.csv Perform the calculation from the target and time server B. This measurement can be obtained using the inbox w32tm.exe tool. To obtain the cumulative network latency between the target and source, measure the average individual NTP roundtrip times (RTTs) between: To calculate the cumulative one-way network latency, add the individual one-way delays between pairs of NTP client-server nodes in the time topology, starting with the target and ending at the high-accuracy stratum 1 time source.įor 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. 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. As such, it is imperative that a network latency be within a reasonable boundary. Measurement uncertainty and "noise" creeps in as network latency increases. To do this, configure the Windows Time service's startup type to 'Automatic' start. The Windows Time service (W32Time) must run continuously. More information for each of these settings can be found in the Windows Time Service Technical Reference: Windows Time Service Tools. There are a variety of ways to perform this configuration, including directly in the registry or through group policy. Reaching high accuracy targets requires system configuration. You can run the command winver at a command prompt to verify the OS version is 1607 (or higher) and OS Build is 14393 (or higher) as shown below: Likewise, the Hyper-V Host on which the virtual machines reside, and the upstream Windows time server must also run Windows Server 2016. In the illustration shown below, the virtual machines requiring high accuracy are running Windows 10 or Windows Server 2016. All of these devices must be at least 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. High accuracy configurations require Windows 10 or Windows Server 2016. Anything that adds assymetry in measurements along this path will negatively influence accuracy will affect the accuracy achievable on your devices.įor this reason, we have documented the Support boundary to configure the Windows Time service for high-accuracy environments outlining the environmental requirements that must also be satisfied to reach high accuracy targets. Time accuracy entails the end-to-end distribution of accurate time from the authoritative time source to the end device. Note Regarding Supportability of Highly Accurate Systems How to Configure Systems for High Accuracy Provide loosely accurate time for Windows clients and servers joined to a common Active Directory forest.Provide the necessary time accuracy to satisfy Kerberos version 5 authentication requirements.While we support accuracy up to 1ms on Windows 10 or Windows Server 2016, the majority of customers do not require highly accurate time.Īs such, the default configuration is intended to satisfy the same requirements as prior operating systems which are to: Windows 10 and Windows Server 2016 Default Configuration Greater tolerances on 2012 R2 and below are outside the design specification of the Windows Time service. Provided loosely accurate time for Windows clients and servers joined to a common Active Directory forest.Provided the necessary time accuracy to satisfy Kerberos version 5 authentication requirements.In these versions, the Windows Time service satisfied the following requirements: These operating systems are not supported for high accuracy. Windows Server 2012 R2 and below can not meet the same high accuracy objectives.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |