Update 12th February 2013: Yep, iOS 6.1 and 6.1.1 are out and causing more issues, where a meeting request response can cause catastrophic transaction log growth by resubmitting the same request repeatedly to Exchange 2010. You’ll find more information at the following Microsoft KB article:
The scripts below identify all post-iOS 6 versions as well as earlier versions, so you can choose a course of action for iOS 6.1 and iOS 6.1.1 devices (even the “switch it on and switch it off again” solution proposed by Apple) and also warn users with pre-iOS 6.1 devices not to upgrade their devices.
If you’ve been following the Exchange and Apple-related news lately, you can’t have failed to hear about a number of bugs in the new iPhone, iPad and iPod Touch OS, iOS 6. No – I’m not talking about the dire Maps replacement, I’m talking about a few ActiveSync related bugs that have caused issues for a number of companies and we’re starting to hear about more and more in the wild.
What’s the problem, then? Well, in iOS the two most widely reported ones relate to:
- AutoDiscover – It doesn’t work unless the Email Address and UPN match.
- Meeting Requests – The iOS device loses track of the organizer and replaces the device user as the organizer instead, allowing the device user to update or cancel meetings other people have asked them to attend. For more info, see KB 2768774
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.
Another method you might want to consider is to find those iOS 6 users within your organization and tell them about the issue. It might not be practical in all situations, but with the help of the script below (which will also report future and previous versions) you’ll be able to see what the task in hand looks like.
Use the script as follows:
.\Export-iOSDeviceStatistics.ps1 -OutputCSVFile .\output.csv
You’ll see output about iOS devices shown in the PowerShell session:
And the resulting CSV file can be opened in Microsoft Excel, or your favourite CSV editor:
- Exporting Exchange 2010 ActiveSync statistics for iOS Devices
- Configuring Certificate-Based Authentication for Exchange 2010 ActiveSync (Part 1)
- Enabling Exchange ActiveSync’s Quarantine Features in an existing organization
- Configuring Certificate-Based Authentication for Exchange 2010 ActiveSync (Part 2)
- Quickly generate reports on ActiveSync users