Microsoft is aware of an increase in the number of incidents that are related to meeting requests. This increase coincided with the release of Apple iOS 6 devices. In these incidents, users who are attendees of a meeting may unintentionally become the meeting organizer.
When this issue occurs, the organizer information is not changed when you view the item in Microsoft Outlook and Outlook Web App (OWA). If a meeting attendee takes action on a meeting item by using an Apple iOS 6 device, and then synchronizes with Microsoft Exchange Server by using Microsoft Exchange ActiveSync (EAS), the attendee may become the meeting organizer.
Additionally, the Apple iOS 6 device may incorrectly let the device user (attendee) act as the meeting organizer. For example, the attendee can send meeting updates or cancellations to all the original meeting attendees.
This issue can affect users of Microsoft Exchange Server 2013, Microsoft Exchange Server 2010, Microsoft Exchange Server 2007, and Microsoft Exchange Server 2003.
Note This issue has been fixed in Microsoft Exchange Online for Office 365 and in Exchange Server 2013 Cumulative Update 1 (CU1).
This issue was investigated by Microsoft and Apple. Apple released the iOS 6.0.1 Software Update that was intended to address the issues that were reported by customers.
For more information about this iOS 6 update, see the "Resolution" section.
This article will be updated with additional information when the information is available.
This issue is not the same issue that was fixed in Exchange Server 2007 Service Pack 3 (SP3) Update Rollup 4 (RU4). The issue that was fixed in Exchange Server 2007 SP3 RU4 is documented in the following article in the Microsoft Knowledge Base:
2521063 You are incorrectly displayed as a meeting organizer after you synchronize the meeting by using your mobile device in an Exchange Server 2007 environment
Install Exchange Server 2010 Service Pack 3
To resolve this issue, install Exchange Server 2010 Service Pack 3 (SP3). For information about Exchange Server 2010 SP3, visit the following Microsoft website:
Apple has released the iOS 6.0.1 Software Update. This update is intended to fix several issues. This includes a bug that affects Exchange meetings and applies to Microsoft Exchange Server 2010, Microsoft Exchange Server 2007, and Microsoft Exchange Server 2003. However, because of a meeting response issue on the device, we recommend that you install the most recent update that is available.
If you cannot install Exchange Server 2010 Service Pack 3 or update devices to the most recent iOS version, use one or more of the following methods:
Recommend that users do not take actions regarding alerts in which the name of the meeting organizer is missing from the alert. For example, recommend that users not tap Delete Event when one of the following is displayed in a new invitation:
Invitation from someone
Invitation from user_name
Instead, recommend that users do not take action, and that they close the alert.
Set the New Invitation Alerts setting to Off in the Calendar settings on the iOS device.
Recommend that users do not take immediate action on Calendar items that are displayed in the Inbox. For example, recommend that users wait until the Accept, Decline, Maybe options appear on the Calendar item.
Recommend that users decline meetings by using Microsoft Outlook, Microsoft Office Outlook Web Access, or Microsoft Outlook Web App.
Recommend that users do not update to iOS 6 now.
Block iOS 6 by using the Exchange Server 2010 Allow/Block/Quarantine feature. For more information about the Exchange Server 2010 Allow/Block/Quarantine feature, see the following Exchange Team Blog post:
Block iOS devices that have mailboxes that are hosted on earlier versions of Exchange Server. For more information about how to block iOS devices that have mailboxes that are hosted on earlier versions of Exchange Server, go to the following TechNet website:
Block users who have a delegate from using Exchange ActiveSync.
Block users who have delegate access from using Exchange ActiveSync.
Recommend that users use a different email client to synchronize email message data. For example, recommend that users use Outlook Web Access or a third-party solution to synchronize email message data.
Recommend the POP protocol or the IMAP protocol for data synchronization on the device.
Troubleshoot ActiveSync issues with Exchange Server
For Managers in a Delegate Manager pair, make sure that only the Delegate receives the meeting requests and responses.
Note The first two procedures are general best practice recommendations for any organization that uses Microsoft Exchange Server and Microsoft Outlook. The third procedure is recommended by Apple. The third procedure has helped in some, but not all, scenarios.
Additional step for Exchange Server 2010
As a general best practice, we recommend that you enable the Exchange Calendar Repair Assistant (ExCRA). For more information about the ExCRA, see the following topic from Microsoft TechNet website:
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
As more information becomes available, it will be summarized under the Scenario 1.2 heading in the following article in the Microsoft Knowledge Base:
2563324 Current issues with Microsoft Exchange ActiveSync and third-party devices
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.