Windows time sync

[Leehilton90]

We have an issue across site at the moment with time not syncing up and even some workstation with time going up x5 faster than normal. But one of our servers is 5 minutes out. I have done w32tm /query /peers and it points to a server that has the correct time. Even after restarting the incorrect server it has not synced to the correct time.

 

We also have 2 servers that point to ntp2d.mcc.ac.uk, 1 server is correct and 1 isn't. We unfortunately can't restart these right now.

 

Does anyone have any ideas?

[Olliedawg]

Are you using ESXi? VM's should get the time from the ESXi host if this is the case (I believe you need VM tools installed).

 

This is how mine is set up -

 

I use both 0.uk.pool.ntp.org & 1.uk.pool.ntp.org as listed NTP servers on our ESXi hosts

 

I have a login script set to run for ALL workstations to our main domain controller net time \\SERVERNAME /set /yes

 

Seems to work great, not had any time sync issues at all.

 

Worth checking some group policies for NTP on the affected machines?

[snagrat]

Machines will get it from the DCs. Make sure these are correct.

 

If virtualised then DCs should not get time from host. In HyperV you can turn if time synchronisation for that machine.

[TwistedHelixis]

Same as above, on our Hyper-V DC we have the time box unticked in that VMs settings. The DC is set to get its time from an external time service. All other clients and servers look at the DC for their time.

[jthompson]

Worth bearing in mind too that if there is a signiifcant difference to correct (like, several minutes), that won't necessarily happen in one instant. Windows will reduce the delta by progressively smaller amounts so as to glide a clock back into alignment.

[timbo343]

We have an issue across site at the moment with time not syncing up and even some workstation with time going up x5 faster than normal. But one of our servers is 5 minutes out. I have done w32tm /query /peers and it points to a server that has the correct time. Even after restarting the incorrect server it has not synced to the correct time.

 

We also have 2 servers that point to ntp2d.mcc.ac.uk, 1 server is correct and 1 isn't. We unfortunately can't restart these right now.

 

Does anyone have any ideas?

Use an application call nettime. It will give you a GUI for configuring time servers and tell you if the sync was successful

[ITGURU]

All DCs set to time sync from time.windows.com and set as authoritive.

 

These are then used as NTP sources

[Davit2005]

In a on-prem domain environment PCs/servers joined to the domain look at the DC holding the PDC emulator role by default.

 

https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/fsmo-roles

 

The PDC should be configured to talk to reliable time sources if in the UK i.e. 0.uk.pool.ntp.org, 1.uk.pool.ntp.org, etc.

 

Personally I'd configure the HyperVisor to use a reliable source if you are running a virtualized environment in the first place to stop any issues probably a proper ntp server if it is ESXi, I'd assume if HyperV and domain joined it would look at the PDC emulator to by default.

 

With ESXi I have in the past used a reliable NTP source either a NTP server on the network or an external NTP server.

Edited March 7, 2024 by Davit2005

[chazzy2501]

I set my virtualized DC to use the swgfl time servers and everything is a ok.

[Julian]

Similar to others, VMWare hosts sync to NPT source, Servers get time from the hosts. I also have one sever set up as a NTP server, so that all my network switches have the right time, and date. Logs are much easier to understand when the data and time is correct.