I chose a different Time zone and applied it. I then changed back to CST.
No luck in moving the appointments to the correct setting. Interesting that
the appointments set for after April 1 held the correct time. Why did MS
program those in the interim to change? An appointment time is just that no
matter what. It should not change with DST.

"Diane Poremsky [MVP]" wrote:

TZedit seems to be the root of a lot of problems. Did you choose another tz,
apply it then change back to the correct one? That, along with changing the
dst setting and changing it back, seem to take care of many problems.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



"cn" wrote in message
...
I verified the update is installed. I used tzedit to show that the CST is
set for the 2nd Sunday in March and the 1st Sunday in November. I
verified
that CST is the time zone on both the operating system and Outlook. This
was
all done immediately! What is the current fix?

"Diane Poremsky [MVP]" wrote:

Did you verify the Tine zone update is installed in windows? Did you use
the
correct time zone for the "move to" zone?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



"cn" wrote in message
...
Like so many others I applied the tz move.exe and my Outlook calendar
appointments still are off 1 hour after the DST change for CST.

I have Windows XP SP2 with Outlook 2003. The current appointments all
moved
to one hour later than originally scheduled. What is the fix? If
Microsoft
doesn't have one, is there a third party fix anyone knows of?