Since the release of iOS6 devices there have been a variety of reported issues from people using Apple devices to connect to Exchange Server with ActiveSync. I haven’t covered the issues here yet, but fortunately for all of us several of my fellow Exchange MVPs have.
Looking for the issues with iOS 6.1? Click here
As Tony Redmond summarized in his report:
Online forums have many reports about ActiveSync problems encountered by Exchange 2007 and Exchange 2010 users after upgrading their Apple devices to iOS6. One issue is when a user apparently “hijacks” a meeting by being made its organizer after they open a meeting request, sometimes associated with delegate access to the organizer’s mailbox. A related issue might be when a user edits a meeting on their device only to send a cancellation message to all involved, even when the meeting request isn’t sent by a delegate.
Pretty serious issues, and although I have not been able to reproduce them myself it is clearly impacting many customers and causing some havoc.
Unfortunately this is not a new scenario. Paul Robichaux explains:
EAS is a fairly complex protocol and Apple has displayed a somewhat cavalier attitude towards verifying that their EAS clients behave properly. If you don’t believe me, all you have to do is look at this list of known EAS issues with third-party devices and see how many of them involve iOS.
The usual pattern for these bugs is fairly predictable:
- Apple (or another EAS licensee) releases an update.
- People start complaining in various fora that some EAS-related functionality is broken. However, these reports are only rarely made directly to either Microsoft or the vendor.
- A critical mass of reports accumulates and begins to draw attention. This is often accelerated by the opening of support cases with either Microsoft or the ISV.
- The source of the problem is identified, a resolution is developed, and everything is fixed.
- GOTO 1
Sad but true, and even though the latest “hijack” issues now have their own Microsoft KB article it only provides some information on the symptoms and this note on the cause:
Microsoft is aware of an increase in issues for meeting requests that coincided with the release of Apple iOS 6 devices. When this occurs, users that are attendees of a meeting may inadvertently become the meeting organizer.
Microsoft does provide the following suggested workarounds:
To work around this issue use one or more of the following methods:
- Recommend that users do not take any action on Calendar items, to include Meeting Requests and Responses in the Inbox, using their iOS device.
- Recommend that users not update to iOS 6 at this time.
- Block iOS 6 using the Exchange Server 2010 Allow/Block/Quarantine feature. See the following post on the MS Exchange Team Blog:
- Block iOS devices for earlier versions of Exchange Server using the following documentation:
- Block anyone who has, or is, a delegate from using EAS.
- Recommend a different client, such as Outlook Web Access or a third-party e-mail synchronization solution.
- Recommend the use of POP/IMAP for e-mail synchronization on the device.
Whether these are practical for your organization is a matter for you to decide, though I tend to agree with Steve Goodman on the matter:
Some people have suggested a good solution to this is to block iOS 6, however I’m not so sure. As a consultant I’m on the road a lot, and if my device was blocked then I’d be in deep water – I rely on it to keep in touch with customers and colleagues when I’m out and about. So, I don’t think blocking an update that comes through semi-automatically will win Exchange administrators any friends within their business.
So if you’re stuck in the middle ground between not wanting to block iOS6 devices, but wanting to mitigate the risks as much as possible, then you’ll need a way to communicate the issue to those users who are using iOS6 devices.
Steve Goodman to the rescue with his new Export-iOSDeviceStatistics.ps1 script. A quick and easy solution to export a list of iOS devices, their version numbers, and the usernames of the people who are using them.
Steve also covers the other major issue that iOS6 users are running up against, that Autodiscover doesn’t work. However Steve notes, as have others who have tested the issue as well, that it does work as long as the user’s UPN and email address match.
Jason Sherry writes:
Per several Exchange MVPs it seems that Autodiscover (the feature that will automatically configure you phone to connect to Exchange based on an e-mail address and password) doesn’t work in many cases with Exchange.
This has been verified by multiple people, see Clint Boessen’s blog post here: http://clintboessen.blogspot.com.au/2012/10/apple-iphone-ios6-and-exchange.html for a bit more details.
One person was able to get it to work, but only if the e-mail addresses entered on the iPhone matched the user’s UPN (User Principal Name aka e-mail like login).
All in all a rough time for Exchange administrators and customers.
Are you experiencing issues with iOS6 and ActiveSync?