How To Check Time Sync On Windows 2012
This browser is no longer supported.
Upgrade to Microsoft Edge to have advantage of the latest features, security updates, and technical support.
Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows x, Azure Stack HCI, versions 21H2 and 20H2
The Windows Time service (W32Time) synchronizes the date and time for all computers managed by Active Directory Domain Services (AD DS). This commodity covers the different tools and settings used to manage the Windows Time service.
Past default, a estimator that is joined to a domain synchronizes time through a domain hierarchy of fourth dimension sources. Nonetheless, if a calculator has been manually configured to synchronize from a specific time source, perhaps considering it was formerly non joined to a domain, you can reconfigure the reckoner to begin automatically sourcing its fourth dimension from the domain bureaucracy.
Near domain-joined computers have a time customer type of NT5DS, which ways that they synchronize fourth dimension from the domain hierarchy. An exception to this is the domain controller, which functions equally the primary domain controller (PDC) emulator operations master for the root wood domain. The PDC emulator operations main in turn is usually configured to synchronize time with an external time source.
Y'all tin achieve down to one-millisecond time accuracy in your domain. For more data, see Support boundary for high-accuracy time and see Accurate Fourth dimension for Windows Server 2016.
Caution
Don't employ the Cyberspace fourth dimension command to configure or set a figurer's clock time when the Windows Time service is running.
Also, on older computers that run Windows XP or before, the Net time /querysntp command displays the name of a Network Fourth dimension Protocol (NTP) server with which a reckoner is configured to synchronize, but that NTP server is used only when the reckoner'southward time client is configured equally NTP or AllSync. This command has since been deprecated.
Network port
The Windows Time service follows the Network Time Protocol (NTP) specification, which requires the use of UDP port 123 for all fourth dimension synchronization. Whenever the computer synchronizes its clock or provides time to another reckoner, it happens over UDP port 123. This port is exclusively reserved by the Windows Time service.
Note
If you accept a calculator with multiple network adapters (is multi-homed), you cannot enable the Windows Fourth dimension service based on a network adapter.
You tin can use the command-line tool W32tm.exe to configure Windows Time service settings and to diagnose estimator time bug. W32tm.exe is the preferred command-line tool for configuring, monitoring, and troubleshooting the Windows Time service. W32tm.exe is included with Windows XP and later and Windows Server 2003 and later.
Membership in the local Administrators group is required to run W32tm.exe locally, while membership in the Domain Admins grouping is required to run W32tm.exe remotely.
Run W32tm.exe
- In the Windows search bar, enter cmd.
- Right-click Control Prompt, and so select Run as administrator.
- At the command prompt, enter w32tm followed by the applicable parameter, as described below:
| Parameter | Description |
|---|---|
| /? | Displays the W32tm command-line assistance |
| /register | Registers the Windows Time service to run equally a service and adds its default configuration information to the registry. |
| /unregister | Unregisters the Windows Fourth dimension service and removes all of its configuration information from the registry. |
| /monitor [/domain:<domain name>] [/computers:<name>[,<proper name>[,<proper name>...]]] [/threads:<num>] | Monitors the Windows Time service. /domain: Specifies which domain to monitor. If no domain proper noun is given, or neither the /domain nor /computers choice is specified, the default domain is used. This pick might exist used more than in one case. /computers: Monitors the given list of computers. Computer names are separated by commas, with no spaces. If a name is prefixed with a *, it is treated as a PDC. This option might exist used more than once. /threads: Specifies the number of computers to analyze simultaneously. The default value is 3. The allowed range is 1-fifty. |
| /ntte <NT time epoch> | Converts a Windows NT organization time (measured in 10-7-2d intervals starting from 0h 1-January 1601) into a readable format. |
| /ntpte <NTP time epoch> | Converts an NTP time (measured in two-32-second intervals starting from 0h 1-January 1900) into a readable format. |
| /resync [/computer:<figurer>] [/nowait] [/rediscover] [/soft] | Tells a computer that it should resynchronize its clock equally soon as possible, throwing out all accumulated error statistics. /computer:<figurer>: Specifies the calculator that should resynchronize. If non specified, the local figurer will resynchronize. /nowait: do not wait for resynchronization to occur; render immediately. Otherwise, wait for resynchronization to complete before returning. /rediscover: Redetects the network configuration and rediscovers network sources, then resynchronizes. /soft: Resynchronizes past using existing error statistics. This is used for compatibility purposes. |
| /stripchart /computer:<target> [/period:<refresh>] [/dataonly] [/samples:<count>] [/rdtsc] | Displays a strip chart of the showtime between this computer and another computer. /computer:<target>: The computer to measure the commencement against. /period:<refresh>: The fourth dimension between samples, in seconds. The default is 2 seconds. /dataonly: Displays the data just, without graphics. /samples:<count>: Collects <count> samples, and so stops. If not specified, samples will exist collected until Ctrl+C is pressed. /rdtsc: For each sample, this pick prints comma-separated values forth with the headers RdtscStart, RdtscEnd, FileTime, RoundtripDelay, and NtpOffset instead of the text graphic.
|
| /config [/computer:<target>] [/update] [/manualpeerlist:<peers>] [/syncfromflags:<source>] [/LocalClockDispersion:<seconds>] [/reliable:(Aye|NO)] [/largephaseoffset:<milliseconds>]** | /computer:<target>: Adjusts the configuration of <target>. If non specified, the default is the local calculator. /update: Notifies the Windows Time service that the configuration has changed, causing the changes to take issue. /manualpeerlist:<peers>: Sets the transmission peer list to <peers>, which is a space-delimited list of DNS or IP addresses. When specifying multiple peers, this option must be enclosed in quotes. /syncfromflags:<source>: Sets what sources the NTP client should synchronize from. <source> should be a comma-separated list of these keywords (not case sensitive):
/reliable:(Yep|NO): Set whether this computer is a reliable time source. This setting is simply meaningful on domain controllers.
|
| /tz | Displays the current fourth dimension zone settings. |
| /dumpreg [/subkey:<key>] [/computer:<target>] | Displays the values associated with a given registry key. The default key is HKLM\System\CurrentControlSet\Services\W32Time (the root key for the Windows Time service). /subkey:<central>: Displays the values associated with subkey <key> of the default cardinal. /figurer:<target>: Queries registry settings for computer <target> |
| /query [/reckoner:<target>] {/source | /configuration | /peers | /status} [/verbose] | Displays the computer's Windows Time service information. This parameter was start made available for the Windows Fourth dimension client in Windows Vista and Windows Server 2008. /computer:<target>: Queries the information of <target>. If non specified, the default value is the local reckoner. /source: Displays the time source. /configuration: Displays the configuration of run fourth dimension and where the setting comes from. In verbose mode, display the undefined or unused setting as well. /peers: Displays a listing of peers and their status. /status: Displays Windows Time service status. /verbose: Sets the verbose mode to display more information. |
| /debug {/disable | {/enable /file:<name> /size:/<bytes> /entries:<value> [/truncate]}} | Enables or disables the local computer Windows Time service private log. This parameter was offset made bachelor for the Windows Fourth dimension client in Windows Vista and Windows Server 2008. /disable: Disables the private log. /enable: Enables the private log.
|
Set customer to use 2 fourth dimension servers
To set a customer computer to indicate to 2 unlike fourth dimension servers, i named ntpserver.contoso.com and some other named clock.adatum.com, type the post-obit command at the control prompt, and then press ENTER:
w32tm /config /manualpeerlist:"ntpserver.contoso.com clock.adatum.com" /syncfromflags:transmission /update Prepare client to sync time automatically from a domain source
To configure a client calculator that is currently synchronizing time using a manually-specified computer to synchronize time automatically from the Advertisement domain hierarchy, run the following following:
w32tm /config /syncfromflags:domhier /update net stop w32time net kickoff w32time Bank check client fourth dimension configuration
To check a client configuration from a Windows-based client computer that has a host name of contosoW1, run the post-obit command:
W32tm /query /reckoner:contosoW1 /configuration The output of this command displays a list of W32time configuration parameters that are set for the client.
Important
Windows Server 2016 has improved the time synchronization algorithms to align with RFC specifications. Therefore, if you want to set the local time customer to point to multiple peers, we recommended that you prepare iii or more dissimilar time servers.
If yous have simply ii fourth dimension servers, you should specify the Ntpserver UseAsFallbackOnly flag (0x2)to de-prioritize one of them. For instance, if you lot want to prioritize ntpserver.contoso.com over clock.adatum.com, run the post-obit command.
w32tm /config /manualpeerlist:"ntpserver.contoso.com,0x8 clock.adatum.com,0xa" /syncfromflags:manual /update Additionally, you can run the following command and read the value of NtpServer in the output:
reg query HKLM\Arrangement\CurrentControlSet\Services\W32Time\Parameters Configure computer clock reset
In guild for W32tm.exe to reset a calculator clock, it first checks the offset (CurrentTimeOffset, also known as Stage Offset) betwixt the current time and the reckoner clock time to determine whether the offset is less than the MaxAllowedPhaseOffset value.
-
CurrentTimeOffset≤MaxAllowedPhaseOffset: Adjust the computer clock gradually by using the clock rate. -
CurrentTimeOffset>MaxAllowedPhaseOffset: Set up the reckoner clock immediately.
Then, to adjust the computer clock past using the clock rate, W32tm.exe calculates a PhaseCorrection value. This algorithm varies depending on the version of Windows:
-
Windows Server 2016 and later versions:
PhaseCorrection_raw= |CurrentTimeOffset| ÷ (16 ×PhaseCorrectRate×pollIntervalInSeconds)
MaximumCorrection= |CurrentTimeOffset| ÷ (UpdateInterval÷ 100)
PhaseCorrection= min(PhaseCorrection_raw,MaximumCorrection) -
Windows Server 2012 R2 and earlier versions:
To get the SystemClockRate value, you lot can use the following command and catechumen information technology from seconds to clock ticks past using the formula of (seconds × 1,000 × 10,000):
PhaseCorrection= |CurrentTimeOffset| ÷ (PhaseCorrectRate×UpdateInterval)
All versions of Windows utilise the same terminal equation to check PhaseCorrection:
PhaseCorrection≤SystemClockRate÷ 2
Note
-
Windows Server 2019 and Windows 10 1809 have the same formula every bit [Windows Server 2016 and later versions] described to a higher place by applying cumulative updates from KB5006744 onwards.
-
These equations apply
PhaseCorrectRate,UpdateInterval,MaxAllowedPhaseOffset, andSystemClockRatemeasured in units of clock ticks. On Windows systems, 1 ms = ten,000 clock ticks. -
MaxAllowedPhaseOffsetis configurable in the registry. However, the registry parameter is measured in seconds instead of clock ticks. -
To run into the
SystemClockRateandpollIntervalInSecondsvalues (measured in seconds), open a Control Prompt window and so runW32tm /query /status /verbose. This command produces output that resembles the post-obit.
The output presents the poll interval in both clock ticks and in seconds. The equations utilize the value measured in seconds (the value in parentheses).
The output presents the clock rate in seconds. To see theSystemClockRatevalue in clock ticks, use the following formula:(
value in seconds) × 1,000 × 10,000For example, if
SystemClockRateis 0.0156250 seconds, the value that the equation uses is 156,250 clock ticks. For full descriptions of the configurable parameters and their default values, run across Config entries later in this article.
The following examples testify how to employ these calculations for Windows Server 2012 R2 and earlier versions.
Case: Organization clock rate off by four minutes
Your computer clock time is 11:05 and the bodily electric current time is 11:09:
PhaseCorrectRate= 1
UpdateInterval= 30,000 clock ticks
SystemClockRate= 156,000 clock ticks
MaxAllowedPhaseOffset= ten min = 600 seconds = 600 × 1,000 × 10,000 = half-dozen,000,000,000 clock ticks|
CurrentTimeOffset| = 4 min = 4 × 60 × 1,000 × 10,000 = two,400,000,000 clock ticks
Is CurrentTimeOffset ≤ MaxAllowedPhaseOffset?
ii,400,000,000 ≤ 6,000,000,000: TRUE
AND does it satisfy the post-obit equation?
(|
CurrentTimeOffset| ÷ (PhaseCorrectRate×UpdateInterval) ≤SystemClockRate÷ 2)
Is 2,400,000,000 / (30,000 × 1) ≤ 156,000 ÷ ii
80,000 ≤ 78,000: FALSE
Therefore, W32tm.exe would set the clock dorsum immediately.
Note
In this case, if you want to fix the clock dorsum slowly, you would too have to adjust the values of PhaseCorrectRate or UpdateInterval in the registry to make sure that the equation result is True.
Example: Arrangement clock charge per unit off by iii minutes
Your estimator clock time is eleven:05 and the bodily electric current time is xi:08:
PhaseCorrectRate= i
UpdateInterval= 30,000 clock ticks
SystemClockRate= 156,000 clock ticks
MaxAllowedPhaseOffset= 10 min = 600 seconds = 600 × i,000 × 10,000 = vi,000,000,000 clock ticks|
CurrentTimeOffset| = 3 mins = iii × 60 × 1,000 × 10,000 = 1,800,000,000 clock ticks
Is CurrentTimeOffset ≤ MaxAllowedPhaseOffset?
one,800,000,000 ≤ half-dozen,000,000,000: TRUE
AND does it satisfy the following equation?
(|
CurrentTimeOffset| ÷ (PhaseCorrectRate×UpdateInterval) ≤SystemClockRate÷ 2)
Is 3 mins × (1,800,000,000) ÷ (thirty,000 × ane) ≤ 156,000 ÷ ii
Is 60,000 ≤ 78,000: True
In this case, the clock will be set dorsum slowly.
Using Local Grouping Policy Editor
The Windows Fourth dimension service stores a number of configuration properties equally registry entries. You tin can utilize Group Policy Objects (GPOs) in Local Grouping Policy Editor to configure almost of this data. For case, y'all can use GPOs to configure a reckoner to exist an NTPServer or NTPClient, configure the time synchronization machinery, or configure a computer to exist a reliable time source.
Notation
Group Policy settings for the Windows Time service tin be applied on Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, and Windows Server 2008 R2 domain controllers and can be applied to computers running Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, and Windows Server 2008 R2.
Windows stores the Windows Time service policy data in the Local Group Policy Editor under Computer Configuration\Administrative Templates\Organisation\Windows Time Service. It stores configuration information that the policies ascertain in the Windows registry, and so uses those registry entries to configure the registry entries specific to the Windows Time service. Equally a result, the values defined by Group Policy overwrite whatever 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.
For example, suppose yous edit policy settings in the Time Providers\Configure Windows NTP Customer policy. Windows loads these settings into the policy expanse of the registry nether the following subkey:
HKLM\Software\Policies\Microsoft\W32time\TimeProviders\NtpClient
And so Windows uses the policy settings to configure the related Windows Time service registry entries nether the following subkey:
HKLM\Arrangement\CurrentControlSet\Services\W32Time\Fourth dimension Providers\NTPClient\\
The following table lists the policies that yous can configure for the Windows Time service, and the registry subkeys that those policies affect.
Note
When you remove a Group Policy setting, Windows removes the corresponding entry from the policy area of the registry.
| Group Policy1 | Registry locations2, 3 |
|---|---|
| Global Configuration Settings | W32Time W32Time\Config W32Time\Parameters |
| Time Providers\Configure Windows NTP Client | W32Time\TimeProviders\NtpClient |
| Time Providers\Enable Windows NTP Client | W32Time\TimeProviders\NtpClient |
| Time Providers\Enable Windows NTP Server | W32Time\TimeProviders\NtpServer |
one Category path: Computer Configuration\Administrative Templates\Organisation\Windows Time Service
two Subkey: HKLM\SOFTWARE\Policies\Microsoft
3 Subkey: HKLM\System\CurrentControlSet\Services
Windows registry reference
Warning
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 practical. If the registry contains invalid values, Windows may experience unrecoverable errors.
The Windows Time service stores data in the registry at the HKLM\Arrangement\CurrentControlSet\Services\W32Time path under the following subkeys:
- \Config
- \Parameters
- \TimeProviders\NtpClient
- \TimeProviders\NtpServer
In the post-obit tables, "All versions" refers to Windows seven, Windows 8, Windows x, Windows Server 2008 and Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019.
Note
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:
- 1 minute = 60 sec
- 1 sec = 1000 ms
- 1 ms = ten,000 clock ticks on a Windows organisation, as described at DateTime.Ticks Belongings.
For example, v minutes becomes v × sixty × 1000 × 10000 = iii,000,000,000 clock ticks.
Config entries
The Config subkey entries are located at HKLM\Arrangement\CurrentControlSet\Services\W32Time\Config.
| Registry entry | Versions | Description |
|---|---|---|
| AnnounceFlags | All versions | Controls whether this estimator is marked equally a reliable fourth dimension server. A estimator is not marked as reliable unless information technology is as well marked as a fourth dimension server.
The default value for domain members is 10. The default value for stand-alone clients and servers is ten. |
| ChainDisable | Controls whether or non the chaining mechanism is disabled. If chaining is disabled (set to 0), a read-just domain controller (RODC) can synchronize with any domain controller, but hosts that do not have their passwords buried on the RODC will not exist able to synchronize with the RODC. This is a boolean setting, and the default value is 0. | |
| ChainEntryTimeout | Specifies the maximum amount of fourth dimension that an entry tin can remain in the chaining tabular array before the entry is considered to exist expired. Expired entries may exist removed when the next asking or response is processed. The default value is 16 (seconds). | |
| ChainLoggingRate | Controls the frequency at which an upshot that indicates the number of successful and unsuccessful chaining attempts is logged to the System log in Event Viewer. The default is 30 (minutes). | |
| ChainMaxEntries | Controls the maximum number of entries that are immune in the chaining table. If the chaining table is total and no expired entries can be removed, any incoming requests are discarded. The default value is 128 (entries). | |
| ChainMaxHostEntries | Controls the maximum number of entries that are allowed in the chaining tabular array for a particular host. The default value is 4 (entries). | |
| ClockAdjustmentAuditLimit | Windows Server 2016 Version 1709 and subsequently versions; Windows ten Version 1709 and subsequently versions | Specifies the smallest local clock adjustments that may exist logged to the W32time service event log on the target computer. The default value is 800 (parts per million - PPM). |
| ClockHoldoverPeriod | Windows Server 2016 Version 1709 and later versions; Windows 10 Version 1709 and afterward versions | Indicates the maximum number of seconds a system clock tin can nominally agree its accuracy without synchronizing with a time source. If this menses of time passes without W32time obtaining new samples from any of its input providers, W32time initiates a rediscovery of fourth dimension sources. Default: seven,800 seconds. |
| EventLogFlags | All versions | Controls which events that the time service logs.
|
| FrequencyCorrectRate | All versions | Controls the charge per unit at which the clock is corrected. If this value is too small, the clock is unstable and overcorrects. If the value is besides large, the clock takes a long fourth dimension to synchronize. The default value on domain members is 4. The default value on stand-alone clients and servers is 4. Note |
| HoldPeriod | All versions | Controls the flow of time for which spike detection is disabled in social club to bring the local clock into synchronization quickly. A spike is a fourth dimension sample indicating that fourth dimension is off a number of seconds, and is usually received after good time samples accept been returned consistently. The default value on domain members is five. The default value on stand-lone clients and servers is 5. |
| LargePhaseOffset | All versions | Specifies that a fourth dimension offset greater than or equal to this value in 10-7 seconds is considered a spike. A network disruption such as a big corporeality of traffic might crusade a fasten. A spike will be ignored unless it persists for a long period of fourth dimension. The default value on domain members is 50000000. The default value on stand-alone clients and servers is 50000000. |
| LastClockRate | All versions | Maintained by W32Time. Information technology contains reserved information that is used by the Windows operating system, and any changes to this setting tin crusade unpredictable results. The default value on domain members is 156250. The default value on stand up-alone clients and servers is 156250. |
| LocalClockDispersion | All versions | Controls the dispersion (in seconds) that you must assume when the just fourth dimension source is the born CMOS clock. The default value on domain members is x. The default value on stand-alone clients and servers is 10. |
| MaxAllowedPhaseOffset | All versions | Specifies the maximum start (in seconds) for which W32Time attempts to suit the computer clock by using the clock rate. When the outset exceeds this rate, W32Time sets the reckoner clock straight. The default value for domain members is 300. The default value for stand-alone clients and servers is 1. |
| MaxClockRate | All versions | Maintained by W32Time. It contains reserved information that is used past the Windows operating system, and any changes to this setting can crusade unpredictable results. The default value for domain members is 155860. The default value for stand-alone clients and servers is 155860. |
| MaxNegPhaseCorrection | All versions | Specifies the largest negative fourth dimension correction, in seconds, that the service makes. If the service determines that a change larger than this is required, it logs an issue instead. Annotation The default value for domain members is 0xFFFFFFFF (hexadecimal). The default value for domain controllers is 172,800 (48 hrs). The default value for stand-alone clients and servers is 54,000 (15 hrs). |
| MaxPollInterval | All versions | Specifies the largest interval, in log2 seconds, immune for the system polling interval. Note that while a system must poll co-ordinate to the scheduled interval, a provider tin decline to produce samples when requested to exercise so. The default value for domain controllers is 10. The default value for domain members is 15. The default value for stand-lone clients and servers is 15. |
| MaxPosPhaseCorrection | All versions | Specifies the largest positive fourth dimension correction in seconds that the service makes. If the service determines that a alter larger than this is required, information technology logs an consequence instead. Note The default value for domain members is 0xFFFFFFFF (hexadecimal). The default value for domain controllers is 172,800 (48 hrs). The default value for stand up-alone clients and servers is 54,000 (15 hrs). |
| MinClockRate | All versions | Maintained by W32Time. It contains reserved data that is used by the Windows operating organisation, and any changes to this setting tin can cause unpredictable results. The default value for domain members is 155860. The default value for stand up-alone clients and servers is 155860. |
| MinPollInterval | All versions | Specifies the smallest interval, in log base of operations two seconds, immune for the arrangement polling interval. Annotation that while a system does not asking samples more frequently than this, a provider can produce samples at times other than the scheduled interval. The default value for domain controllers is half dozen. The default value for domain members is ten. The default value for stand-lonely clients and servers is 10. |
| PhaseCorrectRate | All versions | Controls the rate at which the phase error is corrected. Specifying a small value corrects the phase error quickly, merely might crusade the clock to get unstable. If the value is also large, it takes a longer time to correct the phase error. The default value on domain members is ane. The default value on stand-alone clients and servers is 7. Notation |
| PollAdjustFactor | All versions | Controls the decision to increase or decrease the poll interval for the system. The larger the value, the smaller the corporeality of error that causes the poll interval to be decreased. The default value on domain members is 5. The default value on stand-lonely clients and servers is v. |
| RequireSecureTimeSyncRequests | Windows viii and after versions | Controls whether or not the DC will respond to time sync requests that use older hallmark protocols. If enabled (set to 1), the DC will non 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 earlier it is accepted as correct (in seconds). The default value on domain members is 900. The default value on stand-solitary clients and workstations is 900. |
| TimeJumpAuditOffset | All versions | An unsigned integer that indicates the fourth dimension jump audit threshold, in seconds. If the fourth dimension service adjusts the local clock past setting the clock directly, and the time correction is more this value, then the fourth dimension service logs an audit issue. |
| UpdateInterval | All versions | Specifies the number of clock ticks between phase correction adjustments. The default value for domain controllers is 100. The default value for domain members is 30,000. The default value for stand-alone clients and servers is 360,000. Annotation |
| UtilizeSslTimeData | Windows versions later than Windows 10 build 1511 | Value of one indicates that W32Time uses multiple SSL timestamps to seed a clock that is grossly inaccurate. |
Parameters entries
The Parameters subkey entries are located at HKLM\Organisation\CurrentControlSet\Services\W32Time\Parameters.
| Registry entry | Versions | Description |
|---|---|---|
| AllowNonstandardModeCombinations | All versions | Indicates that not-standard way combinations are allowed in synchronization between peers. The default value for domain members is 1. The default value for stand up-solitary clients and servers is ane. |
| NtpServer | All versions | Specifies a infinite-delimited list of peers from which a reckoner obtains time stamps, consisting of 1 or more DNS names or IP addresses per line. Each DNS name or IP address listed must exist unique. Computers connected to a domain must synchronize with a more reliable fourth dimension source, such as the official U.S. time clock.
In that location is no default value for this registry entry on domain members. The default value on stand up-lonely clients and servers is time.windows.com,0x1. |
| ServiceDll | All versions | Maintained past W32Time. Information technology contains reserved data that is used past the Windows operating system, and whatsoever changes to this setting tin can cause unpredictable results. The default location for this DLL on both domain members and stand-alone clients and servers is %windir%\System32\W32Time.dll. |
| ServiceMain | All versions | Maintained past W32Time. It contains reserved data that is used by the Windows operating organization, and whatsoever changes to this setting can crusade unpredictable results. The default value on domain members is SvchostEntry_W32Time. The default value on stand-lonely clients and servers is SvchostEntry_W32Time. |
| Type | All versions | Indicates which peers to accept synchronization from:
|
NtpClient entries
The NtpClient subkey entries are located at HKLM\Organisation\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient
| Registry entry | Version | Description |
|---|---|---|
| AllowNonstandardModeCombinations | All versions | Indicates that non-standard way combinations are allowed in synchronization betwixt peers. The default value for domain members is i. The default value for stand up-alone clients and servers is i. |
| CompatibilityFlags | All versions | Specifies the post-obit compatibility flags and values:
|
| CrossSiteSyncFlags | All versions | Determines whether the service chooses synchronization partners exterior the domain of the computer. The options and values are:
|
| DllName | All versions | Specifies the location of the DLL for the time provider. The default location for this DLL on both domain members and stand-alone clients and servers is %windir%\System32\W32Time.dll. |
| Enabled | All versions | Indicates if the NtpClient provider is enabled in the current Time Service.
|
| EventLogFlags | All versions | Specifies the events logged by the Windows Time service.
|
| InputProvider | All versions | Indicates whether to enable the NtpClient as an InputProvider, which obtains time data from the NtpServer. The NtpServer is a time server that responds to client fourth dimension 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. To comply with Security and Exchange Commission (SEC) specifications, this should exist set up to 3 seconds. Events volition exist logged for this setting merely when EventLogFlags is explicitly configured for 0x2 big sample skew. The default value on domain members is 3. The default value on stand-lonely 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 null means that the look interval is always the minimum. The default value on domain members is 7. The default value on stand up-alone clients and servers is 7. |
| ResolvePeerBackoffMinutes | All versions | Specifies the initial interval to expect, in minutes, earlier attempting to locate a peer to synchronize with. The default value on domain members is 15. The default value on stand-alone clients and servers is 15. |
| SpecialPollInterval | All versions | Specifies the special poll interval, in seconds, for transmission 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,600. The default value on stand-lone clients and servers is 604,800. New for build 1703, SpecialPollInterval is contained by the MinPollInterval and MaxPollInterval Config registry values. |
| SpecialPollTimeRemaining | All versions | Maintained past W32Time. It contains reserved information that is used by the Windows operating system. It specifies the time, in seconds, before W32Time volition 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 up-alone clients and servers is left blank. |
NtpServer entries
The NtpClient subkey entries are located at HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer.
| Registry Entry | Versions | Clarification |
|---|---|---|
| AllowNonstandardModeCombinations | All versions | Indicates that non-standard fashion combinations are allowed in synchronization between clients and servers. The default value for domain members is 1. The default value for stand up-alone clients and servers is 1. |
| DllName | All versions | Specifies the location of the DLL for the time provider. The default location for this DLL on both domain members and stand-alone clients and servers is %windir%\System32\W32Time.dll. |
| Enabled | All versions | Indicates if the NtpServer provider is enabled in the electric current Time Service.
|
| InputProvider | All versions | Indicates whether to enable the NtpClient as an InputProvider, which obtains fourth dimension information from the NtpServer. The NtpServer is a fourth dimension server that responds to client fourth dimension requests on the network by returning time samples that are useful for synchronizing the local clock.
|
Enhanced logging
The post-obit registry entries are not a part of the W32Time default configuration but can be added to the registry to obtain enhanced logging capabilities. The information logged to the Organization Result log tin be modified by changing values for the EventLogFlags setting in the Grouping Policy Object Editor. By default, the Windows Fourth dimension service logs an event every time that it switches to a new fourth dimension source.
In social club to enable W32Time logging, add the following registry entries:
| Entry | Versions | Clarification |
|---|---|---|
| FileLogEntries | All versions | Controls the number of entries created in the Windows Time log file. The default value is none, which does not log whatsoever Windows Time activeness. Valid values are 0 to 300. This value does not touch the effect log entries ordinarily created past Windows Time |
| FileLogName | All versions | Controls the location and file name of the Windows Time log. The default value is blank, and should not exist changed unless FileLogEntries is inverse. A valid value is a full path and file proper noun that Windows Time will use to create the log file. This value does non bear upon the event log entries normally created by Windows Time. |
| FileLogSize | All versions | Controls the circular logging behavior of Windows Time log files. When FileLogEntries and FileLogName are defined, defines the size, in bytes, to let the log file to reach before overwriting the oldest log entries with new entries. Please use one thousand thousand or larger value for this setting. This value does not touch on the upshot log entries normally created by Windows Time. |
Group Policy Object settings
Grouping Policy settings are contained in the Global Configuration Settings and the Windows NTP Client Settings GPOs.
Global Configuration Settings
These are the global Group Policy settings and default values for the Windows Fourth dimension service. These settings are contained in the Global Configuration Settings GPO in Local Policy Editor.
| Group Policy setting | Default value |
|---|---|
| AnnounceFlags | 10 |
| EventLogFlags | 2 |
| FrequencyCorrectRate | four |
| HoldPeriod | v |
| LargePhaseOffset | ane,280,000 |
| LocalClockDispersion | x |
| MaxAllowedPhaseOffset | 300 |
| MaxNegPhaseCorrection | 54,000 (xv hours) |
| MaxPollInterval | xv |
| MaxPosPhaseCorrection | 54,000 (15 hours) |
| MinPollInterval | 10 |
| PhaseCorrectRate | seven |
| PollAdjustFactor | 5 |
| SpikeWatchPeriod | 90 |
| UpdateInterval | 100 |
Windows NTP Client settings
These are the Windows NTP client settings and default values for the Windows Fourth dimension service. These settings are contained in the Configure Windows NTP Customer GPO in Local Group Policy Editor.
| Group Policy setting | Default value |
|---|---|
| NtpServer | time.windows.com, 0x1 |
| Type | NTP - Use for non-domain-joined computers NT5DS - Utilise for domain-joined computers |
| CrossSiteSyncFlags | 2 |
| ResolvePeerBackoffMinutes | fifteen |
| ResolvePeerBackoffMaxTimes | 7 |
| SpecialPollInterval | 3,600 |
| EventLogFlags | 0 |
See RFC 1305 - Network Time Protocol of the Cyberspace Engineering Job Force (IETF).
Feedback
Submit and view feedback for
Source: https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/windows-time-service-tools-and-settings
Posted by: ferrellgially.blogspot.com
0 Response to "How To Check Time Sync On Windows 2012"
Post a Comment