From: "Rich Gauszka" 

If that is the requirement why not use an NTP server?

My NAS was getting out of whack so I just set it to get the time from one
of the free NTP servers

http://www.pool.ntp.org/zone/us

"Gary Britt"  wrote in
message news:45ea0753$1{at}w3.nls.net...
>I you not anal about having every computer on the network with the exact
>same time?  I've worked places where they were extremely anal about every
>computer must have the exact same time down to the second so some computers
>syncing time other than off the domain controller would have been a big no
>no?
>
> I never quite understood it, but they seemed to think it was critical to
> the IT department for some reason.
>
> Gary
>
> Geo. wrote:
>> "Mike N."  wrote in message
>> news:l1dgu2957ubn3reo468k8h62qbuf9e0tu8{at}4ax.com...
>>
>>> Daylight Saving Time. Some may characterize DST as a
"mini-Y2K". No,
>>> it's
>>> not, it's worse than Y2K. At least with Y2K, everyone had the runs for
>>> the
>>> year leading up to it and were prepared. DST has hit American IT over
>>> the
>>> head with a two-by-four. Here at Sunbelt, we have had buckets of work to
>>> do
>>> for the transition - updates to SalesLogix, Exchange, SQL 2005, Office,
>>> Java runtime engine, etc.
>>
>> WTF is wrong with these people, has the automatic time switch function
>> always worked perfectly for everyone or something, I mean bfd so a
>> computer is off by an hour until someone changes the clock. what like
>> we've never had that happen before?
>>
>> Twice every year I have to change half our computer's manually. That's
>> why I run an NST program on some of them. it corrects the clocks every
>> 5000 seconds and cost me a whopping $0.
>>
>> Geo.

--- BBBS/NT v4.01 Flag-5