Apple iOS 6.1 Release Can Overload Exchange 2010

An Exchange 2010 overload problem that started to occur after Apple released iOS 6.1 continues to go unfixed, although Apple and Microsoft have offered workaround solutions.

Apple's notification describes the problem as associated with "an exception to a recurring calendar event with a Microsoft Exchange account on a device running iOS 6.1." The glitch can generate repeated activity on Exchange 2010 SP1 or later servers, and it can also affect Exchange Online offered via Microsoft's Office 365 service. Users of iPhones get affected too, as the glitch apparently can drain the battery life of an iOS device.

Apple is offering a workaround that users can try, which involves resetting the user's Exchange account. Microsoft has responded to the glitch by issuing a Knowledge Base article, which contains three workarounds but no solution as yet. The two companies are currently investigating the problem, according to the article.

In the meantime, before a fix is available, Microsoft has described three workarounds. First, the Exchange account on the device can be removed and reinstalled. Alternatively, IT pros can set the Exchange throttling policy specific for iOS 6.1 users to avoid the excessive traffic activity. Third, Microsoft suggests blocking iOS 6.1 users altogether from tapping Exchange.

The calendar syncing problem, in which Exchange 2010 generates excessive log activity, seems to date back to late January, based on a Microsoft forum post description. Apple released iOS 6.1.1 on February 11 to fix iOS 6.1 problems on iPhone 4S models. That iOS 6.1.1 release fixes problems for Vodafone UK users, according to a press report. However, a poster at Microsoft's forum claimed that the iOS 6.1.1 release did not fix the Exchange problem.

"The 6.11 update does not fix this issue," the poster Peregrine Holdings wrote. "This update is specifically for iPhone 4s devices and addresses signal issues."

Microsoft indicated in its Knowledge Base article that it would update that article with any new information. The article currently recommends opening a case report with Apple over the issue.