I rebooted my Windows Server 2019 Active Directory Domain Controller (AD DC) and after the restart, the clock unexpectedly rolled back to the year 1839 and then jumped forward to 2038. The time settings were unchanged, and I can't figure out what caused this issue. Has anyone experienced something like this before?
4 Answers
Also, during startup, your VM's system clock could be incorrect and might be setting the time on the guest OS. Once it connects to the network, NTP takes over, which could lead to these weird jumps.
You might want to check if you're running this on a VM or a physical machine. If it’s a VM, make sure your Domain Controller holds the PDCe role, and look at how you've set up time sync. Don’t forget to check what hypervisor you’re using too!
This could be due to an NTP issue or potentially a dead CMOS battery, based on how your time source is set up. Just so you know, the date January 19, 2038, is significant because it tends to show up when there's a problem with time values in 32-bit systems. Not sure what the 1839 date is about, though.
You can use the command `w32tm.exe /query /source` to check your time source. Make sure your AD PDC emulator is configured to look for an NTP server, and all other domain controllers should sync with that PDC. If you see 'CMOS clock' as a source, that could cause some serious issues.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures