| title | description | ms.date | manager | audience | ms.topic | localization_priority | ms.reviewer | ms.custom |
|---|---|---|---|---|---|---|---|---|
How Windows Time service treats leap second |
Describes how the Windows Time service does not include the value of the Leap Indicator when the service receives a packet that includes a leap second. |
12/26/2023 |
dcscontentpm |
itpro |
troubleshooting |
medium |
kaushika, RyukiY |
sap:Active Directory\Windows Time Service configuration, accuracy, and synchronization, csstroubleshoot |
This article describes how the Windows Time service treats a leap second.
Applies to: Windows 7 Service Pack 1, Windows Server 2012 R2
Original KB number: 909614
The Windows Time service does not indicate the value of the Leap Indicator when the Windows Time service receives a packet that includes a leap second. (The Leap Indicator indicates whether an impending leap second is to be inserted or deleted in the last minute of the current day.) Therefore, after the leap second occurs, the NTP client that is running Windows Time service is one second faster than the actual time. This time difference is resolved at the next time synchronization.
For more information about Windows time synchronization, see How the Windows Time Service Works.
No method exists to include a leap second explicitly for the Windows Time service when the service is working as an NTP server.
However, if an external NTP server sends a Leap Indicator that has a value of 01 to the Windows Time service NTP server, the Windows NTP server sends the same value to following NTP client.