toby_amsterdam
asked on
ActiveSync and calendar event corruption
I am using Exchange 2010, Outlook 2011 for Mac, ActiveSync for iPhone, iPad and Android sync.
The problem I'm having...
When users accept meeting requests on mobile devices, subsequent updates for that particular event are not processed and meeting request emails become just emails without accept or decline options. Also the event update is not reflected on the mobile device calendar but it does update on Outlook on the PC.
Accepting the meeting request on the mobile device seems to corrupt the calendar event.
Does anyone have a solution for this? I've updated iOS on the devices and still the same issue.
The problem I'm having...
When users accept meeting requests on mobile devices, subsequent updates for that particular event are not processed and meeting request emails become just emails without accept or decline options. Also the event update is not reflected on the mobile device calendar but it does update on Outlook on the PC.
Accepting the meeting request on the mobile device seems to corrupt the calendar event.
Does anyone have a solution for this? I've updated iOS on the devices and still the same issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Maybe - I haven't used either.
Simon.
Simon.
It's strange to blame Apple devices for this behavior, since Apple is just using the ActiveSync stack they licensed from Microsoft in their Calendar.app - the same ActiveSync stack deployed by Google in Android. This would implicate Microsoft in any problems arising from iOS/Android handling of calendar items.
This may be why Microsoft eschewed their own ActiveSync tech for their OWA.app? Perhaps they wanted their own app to actually work as expected?
This may be why Microsoft eschewed their own ActiveSync tech for their OWA.app? Perhaps they wanted their own app to actually work as expected?
Microsoft licenced the protocol.
How that protocol is implemented is down to the vendor.
If it was any other way then all clients would be equal. They are not.
This Wikipedia article outlines the differences.
http://en.wikipedia.org/wiki/Comparison_of_Exchange_ActiveSync_clients
As for the Microsoft OWA app, that is being replaced by technology they have purchased via Accompli, which uses ActiveSync.
Don't be an Apple apologist - they are the ones responsible for these problems - their implementation of ActiveSync is dreadful.
How that protocol is implemented is down to the vendor.
If it was any other way then all clients would be equal. They are not.
This Wikipedia article outlines the differences.
http://en.wikipedia.org/wiki/Comparison_of_Exchange_ActiveSync_clients
As for the Microsoft OWA app, that is being replaced by technology they have purchased via Accompli, which uses ActiveSync.
Don't be an Apple apologist - they are the ones responsible for these problems - their implementation of ActiveSync is dreadful.
You had my attention and respect until you dragged out the tired phrase "Apple apologist" and then seemed to apologize for Microsoft by saying it's all the third-party implementation causing the problem and none of Microsoft's responsibility. It's no secret that ActiveSync has had ongoing issues since long before Apple or Google licensed the tech. Perpetuating a "Brand-X is always to blame" mythology doesn't constructively contribute to the practical troubleshooting spirit of this forum.
Truth is all parties have culpability. Microsoft has a responsibility to be sure ActiveSync performs as expected and third-parties need to implement the tech in the best way possible. It's fair to say that there have been failures on both sides of that equation. The bottom line is, it's not practical to say to someone having problems that they should "never use this or that mobile device," when millions currently do with no issues whatever. I would suggest it is better to offer either realistic solutions or none at all. My two cents.
Truth is all parties have culpability. Microsoft has a responsibility to be sure ActiveSync performs as expected and third-parties need to implement the tech in the best way possible. It's fair to say that there have been failures on both sides of that equation. The bottom line is, it's not practical to say to someone having problems that they should "never use this or that mobile device," when millions currently do with no issues whatever. I would suggest it is better to offer either realistic solutions or none at all. My two cents.
ASKER