Random meeting times off one hour (not a TZ issue)

Hi, all!  Workstations are Windows 7, Office 2010; Exchange server is 2k3.  This problem occurs (seemingly) randomly for different users, while other users report no problems.  Date, time, and time zones have been verified and are correct on all workstations in question, as well as on the Exchange 2003 cluster.

Occassionally (enough to be annoying, but not replicable) a user's meeting appointments will change time by one hour.  Meetings set for 1:00p will start appearing as 2:00p.  Today, on two separate calendars shared by three people, all meetings in one day advanced one hour.  All other meetings on other days are still correct.  Basically, our attorney's calendars are shared with their secretaries.  On this particular day in question, meetings were created on individual calendars by everyone concerned (two calendars, three people), and a couple others were meeting invites from outside the Company.  All meeting creators are in the same time zone as the company, and one invitee for one meeting is in a different time zone.  As I mentioned, all of today's meetings for this group were advanced one hour; past meetings and future meetings are still correct.

For another group (no shared calendars between the two groups) occassionally a single meeting will start displaying as one hour ahead of the time it was origianlly scheduled for.  Meetings this has happened on have both originated at the Company, and others have been originated outside the Company.

I cannot replicate the reported problem; all tests using different machines and different accounts on the same platform function correctly.  All meetings in question were created AFTER the recent DST time change here in US.  Most other users report no problems at all with their  meetings, but admittedly they don't schedule as many meetings as these two groups.  Also, please note that this is NOT a reminder issue; this is the time in the actual meeting changing from when it was originally set.

Are there any known unresolved issues with using Outlook 2010 in an Exchange 2003 environment that relates to something like this?  I've looked at what I could find regarding the time zone tool, but from what I've read is really doesn't apply to Outlook 2010.

Thanks, and suggestions welcome!

edit: these machines are all clean builds; none have had older operating systems on them, and none have had any other versions of Office/Outlook installed on them.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AmitIT ArchitectCommented:
SteveAtLSCAuthor Commented:
amitkulshrestha, thanks for replying.

None of the modifications/fixes in the referenced hotfix apply to us, so no, this hotfix has not been applied.

Also, all machines involved have the DST & TZ settings set correctly (see my original post).  Thanks!
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

AmitIT ArchitectCommented:
I would suggest that the DST patch is applied even thought you don't think it is related since it could be a cascading issue. Worse case you are up to date.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SteveAtLSCAuthor Commented:
Thanks!  I'll install the DST update anyway, and see what happens.  

Closing ticket since problem isn't readily replicable.
Thanks for the points and let us know how it turns out
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.