Common syntax
w32tm /query /source
w32tm /query /status
w32tm /query /configuration
w32tm /query /peers
/source
w32tm /query /source
Displays the source currently selected by Windows Time Service.
Typical results include:
- A domain controller name.
- An external NTP hostname.
Local CMOS Clock.Free-running System Clock.VM IC Time Synchronization Provider.
This is usually the quickest way to decide whether the computer is following the intended design.
/status
w32tm /query /status
Displays the current synchronisation state. Important fields include:
- Leap Indicator – whether the source reports a leap warning or unsynchronised state.
- Stratum – the distance from the original reference source.
- Last Successful Sync Time – when Windows last accepted a time sample.
- Source – the source used for that state.
- Poll Interval – the current polling interval.
A recent successful sync with an unexpected source is still a configuration problem. An expected source with an old sync time may be a connectivity or server-health problem.
/configuration
w32tm /query /configuration
Displays the effective Windows Time configuration, including values supplied locally and by Group Policy.
Review:
Type– commonlyNT5DSfor domain hierarchy orNTPfor manual peers.NtpServer– the configured manual peer list.AnnounceFlags.- Phase-correction limits.
- Client and server provider settings.
Where a value is supplied by policy, changing it locally may have only a temporary effect.
/peers
w32tm /query /peers
Displays the configured peers and their current state.
This command is useful on systems using manual NTP peers. It does not replace /source, because a configured peer is not necessarily the source Windows selected.
Verbose status
w32tm /query /status /verbose
Adds lower-level details useful when comparing providers and timing data. For routine troubleshooting, the normal status output is usually easier to read.
Query another computer
w32tm /query /computer:SERVER01 /source
w32tm /query /computer:SERVER01 /status
w32tm /query /computer:SERVER01 /configuration
Remote queries require suitable permissions, firewall access and Remote Registry/RPC conditions depending on the operating system and command used.
Typical verification sequence
w32tm /query /source
w32tm /query /status
w32tm /query /configuration
Record the output before applying changes. Repeat the same commands afterwards and compare the source, last successful sync and effective type.
What the command does not prove
/configurationdoes not prove a peer is reachable./peersdoes not prove a peer was selected./sourcedoes not by itself prove the last sync was recent./statusdoes not prove the source is organisationally correct.