[windows2000] Re: Daylight Saving Time 2007
- From: "Allen, Christine" <Christine.Allen@xxxxxxxxxxxxxxxxxxxxx>
- To: "'windows2000@xxxxxxxxxxxxx'" <windows2000@xxxxxxxxxxxxx>
- Date: Fri, 9 Mar 2007 15:21:59 -0500
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:
