Microsoft recommends a setting of 1 hour or 30 minutes Restart the windows time service. When Windows for Workgroups is deployed, you have to manually configure time synchronization settings. You need to specify the time server that the Windows Time Service is to use as a reference clock. Alternatively, you can utilize the date and time properties applet from the control panel. Generally, it is because the time reference was in an unsynchronized state. The applet will also periodically automatically synchronize with the specified reference.
Andy Shinton has spent his entire career within the IT industry, mainly in the Time and Frequency sector. The Fundamentals Of Time Synchronization. Then type the NTP server address. Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff microsoft. I always use a free tool timesynctool and I install this on all of my workstations.
You can search for it on the web. Just search for it on the web to get the command syntax from TechNet. You may also need to make sure that your Windows firewall is allowing NTP traffic from the other workstations if you have it turned on.
Office Office Exchange Server. Not an IT pro? Internet Explorer TechCenter. Sign in. United States English. Ask a question. Some of the parameters in the registry are measured in clock ticks and some are measured in seconds. To convert the time from clock ticks to seconds, use these conversion factors:. Note Zero is not a valid value for the FrequencyCorrectRate registry entry. HoldPeriod All versions Controls the period of time for which spike detection is disabled in order to bring the local clock into synchronization quickly.
A spike is a time sample indicating that time is off a number of seconds, and is usually received after good time samples have been returned consistently. The default value on domain members is 5. The default value on stand-alone clients and servers is 5. LargePhaseOffset All versions Specifies that a time offset greater than or equal to this value in 10 -7 seconds is considered a spike. A network disruption such as a large amount of traffic might cause a spike.
A spike will be ignored unless it persists for a long period of time. The default value on domain members is The default value on stand-alone clients and servers is It contains reserved data that is used by the Windows operating system, and any changes to this setting can cause unpredictable results. MaxAllowedPhaseOffset All versions Specifies the maximum offset in seconds for which W32Time attempts to adjust the computer clock by using the clock rate.
When the offset exceeds this rate, W32Time sets the computer clock directly. The default value for domain members is The default value for stand-alone clients and servers is 1. The default value for stand-alone clients and servers is MaxNegPhaseCorrection All versions Specifies the largest negative time correction, in seconds, that the service makes. If the service determines that a change larger than this is required, it logs an event instead. 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.
0コメント