Time running ahead by 2 hours in Windows Server 2019(ADDC)

Question

Hi Team,

Our ADDC server machine's timezone is set to UTC+2. But the time is still showing 2 hours ahead of the actual "UTC+2" time. Saw the same issue reported by multiple users. Manually setting the correct time is not working as the time is reset to the above-mentioned wrong time once the machine is restarted. Also can we set to update the server time(once corrected) on all connected endpoints in the domain? Please advise. Thanks.

Regards,
Anand R Menon

Answer 1

Is this the PDC emulator or another domain controller?

On the PDC emulator you could

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
https://tf.nist.gov/tf-cgi/servers.cgi

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

Answer 2

Glad to hear, all members should be using NT5DS domain time.

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/

w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time
then check
w32tm /query /source
w32tm /query /configuration