Wednesday, February 13, 2013

Apple Screws Up iOS EAS Implementation AGAIN! - Exchange Suffers


Has your Exchange 2010 CAS recently started experiencing heavy CPU, insane transaction logs growth (aka DoS), Apple might be the cause. Apple released iOS 6.1 last week (beginning of Feb) and it has a "slight" EAS bug in it. ;-) Another bonus... it drained iOS batteries and wasted data bandwidth. So bad... Vodafone txted all iPhone users to NOT upgrade to 6.1. Oops.... and 6.1.1 doesn't fix it...

You would think a large company (aka Apple) that prides itself on releasing "amazing products" would not repeat their mistakes in the past (iOS 4), but sadly history is repeating itself. iOS 6.1.1 fixed another problem. This is why I am not a fan of EAS. It's buggy since vendors don't have a real incentive or pressure to make sure EAS works well. Sure, Microsoft releases "guidelines" and crosses it's fingers vendors follow, but it's a frequent problem. I know, since I see the EAS connections logs and the Exchange problems they cause. I'll post in the future, how to look this up in your Exchange logs. I'm leaving EAS soon enough... I'll be happy to return to the BlackBerry ecosystem when the Q10 is released. That's another post...

See the Microsoft KB article, but to summarize, there are is a quick fix:

- delete the Exchange account from the iOS device and re-add

iOS 6.1 EAS Bug - Workarounds

iOS 4 EAS Bug (walk down memory lane)

-Ben

2 comments:

Keith said...

BES 10 uses EAS so there may no escape:

http://www.zdnet.com/youll-need-to-deploy-bes-10-for-blackberry-10-to-make-any-sense-7000005551/

Ben Serebin said...

BB 10 (that's the handheld) can use EAS or can use BES 10 (server) which is still MAPI CDO based. The free BB10 EAS approach has different feature set.

So, I can escape EAS and have a full Exchange sync experience (read: Notes) and full secure management. Take that EAS....

-Ben