UPDATE: We have now released the hotfix that corrects this issue for Exchange 2003 SP2. The article is: 930241 The Exchange 2003 database does not mount, and event IDs 9518 and 9519 are logge...
Updated Jul 01, 2019
Version 2.0
Blog Post
I have users using OMA on their phones and even though our Exchange servers are patched their appointments are off by 1 hour.[1 hour earlier] If their appointments are checked in Outlook or OWA they are at the correct time. It is not the phone as we get the same results if we open OMA in a workstation IE.
Called PSS and they acknowledged that this is an issue but there was no fix.
How can Microsoft ignore this issue when it is part of the code?
Will there be a fix or are my OMA users just going to have to wait till April 1st? Then deal with it Oct 28th?
It would have been better to know this was an issue before having to test and prove it was ideed an issue and not only in my environment.
Called PSS and they acknowledged that this is an issue but there was no fix.
How can Microsoft ignore this issue when it is part of the code?
Will there be a fix or are my OMA users just going to have to wait till April 1st? Then deal with it Oct 28th?
It would have been better to know this was an issue before having to test and prove it was ideed an issue and not only in my environment.