DST update moves existing meetings by 1 hour during 1st 3 weeks of DST

Existing meetings (including reoccuring meetings) show one hour off (advanced) in the calendar for the additional 3 frontend weeks of DST after the updates have been appied. Newly created meetings are reflected accurately. Is there anything I can do to address the Existing meetings aside from having the users recreate them to reflect the accurate time?

Subject: DST update moves existing meetings by 1 hour during 1st 3 weeks of DST

Please confirm that the “New” meetings have the correct StartTimeZone and EndTimeZone values 3 2 1 11 1 1 rather than the old values. Having the documents appear one hour before the intended start suggests that the TimeZone Agent was run on them, but the Operating System patch is not applied or taking effect.