This article shows how to configure Windows Time Service on Windows Server 2016 so that it acts as an NTP server for domain client computers.

Configure Windows Time Service

1. Type the following commands on PowerShell:

w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:MANUAL
Stop-Service w32time
Start-Service w32time

Now the Windows Server 2016 is an NTP client of pool.ntp.org and its time/clock is synced with the NTP pool servers (The server is at the same time the NTP server for other domain client systems).

If your Windows Server 2016 machine is a VM inside Hyper-V, you have to disable time sync. Go to VM settings-> Management-> Integration Services and uncheck Time Synchronization. Otherwise, Windows Server 2016 time/clock will be synced with the Host time/clock.

2. Go to the client machines and run the following command on PowerShell to force them to sync their time/clock with the domain controller on the Windows Server 2016.

w32tm /resync

You can check the time synchronization status using the following command.

w32tm /query /status

Check Windows time sync status

 

How to Configure NTP Server in Windows Server 2016

5 thoughts on “How to Configure NTP Server in Windows Server 2016

  • Permalink

    “If your Windows Server 2016 machine is a VM inside Hyper-V, you have to disable time sync. Go to VM settings-> Management-> Integration Services and uncheck Time Synchronization. Otherwise, Windows Server 2016 time/clock will be synced with the Host time/clock.”

    I am unable to locate the VM settings, management,….. On my Hyper-V console.

    Where is this exactly?

    Reply
  • Permalink

    I have spent weeks looking for such a clear, simple explanation of how to set up the Time Service on our Windows Server 2016 Standard Domain Controller. And of course in turn, our Windows 7 and 10 workstations to synchronise their time with our Server.
    As my Danish wife would say, “Tusend Tak guys” which means “A thousand thanks guys”.
    I sure hope I find more articles like this from you.

    Reply
  • Permalink

    Straight to the point, clear and concise. Thank you 😉

    Reply
  • Permalink

    Thanks so much for pointing me in the right direction. Now have our Cisco 7970 phones (SIP) set to reference our internal windows 2016 NTP server and all working well. 🙂

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

*