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 /manualpeerlist:pool.ntp.org /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….

Type:

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.

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

  • May 6, 2019 at 10:03 pm
    Permalink

    It is not working for them because they did not do a resync that’s why

    Reply
  • December 18, 2018 at 6:40 am
    Permalink

    The commands provided only configure one machine to point to the (external) NTP source.. you have not provided the relevant commands to make the clients point to it, so I can only assume that the first machine you used is a DC, and you already set the command “w32tm /config /reliable:yes” on it, which makes any DC a reliable NTP source. All clients that are members of the domain would then automatically use it as an ntp time source (due to default domain policies).

    Note – as per w32tm /? the command “w32tm /config /reliable:yes” is ONLY applicable to DC’s. There are alternative settings that need to be enabled (including registry hacking) to enable a non-DC system as an NTP source.

    Reply
    • December 18, 2018 at 8:17 am
      Permalink

      Hey Wes, thanks for leaving a comment. Yes, indeed the Server is a DC. Thank you for pointing that out.

      Reply
  • October 19, 2018 at 5:27 am
    Permalink

    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.

    C:\Users\Administrator>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: 10/19/2018 12:43:34 PM
    Source: Local CMOS Clock
    Poll Interval: 6 (64s)

    Reply
  • November 14, 2017 at 8:57 pm
    Permalink

    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.

    Reply
    • February 6, 2018 at 4:54 pm
      Permalink

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

      Reply
      • February 6, 2018 at 6:35 pm
        Permalink

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

        Reply

Tell us what you think!

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

%d bloggers like this: