Domain Hierarchy Time Source Acquisition
Applies To: Windows Server 2008 R2
An Active Directory forest has a predetermined time synchronization hierarchy. The Windows Time service (W32time) 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, the Windows Time service uses Network Time Protocol (NTP) algorithms to select the best time source from the configured sources, based on the computer’s ability to synchronize with that time source. Currently, the Windows Time service is synchronizing time with a time source peer from the domain heirarchy.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-Time-Service |
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is not a member of a domain. NtpClient will attempt to use an alternate configured external time source if available. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient. | |
Microsoft-Windows-Time-Service |
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator for the domain at the root of the forest. There is no machine above this machine in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure this PDC emulator in the root domain to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient. | |
Microsoft-Windows-Time-Service |
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but the computer is joined to a Windows NT 4.0 domain. Windows NT 4.0 domain controllers do not have a time service and do not support domain hierarchy as a time source. NtpClient will attempt to use an alternate configured external time source if available. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient. | |
Microsoft-Windows-Time-Service |
The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in %1 minutes. | |
Microsoft-Windows-Time-Service |
The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will fall back to the remaining configured time sources, if any are available. The error was: %1 | |
Microsoft-Windows-Time-Service |
Time Provider NtpClient: No valid response has been received from domain controller %1 after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: %2 | |
Microsoft-Windows-Time-Service |
The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will continue trying to locate a domain controller every %1 minutes. This message will not be logged again until after a domain controller is found. | |
Microsoft-Windows-Time-Service |
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 | |
Microsoft-Windows-Time-Service |
NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error on '%3'. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1. | |
Microsoft-Windows-Time-Service |
NtpClient was unable to set a domain peer to use as a time source because of duplicate error on '%3'. The same time source '%4' has been specified as manual peer in NtpServer. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 | |
Microsoft-Windows-Time-Service |
NtpClient was unable to set a domain peer to use a time source because of an unexpected error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 | |
Microsoft-Windows-Time-Service |
NtpClient succeeds in resolving domain peer %1 after a previous failure. |