[url=http://meincmagazine.com/civis/viewtopic.php?p=24927617#p24927617:2vafsi16 said:Big Wooly Mammoth[/url]":2vafsi16][url=http://meincmagazine.com/civis/viewtopic.php?p=24927173#p24927173:2vafsi16 said:M. Jones[/url]":2vafsi16][url=http://meincmagazine.com/civis/viewtopic.php?p=24927157#p24927157:2vafsi16 said:PaveHawk-[/url]":2vafsi16]
Previous guys who did this VMware deployment set all VMs (inc the DC) to sync time to the host.
Yes, that is a GREAT idea.
In fairness, it was VMware's recommendation to sync time to host through VMware tools until a couple of years ago. I only noticed they entirely reversed their recommendation when it was pointed out to me. It explained a lot because the old way was terrible, and caused much pain.
This is also the default with HyperV R2; I am working on clearing up this mess in our environment as well.
For non-DCs, why does it matter? The time should be the same on the host or the guest (assuming the host is also joined to the same domain the guests are on), no?
I agree that if you have virtualized DCs, they shouldn't sync to anything but NTP... but I hate virtualized DCs too.