Configuring Time Sync In the default configuration, which is also best practice, time sync settings follow the domain hierarchy for all servers except the PDC Emulator. Troubleshooting Time Sync Issues There are a few ways you'll know that there are issues with Windows Time in the domain: Visibly observing that the time on the servers is wrong or doesn't match other servers in the domain Receiving authentication errors pointing to a time or date difference causing an issue Warnings in the System event log with a source of Time-Service If you notice any of the above, you'll need to do some troubleshooting.
This command will reach out to the target server and compare the local time to the server's time. If it's unable to contact the target NTP server, you'll see error codes instead. If that happens, you may have network issues, such as a firewall, preventing communication with the NTP server. You would run this command after making other changes to see if the issues are resolved.
If the time service is simply not behaving, you can use these commands to completely re-register the service. Note that this will remove all configuration related to Windows Time and restore it to default: Net Stop W32time W32tm. The log will contain an entry for each operation that the service performs.
It can be difficult to sort through all of the information, but it can be extremely valuable to see each step in detail. If a single member server is wrong, review the System event log to determine which DCs it is trying to sync from, and ensure those DCs are working correctly. Sometimes, a failure will cascade through the domain.
A networking issue may prevent a set of DCs from syncing with the PDC, which can then cause the member servers in that network to stop as well. An NTP server that acquires its time directly from a reference clock occupies a stratum that is one level higher than that of the reference clock. Resources that acquire time from the NTP server are two steps away from the reference clock, and therefore occupy a stratum that is two higher than the most accurate time source, and so on.
Otherwise, please use IP address. This value indicates that this system is configured to sync with an external time source. If the value is 0XA, it means this system will not sync with any external time source but would sync with itself. If required, restart the new PDC emulator. Run the following command from command prompt of the old PDC Emulator :. After running the first sync, the server detected the newly configured external time source and marked it as root Stratum value 1.
Therefore, the new value of the PDC emulator has been changed to one level up, which is 2. Configuring PDC Emulator and external time source is only one part of the time service configuration.
There are still many other points which we need to consider. Some of the important points are described below. Force all windows systems to use Domain Controller as their time source. By default in Active Directory domain environment clients synchronize their time with domain controllers option Nt5DS — synchronize time to domain hierarchy.
Typically, this behavior does not need to be reconfigured. However, if you want to ensure that the default behavior would not be overridden by someone on the client side, you can force a Group Policy to push the configuration.
Configure the options then append, 0x1 to the NtpServer field so that it reads yourdc. If enabled, guest machines will draw time from the physical host they are running on.
Do not use DHCP scope option unless it is specifically mentioned in any documentation. It waits for a response on the same originating port.
Configure Static Devices. For such devices, you need to configure the time sources statically, from the device console. The downside is, if NTP server name would be changed, you have to change these settings manually. Compare the PDC emulator clock time with any world clock time and observe the difference in seconds. The time difference between Domain Controllers should be less than 1 second in an entire forest.
This value means that the service always corrects the time. The default value for domain controllers is , 48 hrs. The default value for stand-alone clients and servers is 54, 15 hrs. MaxPollInterval All versions Specifies the largest interval, in log2 seconds, allowed for the system polling interval. Note that while a system must poll according to the scheduled interval, a provider can refuse to produce samples when requested to do so.
The default value for domain controllers is MaxPosPhaseCorrection All versions Specifies the largest positive time correction in seconds that the service makes. MinPollInterval All versions Specifies the smallest interval, in log base 2 seconds, allowed for the system polling interval. Note that while a system does not request samples more frequently than this, a provider can produce samples at times other than the scheduled interval.
The default value for domain controllers is 6. PhaseCorrectRate All versions Controls the rate at which the phase error is corrected. Specifying a small value corrects the phase error quickly, but might cause the clock to become unstable.
If the value is too large, it takes a longer time to correct the phase error. The default value on domain members is 1. The default value on stand-alone clients and servers is 7. Note Zero is not a valid value for the PhaseCorrectRate registry entry. PollAdjustFactor All versions Controls the decision to increase or decrease the poll interval for the system. The larger the value, the smaller the amount of error that causes the poll interval to be decreased.
RequireSecureTimeSyncRequests Windows 8 and later versions Controls whether or not the DC will respond to time sync requests that use older authentication protocols. If enabled set to 1 , the DC will not respond to requests using such protocols. This is a boolean setting, and the default value is 0. SpikeWatchPeriod All versions Specifies the amount of time that a suspicious offset must persist before it is accepted as correct in seconds.
The default value on stand-alone clients and workstations is TimeJumpAuditOffset All versions An unsigned integer that indicates the time jump audit threshold, in seconds. If the time service adjusts the local clock by setting the clock directly, and the time correction is more than this value, then the time service logs an audit event. UpdateInterval All versions Specifies the number of clock ticks between phase correction adjustments.
The default value for domain members is 30, The default value for stand-alone clients and servers is , Note Zero is not a valid value for the UpdateInterval registry entry. The default value on stand-alone clients and servers is 1. The default value on stand-alone clients and servers is 0x1.
The NtpServer is a time server that responds to client time requests on the network by returning time samples that are useful for synchronizing the local clock. LargeSampleSkew All versions Specifies the large sample skew for logging, in seconds. Events will be logged for this setting only when EventLogFlags is explicitly configured for 0x2 large sample skew. The default value on domain members is 3. The default value on stand-alone clients and servers is 3.
ResolvePeerBackOffMaxTimes All versions Specifies the maximum number of times to double the wait interval when repeated attempts to locate a peer to synchronize with fail. A value of zero means that the wait interval is always the minimum. The default value on domain members is 7. ResolvePeerBackoffMinutes All versions Specifies the initial interval to wait, in minutes, before attempting to locate a peer to synchronize with.
SpecialPollInterval All versions Specifies the special poll interval, in seconds, for manual peers. When the SpecialInterval 0x1 flag is enabled, W32Time uses this poll interval instead of a poll interval determined by the operating system. The default value on domain members is 3, The default value on stand-alone clients and servers is , It contains reserved data that is used by the Windows operating system. It specifies the time, in seconds, before W32Time will resynchronize after the computer has restarted.
Any changes to this setting can cause unpredictable results. The default value on both domain members and on stand-alone clients and servers is left blank.
The following registry entries are not a part of the W32Time default configuration but can be added to the registry to obtain enhanced logging capabilities. By default, the Windows Time service logs an event every time that it switches to a new time source. These are the global Group Policy settings and default values for the Windows Time service. Skip to main content. This browser is no longer supported.
Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Caution Don't use the Net time command to configure or set a computer's clock time when the Windows Time service is running. Note If you have a computer with multiple network adapters is multi-homed , you cannot enable the Windows Time service based on a network adapter. Important Windows Server has improved the time synchronization algorithms to align with RFC specifications.
Note 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. Note When you remove a Group Policy setting, Windows removes the corresponding entry from the policy area of the registry.
Warning This information is provided as a reference for use in troubleshooting and validation. Note Some of the parameters in the registry are measured in clock ticks and some are measured in seconds. Ticks Property. Submit and view feedback for This product This page. View all page feedback. In this article. Registers the Windows Time service to run as a service and adds its default configuration information to the registry. Unregisters the Windows Time service and removes all of its configuration information from the registry.
Monitors the Windows Time service. Converts a Windows NT system time measured in 10 -7 -second intervals starting from 0h 1-Jan into a readable format. Converts an NTP time measured in 2 -second intervals starting from 0h 1-Jan into a readable format. Tells a computer that it should resynchronize its clock as soon as possible, throwing out all accumulated error statistics. Displays a strip chart of the offset between this computer and another computer.
Displays the values associated with a given registry key. Displays the computer's Windows Time service information. Enables or disables the local computer Windows Time service private log. Controls whether this computer is marked as a reliable time server. A computer is not marked as reliable unless it is also marked as a time server.
Not a time server 0x Always time server 0x Automatic time server 0x
0コメント