On Mar 12, 11:33 am, Unruh <[EMAIL PROTECTED]> wrote: > It may not belong on time.microsoft.com but does on microsoft by making it > hard to use any other server.
Using another NTP server isn't hard on Windows, in fact it is dead simple and easier than configuring the reference ntpd implementation, especially in a Windows Acrive Directory domain. There is, in fact, zero configuration required for most environments. If you want to change things, you can change the time servers on 100s clients with a few clicks in Group Policy Editor. There is no scripting needed. If you don't have AD in your network, or just like scripting, you can, of course script things as much as you want. You could: - Call w32tm /configure from a startup batch file - Use VBscript in Windows Scripting Host at startup or login or even remotely from a central "controller" machine - use regedit files in a script - use kixtart, perl, or any other scripting language available that can modify the registry _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
