Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update configuring-systems-for-high-accuracy.md #7738

Merged
merged 1 commit into from
Feb 20, 2024
Merged

Update configuring-systems-for-high-accuracy.md #7738

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions ...erDocs/networking/windows-time-service/configuring-systems-for-high-accuracy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,11 +41,6 @@ For this reason, we have documented the [Support boundary to configure the Windo

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.

> [!WARNING]
> It is highly recommended to disable the Secure Time Seeding (STS) feature for the Windows Time service on devices that already sync with a reliable time source such as an NTP server. This includes both Active Directory domain controllers as well as member servers. This is because STS was designed specifically to correct only gross clock inaccuracies on portable devices such as tablets and laptops whose batteries might die or whose hardware clocks might not be as reliable. Furthermore, it is possible for STS to incorrectly set the system clock if enough SSL-based handshakes containing random data are received.
>
> For more information, see [Time accuracy improvements for Windows Server 2016](/windows-server/networking/windows-time-service/windows-server-2016-improvements).

In the illustration shown below, 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.

![A diagram that shows three virtual machines connected to a Windows Server 2016 Hyper-V host utilizing the Windows Time service.](../media/Windows-Time-Service/Configuring-Systems-for-High-Accuracy/topology-2016.png)
Expand Down