[windows2000] Re: Daylight Saving Time 2007
- From: "Toby Bierly" <toby@xxxxxxxxxxxxx>
- To: <windows2000@xxxxxxxxxxxxx>
- Date: Mon, 12 Mar 2007 07:48:13 -0800
Looks like Intelliadmin released a seperate patch for 98/ME. The other one
seems to work fine for W2K,XP, and NT.
-Toby
----- Original Message -----
From: George Yobst
To: windows2000@xxxxxxxxxxxxx
Sent: Sunday, March 11, 2007 8:17 AM
Subject: [windows2000] Re: Daylight Saving Time 2007
The W2K, W2K3, and NT patch worked fine here, as well as XP. The W98 didn't
- manually reset.
-George
On 3/10/07, Toby Bierly <toby@xxxxxxxxxxxxx> wrote:
Thanks for the link. It makes the OS updates much easier.
The Exchange patch just effects the CDO DST definitions, which is mainly
just OWA and Blackberry server, I believe, neither of which we use much. I
can't justify $4000 for it.
The Exchange Calendar Update Tool should update all the calendars fine.
That's the biggest thing for most of our users.
We'll find out for sure on Monday.
Thanks,
Toby
----- Original Message -----
From: George Yobst
To: windows2000@xxxxxxxxxxxxx
Sent: Friday, March 09, 2007 12:45 PM
Subject: [windows2000] Re: Daylight Saving Time 2007
I installed this and am crossing my fingers (and working Sunday morning):
http://www.intelliadmin.com/blog/2007/01/unofficial-windows-2000-daylight.html
-George
On 3/9/07, Toby Bierly <toby@xxxxxxxxxxxxx> wrote:
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
--
------------------------------------------------------------------------
George Yobst, Library Technology Analyst phone: 503.723.4890
Library Information Network of Clackamas County fax: 503.794.8238
16239 SE McLoughlin Blvd, Suite 208 web:
http://www.lincc.lib.or.us
Oak Grove, OR 97267-4654 email: george.yobst@xxxxxxxxx
"...it is impossible for anyone to begin to learn
what he thinks he already knows." - Epictetus
--
------------------------------------------------------------------------
George Yobst, Library Technology Analyst phone: 503.723.4890
Library Information Network of Clackamas County fax: 503.794.8238
16239 SE McLoughlin Blvd, Suite 208 web: http://www.lincc.lib.or.us
Oak Grove, OR 97267-4654 email: george.yobst@xxxxxxxxx
"...it is impossible for anyone to begin to learn
what he thinks he already knows." - Epictetus
Other related posts:
