I'm seeing alot of posts regarding this issue, but no resolutions... as
others, I have a few users this change affected, and others it did not... all
have had the dst patch installed... the only difference I'm finding is that
the ones not affected have SP3 for Office 2003 installed, while the others
may have no SP, SP1 or SP2 (my bad).... but, after installing SP3 on one of
the systems, it did not repair the appointment. I'm wondering if this SP3
needed to be installed before the time change for it to work?
Also, it seems to be a recurring appointment that they have received (not
created) that has become the problem....
I noticed a couple systems this happened on last fall. By the time I was
able to research, the issue resolved itself when the original time change
date came - so, I didn't pursue it. Any suggestions would be helpful.
yes, its partly due to not having outlook fully updated. have you tried the
time zone tool?
http://www.outlook-tips.net/archives/2008/20080310.htm

Signature
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:
dailytips-subscribe-request@lists.outlooktips.net
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:
EMO-NEWSLETTER-SUBSCRIBE-REQUEST@PEACH.EASE.LSOFT.COM
> I'm seeing alot of posts regarding this issue, but no resolutions... as
> others, I have a few users this change affected, and others it did not...
[quoted text clipped - 13 lines]
> able to research, the issue resolved itself when the original time change
> date came - so, I didn't pursue it. Any suggestions would be helpful.
jilltre - 11 Mar 2008 23:01 GMT
I'll install the updates, then try the tzmove... thanks.

Signature
jilltre
> yes, its partly due to not having outlook fully updated. have you tried the
> time zone tool?
[quoted text clipped - 17 lines]
> > able to research, the issue resolved itself when the original time change
> > date came - so, I didn't pursue it. Any suggestions would be helpful.