DST E2k patch confusion

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

OK, I've been reading up on the DST patches, specifically how it
relates to E2k running on Windows 2000 server (our setup).

I've read MS' guide and through some general searching I'm still a bit
confused, so hopefully someone can enlighten me on the accuracy of the
following:

- From what I've been able to find, there is no public patch for
either Win2k or E2k, however, there are work-arounds, or we can pay
$4000 for access to the "extended support" patches.

- I found some posts indicating the "work-around" Exchange/Outlook
meeting-time-rebasing tools aren't one-time things and would have to
be run regularly in the 3-week gap between old and new time zone dates
in the absence of a patch.

- booking meetings via OWA is going to be off by an hour (CDO issues)

So, especially as the current setup is due to be mothballed within the
next year, my bigger question is: What happens if we do nothing - no
OS or Exchange or client-side patches, and simply adjust the time
manually, and turn off automatic DST adjustment? Our domain login
script runs a "set time" every time the user logs in, so as long as
the servers running the time service are correct, shouldn't this just
work and keep chugging along (assuming we also run off automatic DST
adjustment on the clients)? Does this affect OWA in any way?
Finally, what happens if a client that was (accidentally) in the new
DST time zone connected and booked meetings - would they just be 1-
hour off as well?

Thanks!

.

Quantcast