Windows server 2008 set time automatically

This depends on the startup timing of the Windows operating system in question. In this situation, the service triggers an automatic stop after the success of the Time Synchronization task.

Therefore, if you use Method 3, you must disable the "Time Synchronization to avoid the task to start the Windows Time service" task. To do this, follow these steps:. The Windows Time service on a workgroup computer is not started automatically at system startup by the Trigger-Start service.

However, the Windows Time service is started by the Time Synchronization setting that's registered on the Task Scheduler Library at a. Therefore, the default setting can be kept as is.

Need more help? Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Click Start , click Shutdown , and then type a reason in the Comment text box. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Important The autologon feature is provided as a convenience. Important This section, method, or task contains steps that tell you how to modify the registry. Note To bypass the AutoAdminLogon process and to log on as a different user, press and hold the Shift key after you log off or after Windows restarts. This registry change does not work if the Logon Banner value is defined on the server either by a Group Policy object GPO or by a local policy.

When the policy is changed so that it does not affect the computer, the autologon feature works as expected. This behavior is by design. This behavior is caused by a change in Windows 8. To work around this behavior in Windows 8. 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. 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.