 |
 |
That's pretty funny--I totally forgot about that! Even after you fix it, Windows will then break it again on April 1! I had the same thought about the clock synchronization for domain members. Won't that in fact take care of getting the clock set correctly? -----Original Message----- From: John Valenti [mailto:[log in to unmask]] Sent: Friday, February 16, 2007 6:01 PM To: [log in to unmask] Subject: Re: [MSUNAG] DST 2007 on Windows 2000 I read some coverage on this that suggested you will also need to adjust the clock when DST used to change, so four times per year instead of just twice. (But you say they are domain members, won't the clock be set automatically wrong whenever they login?) I think we are down to about six Win2000 computers too. My plan was to just upgrade them to XP. I had forgotten about our Win2000 server until now, suppose that will need to be upgraded too. Ughhh! I'm glad we ditched Exchange here. I was reading about the patching strategy for some versions of that: you have to patch W2K, then within an hour patch Exchange. Otherwise it apparently goes thru and modifies meeting times in advance and they can't be easily fixed. On February 16, at 4:34 PM February 16, Wolf, Chris wrote: > As far as I can tell, we have six Windows 2000 computers left, all > members of our domain, none using Exchange. Several of them are > rarely used. My plan was to just have those users set the time > manually to the correct time on (or about) March 11 and September > 28 each year until we replace the computers (which probably won't be > that long). Why wouldn't that work? And even if they don't set it, as > long as they aren't using calendar software, how much does it matter > if their clock is wrong? >