As of May 31, 2023, we have updated our Code of Conduct.

New answers tagged

1 vote

Windows Server Time-Service jumps into the future and (partially) back

TL;DR: We have found the most likely root cause: W32time Secure Time Seeding which looks at the legacy "time" value in SSL handshake headers, which is random in newer SSL implementations, ...
simendsjo's user avatar
  • 239
0 votes

Both LOCAL SERVICE and SYSTEM users are changing server time on DC

Thanks Greg. After some digging I found the culprit to be the backup process. I found a old Veeam KB article that referenced VMWare and the snapshot process could affect the system time. After ...
RobC_CTL's user avatar
0 votes

How to change time source from "Local CMOS Clock" to "DC"

I had the same problems, but the suggestions above didn't help (w32tm /resync brought "The computer did not resync because no time data was available"). Until I found out that there was no ...
Christoph J's user avatar

Top 50 recent answers are included