From: Gary Britt 

Also, after looking at the Microsoft KB article on this issue it seems to
me one might be able to just copy/export the two relevant registry keys
from a patched XP/2003 machine and then use that .reg file to patch any
number of similarly situated Win2K machines.

The MS KB article referenced in the link you give below indicates the two
relevant registry entries are:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

A reboot after patching is probably required.


I haven't followed this through with regard to the special cases for
Outlook/Exchange but this or something similar might work for that as well.

Just a thought off the top of my head.

Gary

Frank Haber wrote:
> A monumental pain for everyone (well, Yanks and Canucks, anyway) this
> month.
>
> For those with Win2k workstations and no extended support extort^H^H
> contract,
>
> http://www.intelliadmin.com/blog/2007/01/unofficial-windows-2000-daylight.htm
l
>
>
> seems to work.  Note that Exchange and Java runtimes may need updating,
> especially if you have jars that need some godforsaken 1.3/4 back-version.
>
> And for 98, there's always tzedit - not too bad if it's a desktop that
> never changes time zones.
>
> Why do I think this will be a "stealth y2k problem?"  Smells like one,
> from here.

--- BBBS/NT v4.01 Flag-5