Article ID: 909614 - Last Review: November 1, 2006 - Revision: 1.4

How the Windows Time service treats a leap second

View products that this article applies to.

On This Page

Expand all | Collapse all

INTRODUCTION

This article describes how the Windows Time service treats a leap second.
Back to the top

MORE INFORMATION

When the Windows Time service is working as a Network Time Protocol (NTP) client

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 difference is resolved at the next time synchronization.
Back to the top

When the Windows Time service is working as an NTP server

No method exists to include a leap second for the Windows Time service.

How a leap second is included depends on NTP server settings.
Back to the top
APPLIES TO
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Server
  • Windows Server 2008 Standard
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Datacenter
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Web Server 2008
  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Enterprise
  • Windows Vista Business
  • Windows Vista Ultimate
  • Windows Vista Starter
Back to the top
Keywords: 
kbinfo KB909614
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations