Seeing that we have seen some support calls on this already, we wanted to highlight a KB article that was written about the above mentioned issue. The article in question is: Meetings are unexpec...
Updated Jul 01, 2019
Version 2.0
Blog Post
2 MIN READ
Meetings are unexpectedly moved one hour ahead in the last week of October 2006 in Exchange Server 2003
So the code only runs against appointments created with CDO apps like OWA, PDA and blackberries and to take place between 22/10/2006 and 29/10/2006.
Can we get a count of the number of items changed?
Why does the code only run for a weeks worth of appointments? rather than the 6months of BST that need to be corrected? either tha or it knows to use local time so after 29th October it is already factored in to the equation.
Can we get a count of the number of items changed?
Why does the code only run for a weeks worth of appointments? rather than the 6months of BST that need to be corrected? either tha or it knows to use local time so after 29th October it is already factored in to the equation.