Windows includes the Windows Time Service on workstation editions in the same way as Windows Server. The difference is usually in how the computer is used. A workstation rarely provides services to other devices, so the emphasis is on maintaining an accurate clock for authentication, certificates, cloud services and file timestamps.

In many cases, the default Windows configuration is sufficient. If the computer has regular Internet access, Windows can synchronise automatically without any manual changes.

When should a workstation be configured manually?

Manual configuration is appropriate where a workstation must use a specific time source, such as a company firewall, an internal Chrony server or a dedicated NTP appliance. It may also be appropriate for laboratory systems, isolated networks or computers that rarely have Internet access.

If several standalone workstations exist in the same environment, pointing them all at the same approved source makes troubleshooting much easier than allowing every machine to use a different service.

Configuring an NTP source

To configure a manual peer list, open an elevated Command Prompt and run:

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

Unlike an Active Directory PDC Emulator, there is no need to configure the workstation as a reliable time source.

Restart the Windows Time Service if required and request a synchronisation:

net stop w32time
net start w32time
w32tm /resync

Checking the result

After making any change, verify that Windows has selected the intended source.

w32tm /query /source
w32tm /query /status

If the configured peer cannot be contacted, Windows may continue using its previous source or fall back to the local clock. Checking the configuration alone does not prove that synchronisation is working.

Laptops

Laptops deserve special consideration because they often spend long periods disconnected from the network. Sleep, hibernation and travel can all introduce clock drift before the computer next contacts its time source.

Normally this is corrected automatically once network connectivity is restored. If a laptop has been unused for a long period, it may take a short time before Windows completes a successful synchronisation.

A significant time error can prevent sign-in to cloud services, VPN connections or websites that depend on valid certificates. When investigating authentication problems on a standalone laptop, verifying the system clock should always be one of the first checks.

Workstations in a small business

Many small businesses have several Windows PCs but no Active Directory domain. In these environments it is often sensible to configure every workstation to use the same local time source, such as the office firewall or a Linux server running Chrony.

This approach keeps all systems aligned without requiring each computer to communicate directly with different Internet time servers.

Common mistakes

  • Changing the configuration without checking whether there is actually a problem.
  • Using a single unreliable public NTP server.
  • Ignoring DNS or firewall issues when testing a new source.
  • Assuming that a successful w32tm /config command proves synchronisation.
  • Manually adjusting the system clock instead of correcting the underlying source.

Related information