Configure manual peers

w32tm /config /manualpeerlist:"0.uk.pool.ntp.org,0x8 1.uk.pool.ntp.org,0x8 2.uk.pool.ntp.org,0x8" /syncfromflags:manual /update

This configures the listed peers and tells Windows to use the manual peer list.

Use quotation marks around multiple peers. Separate peers with spaces.

Configure the forest root PDC Emulator

w32tm /config /manualpeerlist:"0.uk.pool.ntp.org,0x8 1.uk.pool.ntp.org,0x8 2.uk.pool.ntp.org,0x8" /syncfromflags:manual /reliable:yes /update

Under the normal Active Directory design, this belongs only on the PDC Emulator in the forest root domain.

Other domain controllers should normally use the domain hierarchy rather than the same external peer list.

Return a domain member or DC to the hierarchy

w32tm /config /syncfromflags:domhier /reliable:no /update

Then request source rediscovery:

w32tm /resync /rediscover

This is commonly used after a former forest root PDC Emulator loses the FSMO role or when a domain member has retained an old manual peer list.

/manualpeerlist

Specifies one or more manual peers.

/manualpeerlist:"peer1,0x8 peer2,0x8"

Use approved organisational sources. Do not copy old public NTP lists without checking that the servers still exist and permit the intended use.

/syncfromflags

Controls where Windows Time Service obtains time.

  • manual – use the manual peer list.
  • domhier – use the Active Directory domain hierarchy.
  • all – use all available synchronisation mechanisms.
  • no – do not synchronise from a source.

For normal domain members, domhier is usually the correct choice. For a standalone server or forest root PDC Emulator using explicit peers, use manual.

/reliable

/reliable:yes
/reliable:no

Marks the computer as a reliable time source for domain clients. This setting is meaningful on domain controllers.

Do not mark every domain controller reliable merely because it is a DC. The forest root PDC Emulator is the normal authoritative root.

/update

Notifies Windows Time Service that its configuration has changed.

It avoids requiring a service restart for many changes, although a restart may still be used during a controlled maintenance procedure.

Peer flags

A peer can include a hexadecimal flag after a comma.

  • 0x1 – use the special polling interval.
  • 0x2 – use this peer only as a fallback.
  • 0x4 – use symmetric active mode.
  • 0x8 – use client mode.

Flags can be combined. For example, 0x9 combines 0x1 and 0x8.

For public NTP services, 0x8 is commonly used to ensure client mode. Do not add flags without understanding why they are required.

Apply the change to another computer

w32tm /config /computer:SERVER01 /syncfromflags:domhier /update

Remote configuration requires administrative access and appropriate firewall/RPC conditions. For widespread settings, Group Policy is usually more suitable than issuing remote commands individually.

Group Policy overrides

If w32tm /query /configuration shows policy-supplied values, local changes may be replaced during the next policy refresh.

Correct the Group Policy Object and its scope rather than repeatedly reapplying a local command.

Verify every change

w32tm /resync /rediscover
w32tm /query /source
w32tm /query /status
w32tm /query /configuration

Confirm the selected source, a recent successful sync and the intended effective type.

Microsoft documentation

Related information