We recently upgraded a domain controller to Windows Server 2008. A couple of days after that the site administrators reported a problem with time synchronization on one of his servers. In fact it looked like the time was in sync, but we saw w32time errors and warnings in the system log.
Our first guess was of course that this is related to the DC upgrade so I started checking this machine. The server however was doing just fine, it was synchronizing with its time source and advertising as a time server.
Taking a closer look at the system it turned out that it was a virtual machine running on Hyper-V. We ended up disabling the Hyper-V integration for TimeSynchronization and the errors went away.
Wednesday, June 3, 2009
Subscribe to:
Posts (Atom)