Re: DST E2k patch confusion

I think you're going to find that there's still confusion, but it's hard to
say how much. If all Outlook clients are patched and meetings rebased,
things should in general look fine. But if an unpatched client is used or
OWA is used that will show the wrong time, and if they're used to create new
items or modify items, they'll cause wrong times to show.


<mabbuttg@xxxxxxxx> wrote in message
news:1171320678.476549.326730@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
So, if I understand this correctly, the 1 hour off will only be for
clients where the OS patch has been applied, correct? Eg, in my plan
the Exchange box's server OS and the clients authenticating on the
network will have the time manually updated (the time zone itself
won't change), but no patches applied at all, so any of them should
book with the appropriate time once both times have been updated,
correct?



On Feb 9, 8:13 pm, "andy webb" <a...@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
yes, if you can cope with the confusion for 3wks this spring and a week
in
the fall, you could just do nothing.

What a lot of folks are suggesting is that users go through and put the
real
starting time of the meeting into the subject line ("Staff Meeting 11a
Central"). That will help identify when meetings are off due to DST
issues.

<mabbu...@xxxxxxxx> wrote in message

news:1171050058.894942.268790@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



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!- Hide quoted text -

- Show quoted text -




.