On Feb 22, 2:31 am, Martin Burnicki <[EMAIL PROTECTED]> wrote: > Though it's normally preferable to run ntpd rather than w32time, there is a > limitation if you run ntpd on a domain controller: > The domain members (workstations) will stop detecting the domain controller > automatically as their primary time source, so you'll have to configure the > domain controller explicitely as times source on every client. >
Configuraing all the clients takes about 30 seconds using Windows Group Policies on any of your domain controllers. There is an administrative template for the WIndows Time service, and you can configure time sources, poslling intervals, and many other parameters for w32time. See: http://technet2.microsoft.com/windowsserver/en/library/a0fcd250-e5f7-41b3-b0e8-240f8236e2101033.mspx?mfr=true Say what you will about w32time's accuracy... it *is* extremely managable in large windows networks. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
