The registry setting is to allow you to sync time to an internet source and
also offer the ability of the Windows Time Service to sync other machines
which aren't actively part of a domain relationship. If you want to do this
then the registry fix is the way. If you want to simply sync with a
non-domain time source then group policy is the best way on Windows Server
operating systems.



-----Original Message-----
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Moran
Sent: Sunday, 2 September 2007 9:05 PM
Subject: Re: FreeBSD time servers and Windows clients

> Hi all,
>    I have one FreeBSD NTP server which syncs all my server clocks.
Getting the NTP server running was a piece of cake following the
instructions in the online handbook.  Recently I was asked to sync a bunch
of windows machines (10 of them) to my NTP server.   Now I'm not a windows
person, so I asked one of the windows people to figure out his side since my
side was up and running.   He wrote this little .bat file to run on the
windows boxes to be sync'd.   Its pretty straight forward....just save it as
a .bat file (time.bat) and run it from your XP box.   Make sure to enter
your NTP IP address where the x's are below.     It seems to work fine for
us.   Your mileage may vary.  There may be better/easier ways of doing this,
but this is what works ok for us....   

This sounds like a bad idea to me.  I seem to remember there's a
registry setting where you can specify explicit NTP servers for Windows.

Any reason why he went this route?

Bill Moran
_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to