在域环境下运行在Hyper-V下的Windows客户机上，我注意到Windows时间服务存在问题。 我定期收到系统日志中的以下三条消息。
Event Type: Information Event Source: W32Time Event Category: None Event ID: 38 Date: 6/11/2009 Time: 12:26:15 PM User: N/A Description: The time provider NtpClient cannot reach or is currently receiving invalid time data from xxx.xxx.xxx (ntp.d|abxy:123->abxz:123). Event Type: Warning Event Source: W32Time Event Category: None Event ID: 24 Date: 6/11/2009 Time: 12:42:47 PM User: N/A Description: Time Provider NtpClient: No valid response has been received from domain controller xxx.xx.xxxx after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. Event Type: Error Event Source: W32Time Event Category: None Event ID: 29 Date: 6/11/2009 Time: 12:42:47 PM User: N/A Description: The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time. 重新启动Windows时间服务后，它将成功与域控制器同步（事件ID 37），但是我注意到服务器也有另一个同步尝试：
Event Type: Information Event Source: W32Time Event Category: None Event ID: 35 Date: 6/11/2009 Time: 1:04:30 PM User: N/A Description: The time service is now synchronizing the system time with the time source VM IC Time Synchronization Provider.
最终的结果是，W32Time不能与域控制器作为成员服务器正确同步。 所有其他服务器和工作站正在与域控制器正确同步。
解决方法是为每个guest虚拟机在Hyper-V Integration Services中禁用时间同步 。 然后重新启动客人的Windows时间服务。 客人将然后正确与域控制器同步。
这个过程对于虚拟化域控制器是至关重要的，因为它们为所有客户提供时间。 请记住，具有PDC模拟器angular色的域控制器应configuration外部NTP时间源（使用w32tm命令行configuration）。
此答案中提供了有关为Windows时间configuration外部NTP时间源的信息。