The Windows Time Service and Hyper-V

Recently a domain I had a domain running inside Hyper-V on Windows Server 2008.  The challenge was that the domain's clocks were running behind the time being reported at  When I ran the w32tm command (

w32tm /config / /syncfromflags:manual /reliable:yes /update

found here

) to sync to the time peer list which included on the Domain Controller (guest), time would sync for about 4 minutes and then fall behind again. 

This is due to a potential conflict between the host and the guest via Integration Components.  What I did to resolve it is to set the Windows Server 2008 Hyper-V hosts to sync against the peer.  Domain time then was corrected on all guest machines.