Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. This article covers the different tools and settings used to manage the Windows Time service. By default, a computer that is joined to a domain synchronizes time through a domain hierarchy of time sources.
However, if a computer has been manually configured to synchronize from a specific time source, perhaps because it was formerly not joined to a domain, you can reconfigure the computer to begin automatically sourcing its time from the domain hierarchy. Most domain-joined computers have a time client type of NT5DS, which means that they synchronize time from the domain hierarchy. An exception to this is the domain controller, which functions as the primary domain controller PDC emulator operations master for the root forest domain.
The PDC emulator operations master in turn is usually configured to synchronize time with an external time source. You can achieve down to one-millisecond time accuracy in your domain. For more information, see Support boundary for high-accuracy time and see Accurate Time for Windows Server Don't use the Net time command to configure or set a computer's clock time when the Windows Time service is running.
This command has since been deprecated. Whenever the computer synchronizes its clock or provides time to another computer, it happens over UDP port This port is exclusively reserved by the Windows Time service. If you have a computer with multiple network adapters is multi-homed , you cannot enable the Windows Time service based on a network adapter.
You can use the command-line tool W32tm. Membership in the local Administrators group is required to run W32tm. This option might be used more than once. Computer names are separated by commas, with no spaces. The default value is 3. The allowed range is If not specified, the local computer will resynchronize. Otherwise, wait for resynchronization to complete before returning.
This is used for compatibility purposes. The default is 2 seconds. If not specified, the default is the local computer. When specifying multiple peers, this option must be enclosed in quotes. This setting is only meaningful on domain controllers. YES : This computer is a reliable time service. NO : This computer is not a reliable time service. If not specified, the default value is the local computer. In verbose mode, display the undefined or unused setting too.
Valid values are 0 to A range of numbers is valid, in addition to single numbers, such as ,, Value is for logging all information. Set client to use two time servers To set a client computer to point to two different time servers, one named ntpserver. To configure a client computer that is currently synchronizing time using a manually-specified computer to synchronize time automatically from the AD domain hierarchy, run the following following:.
To check a client configuration from a Windows-based client computer that has a host name of contosoW1 , run the following command:. The output of this command displays a list of W32time configuration parameters that are set for the client.
Windows Server has improved the time synchronization algorithms to align with RFC specifications. Therefore, if you want to set the local time client to point to multiple peers, we recommended that you prepare three or more different time servers.
If you have only two time servers, you should specify the Ntpserver UseAsFallbackOnly flag 0x2 to de-prioritize one of them. For example, if you want to prioritize ntpserver. Additionally, you can run the following command and read the value of NtpServer in the output:. In order for W32tm. Then, to adjust the computer clock by using the clock rate, W32tm.
This algorithm varies depending on the version of Windows:. MaxAllowedPhaseOffset is configurable in the registry. However, the registry parameter is measured in seconds instead of clock ticks. This command produces output that resembles the following. The output presents the poll interval in both clock ticks and in seconds. The equations use the value measured in seconds the value in parentheses. The output presents the clock rate in seconds.
To see the SystemClockRate value in clock ticks, use the following formula:. For example, if SystemClockRate is 0.
For full descriptions of the configurable parameters and their default values, see Config entries later in this article. The following examples show how to apply these calculations for Windows Server R2 and earlier versions. In this case, if you want to set the clock back slowly, you would also have to adjust the values of PhaseCorrectRate or UpdateInterval in the registry to make sure that the equation result is TRUE.
The Windows Time service stores a number of configuration properties as registry entries. It stores configuration information that the policies define in the Windows registry, and then uses those registry entries to configure the registry entries specific to the Windows Time service. As a result, the values defined by Group Policy overwrite any pre-existing values in the Windows Time service section of the registry.
Some of the preset GPO settings differ from the corresponding default Windows Time service registry entries. If you have two or more domain controllers you need to find the one that is acting as the PDC. To sync it with a time source open up a command prompt and perform the following:. The X's can be the IP address of the time server or the domain name of a time server such as time-a. Next you need to sync all of your client PC's to the domain controller.
You can do the following from the command line. You can remotely do these commands using psexec from SysInternals if you have a lot of client machines.
I want to use the internal clock on the server as my clock. I have changed the status to Manual, but it is not finding the internal time. I get a message that it could not resync becuase no time date was available after I restarted. How do I get my remaining servers to get the time from the PDC? I have set up the PDC with the information above, but unsure how then re-sync the remaining forest servers to use the PDC and the primary time source.
Can someone be so kind as to provide the proper commands for setting the external time source on the PDCE and then the commands to run on the other DCs for Windows servers. I don't have a test lab to play with and can't 'just try things' on the client site. Hi, Because I don't know your infrastructure design at all so I was assuming In fact, there is no issue if you have Linux NTP server in the inafrastructure as long as your Linux has samba and winbind for kerberos authentication with AD.
If not, AD will not regard them as a domain member and therefore authentication failed. If you look at the event 22 on your event log, the full detail explaination of the event is below.
I will not be able to support you any further in this forum as this will be mainly a Linux NTP server issue. Thank you. Remember to Vote as helpful for others and accept the the proposed Answer if it is relevant to build KB in this Forum. A useful link for your reference to configure time source at your place.
Do not use the "net time" command on Windows and later. When you run net time without option, the workstation will show one time source on the network. So your client display is normal.
If there are more inquiries on this issue, please feel free to let us know. Rick Tan. TechNet Community Support. Am I right? I hope I have answered your question.
NET TIME synchronizes the computer's clock with that of another computer or domain, or displays the time for a computer or domain. When used without options on a Windows Server domain, it displays the current date and time at the computer designated as the time server for the domain.
Please use w32tm. It is good reading for all administrators. Thank you all very much for your replies. Very helpful. And I will read the recommended articles. Rick, you are saying " When you run net time without option, the workstation will show one time source on the network. Does it pick a specific server or just one at random?
That is might be the root of my question - what is the 'main time server'. Can you clarify? I want to make sure the PDCE is configured as the main time server. This article provides a resolution for the issue that time synchronization may not succeed when you try to synchronize with a non-Windows NTP server.
As this problem occurs, the following events may be recorded in the System log. This problem may occur when your computer sends synchronization requests by using symmetric active mode. By default, Windows Server domain controllers are configured as time servers and use symmetric active mode to send synchronization requests.
Some NTP servers that don't run Windows respond only to requests that use client mode.
0コメント