On Thu, Sep 22, 2011 at 11:05 AM, Tom Miller <[email protected]> wrote:
> I am reconfiguring my time providers for my AD servers. What are you using
> for your public time sources?
I've got my PDC Emulator configured to get its time from our
in-house Linux server running the reference implementation of NTP.
That Linux box is configured to sync to multiple pool.ntp.org servers:
server us.pool.ntp.org
server us.pool.ntp.org
server us.pool.ntp.org
server time.windows.com
I list the same name three times because I'm running an older NTP
release which doesn't support the "pool" directive (which does the
same thing and better).
I threw time.windows.com in there as a further diversity measure.
By using multiple diverse time sources, NTP can better detect and
compensate for network latency and drift. Accuracies within a few
seconds of "atomic" time are achievable this way.
Microsoft's documentation on the Windows time service isn't clear on
if/how it handles multiple upstream NTP servers, and given MSKB 939322
I figured I wasn't likely to get an answer, and I already had NTP
configured on *nix, so that's the route I chose.
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin
