Server 2012 R2, Hyper-V
I am trying to finalize setting up my first primary domain controller. One of the warnings that always comes up after first promoting the DC is Event ID 12 along with other time source related events.
Net Stop W32Time W32tm /config /syncfromflags:manual /manualpeerlist:"time-nw.nist.gov" W32tm /config /reliable:yes Net Start W32Time W32tm /config /update
I did this because it seemed pretty straightforward and now my DC seems 'happy' WRT to it's time service, at least it's not throwing any more warnings when it starts up.
But it's not very satisfying. I assigned my external reference as time-nw.nist.gov, but when I run this command at the prompt:
w32tm /stripchart /computer:"time-nw.nist.gov" /samples:5 /dataonly
I see my time is off by +15.xxx seconds.
I also ran "w32tm /resync" but there's still a discrepency.
That suggests to me the external reference isn't working. But I don't understand how to ask the DC what it's using as an external reference. I only understand how to assign it.
There's also the issue of the DC being hosted on Hyper-V. At link4 above Microsoft says this in a note:
"This guidance has been recently updated to reflect the current recommendation to synchronize time for the guest domain controller from only the domain hierarchy, rather than the previous recommendation to partially disable time synchronization between the host system and guest domain controller."
So was link2's guidance correct? But even so, how do I know it was actually set correctly, and why is there still a lag? Is there any new guidance on doing this when the DC is a vm hosted on Hyper-V?