How to Configure NTP Server on Windows Server 2016

In this article, I will show you how to configure NTP Server on Windows Server 2016 in just a few steps.

We will use PowerShell to change the NTP Server and we will validate if it worked afterward.

Configure the NTP Server on Windows Server 2016

On your Windows Server, 2016 hit the Windows Button and type: PowerShell and right-click it and select Run as Administrator

Type the following commands

w32tm /config / /syncfromflags:MANUAL
Stop-Service w32time
Start-Service w32time

Of course, you can take any NTP Server that you want.

Now verify if the time-server was set correctly on your Server 2016 by typing:

w32tm /query /status

You should get a reply like this:

Now we will go ahead and verify if our clients sync properly.


Verifying if the Time Server was correctly set on our Clients

On a client computer open a PowerShell with right-click and Run as Administrator….


w32tm /query /status

Check the time-server and type:

w32tm /resync 
w32tm /query /status

Then you are able to see that the time-server actually changed like in the example below.

And that’s it! Easy, right?

Always make sure that you use the same time-server in your network and that all your clients are syncing with it. If you have time differences inside of your Active Directory Domain you will run into major issues.

6 thoughts on “How to Configure NTP Server on Windows Server 2016

  • Pingback:How to Configure NTP Server on Windows Server 2016 -

  • Pingback:It’s the networks fault #18

    • December 25, 2017 at 4:26 pm

      Hey, thanks for your feedback! I also wish to remove them, but that only works if some donations are coming in to at least be able to pay the server cost. As soon as I get enough donations that I don’t lose money, the ads are gone.

  • November 14, 2017 at 8:57 pm

    Nope.. After doing those steps it still says the source is local cmos clock. I am an Enterprise admin:

    PS C:\Windows\system32> w32tm /query /status
    Leap Indicator: 0(no warning)
    Stratum: 1 (primary reference – syncd by radio clock)
    Precision: -6 (15.625ms per tick)
    Root Delay: 0.0000000s
    Root Dispersion: 10.0000000s
    ReferenceId: 0x4C4F434C (source name: “LOCL”)
    Last Successful Sync Time: 11/14/2017 2:53:29 PM
    Source: Local CMOS Clock
    Poll Interval: 6 (64s)

    Please advise.

    • February 6, 2018 at 4:54 pm

      i found the same output as well. the commands mentioned in this „tutorial“ doesn’t work at all, or it’s missing something crucial.

      • February 6, 2018 at 6:35 pm

        I just tried it again and it worked. Are you running an elevated cmd shell?


Tell us what you think!

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: