Tony Hoyle wrote:
David J Taylor wrote:
Yes, I was also in a network management role at the time, and I don't
recall it being an issue in the UK. Our Windows NT servers at that
time were almost certainly running NTP, and IIRC the clients had a
NET TIME /SET command (or whatever) in the login script. Most
clients were
A properly configured server will handle NTP just fine.
... as ours did ...
It's not that uncommon for people to have their windows servers set to
completely the wrong timezone (often either Seattle time, since that's
the default, or GMT (for some reason)) which works fine right up until
the point they try to use something which modifies the time like NTP
(or anything that relies on the UTC time such as the software I work
with). At that point it all goes pear shaped, since Windows bases
all its UTC times on the current timezone and vice/versa (ie. you set
UTC, you change 'local time' in the BIOS).
Those kind of bug reports are a 'mare of course.. you have to (a)
prove your software is working correctly, and (b) tell them that
they've setup their machines wrong... really nicely...
Tony
Being interested in timekeeping, having the wrong time zone is not
something I would allow on my servers! But you're right, and I have seen
that elsewhere.
David
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
