One of the great benefits to running one of the world’s largest Exchange deployments is that we at Microsoft get to see all the things that our customers face on a daily basis. With the recent rele...
Updated Jul 01, 2019
Version 2.0
Blog Post
<quote>What do you mean by "happens when the iPad user in in a different domain"? Do you mean that someone in a different domain sends a meeting request that is then "Adjusted" on the iOS device of a user in a different domain?</quote>
Someone in my domain invites someone *outside* our domain - different forest if you will - and that person responds using his iPad. He declines, and the meeting is deleted - completely - from the calendar of the organizer in my domain. This, as I indicated, should never happen; but especially when the person invited/declining is in another domain. He has no credentials/authority in our domain at all. In fact, only the organizer has permission to change or delete appointments on their own calendar.
Finally - as I understand it - the *other* invitees (inside our domain) receive "cancellation" notices.
So I think that there are two problems: the iOS and Android devices are not following the protocols correctly, AND Exchange is reacting incorrectly to the malformed responses.
<quote> If so, I don't see how it is much different than being in the same domain; the entry on Dave's calendar from Company A is the original but was sent to Joe at Company B. Joe accepts the meeting (whether by his own hand or by his delegate) then later his iOS device "Updates" the appointment to mark him as the organizer and may or may not send a cancellation to Dave and/or other attendees. </quote>
Joe can send all the crap he wants; he should not be able to *delete* Dave's meeting.
<quote>The issue is not that Exchange has a bug, but rather the problem is in Apple's implementation of ActiveSync. Sure, Exchange could act as a "Gatekeeper" and deny this type of erroneous update, which would be a very helpful thing to mitigate these issues before they occur, but as long as EAS is implemented properly there should be no need for this.</quote>
(Welcome to the brave new world :-)
Apple AND Google. I have experienced this myself where one of my staff carrying an Android phone gets the message "you cannot accept the invitation, as you are the organizer" - or words to that effect.
This is complex stuff, and hard to nail down; I agree. But as I have said, we can't just point fingers here.