2 ms·
Windows time sync only cares about being accurate to 5 !minutes, for Kerberos. HyperV and makes Windows not even able to be that accurate. Oddly enough, Linux g
by MichaelGG 12y ago
Windows time sync only cares about being accurate to 5 !minutes, for Kerberos. HyperV and makes Windows not even able to be that accurate. Oddly enough, Linux guests have no trouble with subsecond accuracy.
I'm told the w32time codebase is not something MS employees like to look at.
- 72deluxe 12y agoI don't think that w32time is something that users like to look at! I recall a situation where you run w32time on a server and it runs fine and doesn't report an error, but still silently ignore the option you set as it is using another time source from another machine that it has designated a master. I could be wrong, but I was disappointed that the utility didn't return any errors when it knew that it was going to ignore you.
- deleted 12y ago[deleted]