Ever since the last round of windows updates about a week ago, we have 4 servers with similar issues.
Each time the servers are rebooted, the clocks revert to 10/16/2008
- exchange server, server 2008 r2, domain1 - physical
- domain controller, server 2008 r1, domain1, dns server - vmware
- utility server, server 2008 r2, domain1 - physical
- domain controller for an unrelated domain, server 2008 r2, dns server - vmware
the domain controller reverting, did not cause all of the other servers to lose their time - and the 4th server is in an entirely different domain. this did cause all of the active directory connections to get out of whack as the tombstone times were jacked up. prevented people from authenticating to exchange, since exchange thought it was 7 years ago
was there a recent windows update that messed up timezones or something? where should i start looking?
note: when i say rebooted, i mean rebooted - not turned off, not removed from electricity - i've ruled out the case of a dead cmos battery, especially as it's happening to four individual servers