Set time source windows 2003

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. This allows the registry to be restored in the event of erroneous modification. This makes the PDC announce itself as a reliable time source. However, the system clock can drift over time and is not referenced to an accurate time source.

Additionally, Windows Time will periodically generate system event log warnings indicating that the PDC should be configured to synchronise to an external time source. This warning can be ignored. Set this registry entry to the value '5'. This entry should be set to the value 1. Microsoft recommends a value of seconds which transposes to one poll every 15 minutes. If a time correction larger than the maximum is required the time service logs an Event in the Event Log.

A suitable value may be seconds 1 hour. After the registry entries have been correctly modified, the Windows Time service must be stopped and restarted. Would this override any sntp settings that may have been configured before? It just some of our members servers that I wanted to give the once over to. Well the time service has to be specifically configured via GPO to talk to the domain controller, or the best two domain controllers.

To have it well working, you need to configure it thru GPO, because defaults are very generic, and they very often drift a lot. Add a comment. Active Oldest Votes. Improve this answer. Tim Brigham Tim Brigham On a test server it is showing as not configured which leads me to believe it is picking it up from the DC which is good. Alex Berry Alex Berry 2, 12 12 silver badges 23 23 bronze badges.

That's not actually true. All domain members should get their time settings from a domain controller, but that doesn't mean they will, or that it can't be changed. Also, all machines will be getting their time from an NTP source W32time is an NTP source. 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 can be beneficial to other community members reading the thread. A computer uses one of the following methods to identify a time source to synchronize with: If the computer is not a member of a domain, it must be configured to synchronize with a specified time source. If the computer is a member server or workstation within a domain, by default, it follows the AD DS hierarchy and synchronizes its time with a domain controller in its local domain that is currently running the Windows Time service.

So the server is workstation logon DC server based on AD site and subnet which could show via command "set l". By they way, I have "Alert me' checked and an email address configured but I'm not getting Alerts so I don't always reply as quickly as I'd like.

What is you PDCE ipaddress? You can modify this from the command line by using the net time command. Should it? I just noticed this is Event Viewer. Even though the registry settings above would indicate the PDCe is configured with a time source, I get the following:. Description: The time service has not synchronized the system time for seconds because none of the time service providers provided a usable time stamp.

The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. Monitor the system events displayed in the Event Viewer to make sure that a more serious problem does not exist. NtpServer cannot provide secure signed time to the client and will ignore the request.

The error was: Not enough storage is available to process this command. Occassionally the above message also end with "the specified user does not exist" or ".