You receive Windows Time Service event IDs 24, 29, and 38 on a virtualized domain controller that is running on a Windows Server 2008-based host server with Hyper-V

If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.

Symptoms

When a virtualized domain controller is running in a guest operating system on a host server that is running Windows Server 2008 with Hyper-V, and the Windows Time Service (W32Time) synchronizes with a primary domain controller, the following events may be logged in the System log on the virtualized domain controller: 


If you enable Windows Time Services Debug logging on the domain controller, information that resembles the following is logged in the Debug log:

149040 14:15:14.2970940s - Logging information: The time service is now synchronizing the system time with the time source VM IC Time Synchronization provider.

Cause

On a host server that is running Windows 2008 with Hyper-V, virtualized domain controllers that are running on a guest operating system are allowed to synchronize their system clocks with the clock of the host operating system. The events that are listed in the "Symptoms" section are recorded in the System log because domain controllers have their own time synchronization mechanism. If domain controllers synchronize time from their own source and synchronize time from the host, the domain controller time can change frequently. Because many domain controller tasks are tied to the system time, a jump in the system time can cause lingering objects to be left in caches, and may cause replication to stop. 

Resolution

To resolve this issue, disable time synchronization on the host by using Integration Services, and then configure the virtualized domain controller to accept the default Windows Time Service (W32time) domain hierarchy time synchronization.

To do this, follow these steps:
  1. Open Hyper-V Manager.
  2. Click Settings.
  3. Click Integration services.
  4. Clear the Time Synchronization option.
  5. Exit Hyper-V Manager.
  6. Restart the server.

References

For more information about virtualized domain controllers, see Microsoft TechNet article Deployment Considerations for Virtualized Domain Controllers.
Özellikler

Makale No: 976924 - Son İnceleme: 13 Ağu 2012 - Düzeltme: 1

Geri bildirim