Windows Server Time is Out of Sync: 2 Best Ways to Force Sync

If Windows Server time is out of sync adjusting your policies will help

Reading time icon 3 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

Key notes

  • Time sync issues on your Windows Server can cause a lot of problems, so it's important to fix them.
  • Adjusting the policy settings can fix this problem, so we encourage you to do that.

If your Windows Server time is out of sync, you came to the right place. Not having the correct time on your Windows server can be extremely annoying, especially if you are using apps that require time to be synced.

We already showed you how to fix time on Windows 10, and today we will show you how to deal with this issue on Windows Server.

Why is my Windows time always out of sync?

There are several reasons for this issue on Windows Server:

  • Group Policy settings – In most cases, incorrect group policy settings can cause this problem. Change them accordingly, and the issue will be gone.
  • Improperly configured settings – Sometimes Windows Time isn’t configured properly. Use Command Prompt to configure it and fix the problem.

What can I do if Windows Server time is out of sync?

Before we start fixing this issue, there are a few checks that you can perform:

  • Enable UDP port 123 – Windows uses this port for time synchronization, so ensure your hardware or software firewall isn’t blocking it.
  • Make sure that your host time is properly configured – If you’re running a server inside of a virtual machine, check if the time on the host device is correct.

1. Use Command Prompt

  1. Open Search and enter cmd. Right-click Command Prompt and choose Run as administrator.
  2. Run the following command: w32tm /query /source
  3. In case it shows a different server, correct the time on that server and run the following command: w32tm /resync /rediscover 
  4. If the command from step 2 says comes back as free or running local CMOS, run the following commands:
    net stop w32time
    w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org" /reliable:yes /update
    net start w32time
    w32tm /config /update
    w32tm /resync /rediscover

2. Modify the Group Policy

  1. Press Windows key + R and enter gpedit.msc. Press Enter.
  2. Now navigate to Computer Configuration and choose Administrative Templates. Next, expand System and go to Windows Time Service. Lastly, choose Time Providers.
  3. Double-click on Configure Windows NTP Client.
  4. Enable the policy and set the following settings:
    NtpServer: tick.usno.navy.mil  (or your preferred server of choice)
    Type: NTP
    SpecialPollInterval: 3600
  5. After doing that, open Enable Windows NTP Client and Server services, end set each to Enabled.
  6. Keep in mind that these settings should be only on your master clock. To ensure that run the following commands:
    root\CIMv2
    Select * from Win32_ComputerSystem where DomainRole = 5

The rest of your computers should be configured as follows:

  1. Open Group Policy Editor.
  2. Go to Computer Configuration and expand Administrative Templates. After that, choose System. Lastly, go to Windows Time Service.

  3. Double-click on Global Configuration Settings.
  4. Set it to Enabled and save changes.
  5. Next, go to Time Providers in the left pane.
     
  6. Select Configure Windows NTP Client.
  7. Enable the policy and configure it as follows:
    Type: NT5DS
    CrossSiteSyncFlags: 1
    SpecialPollInterval: 3600
  8. Save changes.

Because we understand how important it is for you to have a correct time set on your machine, for both personal and software-related reasons, following the above steps will surely help.

Many reported that the Windows Time service is missing, but we fixed that issue in one of our other guides.

You can do this by using the comment section found below this article.

More about the topics: windows 10, windows server

User forum

0 messages