Network clients time not updating
Note In Windows Server 2003 and Microsoft Windows 2000 Server, the directory service is named Active Directory directory service.In Windows Server 2008 and later versions, the directory service is named Active Directory Domain Services (AD DS).The following factors often affect the accuracy of synchronization in AD DS: Important Prior to Windows Server 2016, the W32Time service was not designed to meet time-sensitive application needs.However, updates to Windows Server 2016 now allow you to implement a solution for 1ms accuracy in your domain.However, the Windows Time Service can be configured to request time from a designated reference time source, and can also provide time to clients.The degree to which a computer's time is accurate is called a stratum.The Windows Time service synchronizes time between computers within the hierarchy, with the most accurate reference clocks at the top.If more than one time source is configured on a computer, Windows Time uses NTP algorithms to select the best time source from the configured sources based on the computer's ability to synchronize with that time source.
If the time difference between the local clock and the selected accurate time sample (also called the time skew) is too large to correct by adjusting the local clock rate, the time service sets the local clock to the correct time.
A time protocol is responsible for determining the best available time information and converging the clocks to ensure that a consistent time is maintained on separate systems.
The Windows Time service uses the Network Time Protocol (NTP) to help synchronize time across a network.
Therefore, it is impossible to guarantee time accuracy on computers that have intermittent or no network connections.
An AD DS forest has a predetermined time synchronization hierarchy.