Performance: Mobile Devices Hijacking Calendar Meetings
There is no workaround for this issue
There have been a number of reports of meeting hijackings recently, both at Cornell and at other institutions and companies. This happens when someone who is invited to a meeting inadvertently becomes the owner of the meeting on the calendar, and changes or deletes the meetings for other invitees.\n \nWHAT CAN OCCUR?\nA mobile device used by one of the meeting invitees incorrectly changes the owner field in the meeting from the original organizer to their own NetID. \n\n• The primary effect will be that the invitee will no longer get updates from the organizer, or updates may create a second meeting at the same time.\n\n• Any time thereafter, if an invitee declines an occurrence of the meeting, and the calendar believes that the invitee owns the meeting, it sends cancellations to everyone else on the meeting list. Depending on which clients the other attendees are using and what actions they take, this may remove the meeting from their calendars as well.\n\nWHAT'S THE CAUSE?\nThe fault seems to be in ActiveSync devices such as iPhones and Androids. It does not appear that you have to accept or update the meeting on the ActiveSync device to cause the problem; it is sufficient that the device is turned on and synchronizing with Exchange. iPhones running iOS 6 seemed to cause a particular flurry of these cases. iOS 6.0.1 has an update that was alleged to address this problem, but cases have been observed after this update was installed. \n\nWHAT SHOULD I DO?\nThere's probably no way to repair such a meeting after it is damaged. If you observe any of the following symptoms, please contact the organizer of the meeting:\n\n• A meeting on your calendar lists you as the organizer when you know you're not.\n\n• You receive a meeting update or cancellation from someone who is not the original organizer.\n\nThe organizer should cancel the original meeting or meeting series and re-issue the meeting invitation. This is the only definite way to remove the problem; other attempted methods usually result in the problem resurfacing later.
Timeline of Changes
|This is not an issue isolated to Cornell. At this time, we are providing this information for awareness purposes only. We will continue to monitor for patches to fix this issue and provide an update if/when a solution is provided.||This is not an issue isolated to Cornell. At this time, we are providing this information for awareness purposes only. We will continue to monitor for patches to fix this issue and provide an update if/when a solution is provided.||2012-11-13||00:00:00|