OK, how obscure is this....
I have Server1 which is the Domain Controller.
I have a HOST system which is NOT joined to the Domain, but it hosts 2
virtualized servers (2003 and 2008).
The virtualized servers *are* joined to the domian.
So here we go..
When the virtualized servers boot, they sync their clocks to the
About two seconds later, they sync to the HOST system!
And, as fate would have it, about half of the computers on our network
are sync'ing their clocks to the virtualized 2003 server rather than
the Domain Controller (virtualized 2003 is only a "member" server, not
So it turns out that the HOST system was never configured to sync to
anything! So over the coarse of time, the HOST has drifted to be 10
minutes faster than the domain controller. And once that happened, the
time rippled up to the virtualized servers, which then went off-line
for the rest of the netowrk based on time variance!
I have configured the the HOST system to sync to an atomic time
source, and re-synced it - and the virtualized servers - time has
resumed it is shape. :)
Now the other hard question...
Why are half of my client systems sync'ing to the virtualized server
2003 rather than the Domain Controller???
More to point, how do I correct it?
I tried w32tm /resync /rediscover - and they go right back to the