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. Windows loads these settings into the policy area of the registry under the following subkey:. Then Windows uses the policy settings to configure the related Windows Time service registry entries under the following subkey:.
The following table lists the policies that you can configure for the Windows Time service, and the registry subkeys that those policies affect. When you remove a Group Policy setting, Windows removes the corresponding entry from the policy area of the registry. This information is provided as a reference for use in troubleshooting and validation.
Windows registry keys are used by W32Time to store critical information. Don't change these values. Modifications to the registry are not validated by the registry editor or by Windows before they are applied.
If the registry contains invalid values, Windows may experience unrecoverable errors. 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. Windows Time Service Technical Reference. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. In this article. Registers the time service to run as a service, and adds default configuration to the registry. Unregisters the time service, and removes all configuration information from the registry.
Displays a strip chart of the offset between this computer and another computer. Dataonly —Display only the data, without graphics.
NO —Do not synchronize from any server. ALL —Synchronize from both manual and domain peers. This setting is meaningful only on domain controllers. YES —This computer is a reliable time service. NO —This computer is not a reliable time service. The rate of change and the magnitude of the change when using Ubuntu seemed to be slower than when using windows 7 professional.
Other than that I didn't know what conclusions could be drawn. Some HP technicians concluded it was then a hardware related problem. So the motherboard was then replaced. Another HP technician concluded after the motherboard was replaced was that the comparison with Ubuntu indicated that it was not a hardware related issue but he already had the knowledge that the motherboard was replaced.
Is it a software related issue? Is it a bios related issue? Is it a driver related issue? HP had emailed to me software which generated files. One of the files that they were concerned about was whether the proper bios or proper image had been installed from the factory.
One of the HP reps commented in her email that it was unclear. A more senior HP rep indicated that it was the proper bios for the system. On another web site I had posted this information and someone suggested flushing the bios. When I had inquired I never got an explanation of what they meant by flush the bios. It was reset once when I worked with HP over the telephone. And the bios was reset again when HP replaced the motherboard. Reinstalling the operating system is a task that I have not yet done.
Is that something to do even if no integrity violations are found? Using windows 7 professional configure internet time update now multiple times will eventually display exact time on time. Then within a few seconds it will display time behind.
Ubuntu is new to me so I did not know how to reset or update time. Using it time was always ahead after a fresh boot to the external flash drive.
Then the longer I used it the more progressive the time ahead. Again the magnitude and rate of change appeared to be slower than with the windows.
I've been working on this time problem for 5 months. It's very unclear to me what the problem is with the time or how to work it up.
The time synchronization at some point was deliberately turned off to evaluate the time problem. HP was wondering whether it was a network related issue. The computer time malfunctioned the same way whether it was or was not connected via ethernet or wireless. So this step of turning off the time synchronization was done to exclude network issues.
The first w32tm administrative command prompt command was done with the synchronization off. All of the others were done with it on. The computer now is displaying more delayed time that it had. Typically it would display delayed times up to 1 minute 15 to 20 seconds and then reset back to approximately 5 seconds delay. How it resets on its own is unclear to me but this happened on a regular basis.
Over the past few days the time delay is nearly 5 minutes and it automatically resets to a delay over 3 minutes. I have not rebooted and only placed the computer to sleep each night. So a reboot may reset it back to a 1 minute and 15 to 20 delay reset.
When viewing the results of the w32tm commands above it had switched to displaying unspecified in the last few results. This was what was displayed when the time had synchronization off. With the worse time delay and with the w32tm displaying unspecified I am wondering whether it is no longer synchronizing. The time synchronization is set to synchronize once per week as per the picture above. I had not looked in the event log since the time synchronization was deliberately turned off to check for network related issues.
If you want me to look for something there please indicate how to go about it. In the next few days I plan to reboot and follow the steps you have above. And the bios was reset again when HP replaced the motherboard How it resets on its own is unclear to me but this happened on a regular basis With the worse time delay and with the w32tm displaying unspecified I am wondering whether it is no longer synchronizing In the next few days I plan to reboot and follow the steps you have above Being that HP is involved in the effort to resolve the problem, and that they have supplied a replacement motherboard , I would think that the BIOS would be at it's latest available version, you can ask them if it is and you should also ask them if the the latest chipset drivers are installed on your operating system.
0コメント