Windows time server not in sync with other devices

Question

Our management team is frustrated with the server time and all other time devices in the office because they are not all synchronized. Windows Time server seems to be 5-7 minutes ahead than cell providers for example. Is there a way to sync with these providers? Appreciate any advice.

Answer 1

By default a virtual machine gets time from hypervisor via integration services. Sounds like you'll want to turn off (uncheck) Time synchronization in integration services. If the host were Hyper-V you can do that here.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Some general info

• All domain members should use NT5DS domain time.
• Desktops and member servers sync with any domain controller.
• Domain controllers sync with PDC emulator (one per domain)
• PDC emulator in child domain can sync with any domain controller in parent domain.
• PDC emulator in parent domain syncs with either a hardware clock or possibly an external source.
  https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/

On the PDCe

some to choose from
https://tf.nist.gov/tf-cgi/servers.cgi

w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /manualpeerlist:<ntp ip address> /syncfromflags:manual /reliable:yes /update
net stop w32time
net start w32time
then check
w32tm /query /source
w32tm /query /configuration

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 3

In our environment (which has been reliable thus far), I configure all Domain Controllers to synchronize their time with an external source.

I use the w32tm command, you have to run it twice, one to set the config, and one to commit the change.

At a command prompt:

1. First, modify the config; You are telling the windows time service here to sync from a manual peer list, and that the server specified is reliable. In my case I use pool.ntp.org - this is a pool of free NTP servers on the internet.

w32tm /config /syncfromflags:MANUAL /manualpeerlist:pool.ntp.org /reliable:YES

Then run a second command to notify the windows time service that the config has changed and to commit it.

w32tm /config /update

Once this is done on all domain controllers, their time will be "synchronized" to the same time source (and an accurate one at that). By default, all member servers and computers look to the closest domain controller for their time updates. This should keep ALL your PCs up to date. You can also point other devices (routers, switches, WAPs, etc) to your domain controllers as an NTP source.

Hope this information can help you

Best wishes

Vicky

Answer 4

Hi, I ran a /query /source command and it shows VM IC Time Synchronization Provider. I have a Domain controller on a VM and a second DC as a stand alone. I don't understand the significance of this provider. Should this be removed? Thanks

Answer 5

Hi,

Welcome to share your current situation if there are any updates.

Please feel free to let us know if you need further assistance.

Best Regards,
Vicky