[windows2000] Re: Daylight Saving Time 2007
- From: "Toby Bierly" <toby@xxxxxxxxxxxxx>
- To: <windows2000@xxxxxxxxxxxxx>
- Date: Fri, 9 Mar 2007 13:51:10 -0800
I have seen nothing anywhere yet that is in contradiction with the original
order I laid out (Individual Workstations, then Servers, then Exchange, then 4
options to fix Outlook Calendars) except if you rely heavily on OWA, it says to
reverse the last two. Below is still the latest greatest from MS:
General order of updating for DST changes:
Normal guidance Environments with users who rely heavily on Outlook Web
Access**
1.. Apply updates to Windows operating systems on Windows Servers.
2.. Apply updates to Windows operating systems on individual
workstations.
3.. Apply the Exchange Server DST update.
4.. Run the Exchange Calendar Update tool against all affected users,
servers, or both OR correct individual e-mail application calendars using the
Outlook Time Zone Data Update tool.
1.. Apply updates to Windows operating systems on Windows Servers.
2.. Apply updates to Windows operating systems on individual
workstations.
3.. Run the Exchange Calendar Update tool against all affected users,
servers, or both OR correct individual e-mail application calendars using
theOutlook Time Zone Data Update tool.
4.. Apply the Exchange Server DST update.
However, my confusion is not with the typical overall order of things but the
details of each. For instance, where do I find patches for earlier versions of
Windows? All I see is XP. Is there any other way to patch Exchange 2000 other
than paying $4000? What are the repercussions of not patching Exchange 2000?
Will the Exchange Calendar Update Tool work correctly if Exchange itself isn't
patched? What about the Outlook Time Zone Data Update Tool? Is it reliant on
Exchange being patched? How would it work if we didn't apply any patches and I
just adjusted the servers' time and had anyone who didn't use TS adjust there
time manually this weekend, and again in 3 weeks?
These are the obvious questions that someone with my environment would have and
I have found nothing yet in Microsoft's literature that answers any of them,
and I have been reading up on this for over 8 hours.
Thanks,
Toby
----- Original Message -----
From: Allen, Christine
To: 'windows2000@xxxxxxxxxxxxx'
Sent: Friday, March 09, 2007 12:53 PM
Subject: [windows2000] Re: Daylight Saving Time 2007
The order is not clearly laid out like it was in the other article you have.
(I had that article too, but in the middle of my process realized that they
changed the order, big mess!)
You need to read the whole article, but in a nutshell patch all your servers
and workstations first. Then rebase your exchange server with either the
Exchange rebasing tool or the outlook (desktop) tool. Then apply the DST
patch. But it sound like your not paying for that so I guess you don't need to
apply it?
------------------------------------------------------------------------------
From: windows2000-bounce@xxxxxxxxxxxxx
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Toby Bierly
Sent: Friday, March 09, 2007 3:44 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: Daylight Saving Time 2007
First off, thank you for your reply.
I'm sorry, I'm having trouble finding an order in that article. I find a lot
of information about the Exchange Calendar Update Tool, but nothing about order
other than it says, "Before you run the Exchange Tool, . . . Install the
Windows daylight saving time update on client and server computers." How is
that different from the order I noted in the first email?
Of course I might have missed something. That document is a book. I have to
hold down the Page Down key for 15 seconds to get to the bottom. I haven't had
the chance to read the entire document carefully yet, but I had already skimmed
through most of it.
Still desperately searching for information.
Thanks,
Toby
----- Original Message -----
From: Allen, Christine
To: 'windows2000@xxxxxxxxxxxxx'
Sent: Friday, March 09, 2007 12:21 PM
Subject: [windows2000] Re: Daylight Saving Time 2007
Actually, the order has changed. You may want to download the article
930879.
----------------------------------------------------------------------------
From: windows2000-bounce@xxxxxxxxxxxxx
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Toby Bierly
Sent: Friday, March 09, 2007 3:12 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Daylight Saving Time 2007
I'm still trying to figure out the best way to go about updating/patching
any/all of our servers/computers. I wish I could find some clearer
instructions (than Microsoft's) on the best way to proceed, especially with
some older systems.
We run an SBS2000 server plus 2 other servers (SQL, TS) which both have W2K
Server. As such, we are still on Exchange 2000 as well. Our desktops/laptops
are about 60% XP / 20% W2K / 20% NT. We have 4 users with Blackberry's, but
I'm not sure how much they use their Calendars.
Everyone that has NT basically uses the computer as a thin client, and
works all the time in Terminal Server.
My biggest problem comes in that Exchange 2000 DST updates are only
available under Extended Support for a fee of $4000, which I can guarantee will
not happen. I'm assuming there is no other way to patch it for a reasonable
price (for a small business like ours), is there?
The order Microsoft recommends is:
1. Apply updates to Windows operating systems on individual workstations.
2. Apply updates to Windows operation systems on Windows servers
3. Apply the Exchange Server DST Update
4. The IT administrator has one of four alternatives:
1.. Run the Exchange Calendar Update tool against all affected users,
servers, or both.
2.. Push out the Outlook Time Zone Data Update tool to the clients and
let the users update their own mailboxes.
3.. Run the Exchange Calendar Update tool against all affected users,
servers, or both, but only modify recurring appointments. Then ask users to
rebook single instance appointments that fall into the extended DST period or
ask them to run the Outlook Time Zone Data Update tool.
4.. Run neither the Exchange Calendar Update tool nor the Outlook Time
Zone Data Update tool. Ask users to examine their calendars and rebook as
necessary.
And this is the point at which I become utterly confused.
First, I try to find the updates for individual workstations. There is a
patch for XP, but none for previous versions. I have seen mention of a tzedit
tool that will work for "all" versions of windows, but cannot find a link to it
yet. Maybe I am missing something obvious.
Once I find a way to patch W2K, I assume that will work for the 3 W2K
servers.
Next challenge is wrapping my mind around the interplay of Windows Servers,
Individual Workstations, Outlook, and Exchange Server. Since I can't update
Exchange 2000, what happens if I go ahead and run updates for Servers,
Workstations, and Outlook? What order should I do those in?
Then we have differences in Outlook between recurring (which store DST
info) and single-instance (which do not) appointments.
I'm starting to think the best thing to do is tell everyone to just
manually adjust their time as needed (one - hour forward this Sunday, one -
hour back in 3 weeks, when DST takes effect), but there has to be a better way.
It seems I should patch the Operating Systems at least, but then what will
happen in Exchange Server with Email and Calendars? Will all emails say they
arrived an hour off. Will everyone's appointments be an hour later then they
originally scheduled.
Is anyone else as confused as I am? Can anyone provide a little direction?
I'd be so grateful.
Thanks,
Toby
Other related posts:
