Users of Apple’s new iPhone 4 phones or iPhone 3G, 3GS or iPod Touch users who upgraded to iOS 4 have been reporting issues synchronizing to Exchange Server using Exchange ActiveSync (EAS). The issue with Apple’s latest mobile operating system, iOS 4, also results in additional load on Exchange Server, which may cause performance issues on Exchange 2010/2007 Client Access servers. The issue isn’t limited to iPhone connectivity to Exchange Servers, but also extends to Google’s Gmail service, which uses EAS to offer mobile email access.
iOS 4’s default timeout for EAS requests is set to a very low 30 seconds, causing the requests to timeout and resulting in additional requests being made by the iOS 4 device.
Apple has released a configuration update that fixes some of these issues. The Apple kb article states:
Immediately after updating to iOS 4, some users may notice that Exchange ActiveSync Mail, Contacts, or Calendars do not sync, or sync very slowly. In addition, some Exchange Server administrators may notice their servers running slowly.
The update increases the timeout for EAS requests made by iOS 4 devices. In particular, the update modifies the DefaultEASTaskTimeout parameter to 240.0 (240 seconds or 4 minutes). Config files are XML, so you can modify this value to what’s appropriate for your environment— although the 240-second timeout should work for most environments. If you feel it’s inadequate, please share your experience in the comments section.
According to Apple, “the profile should be installed on as many iOS 4 devices at your company as possible.” Head over to iOS 4: Exchange Mail, Contacts, or Calendars may not sync after update on Apple.com to download the config file.
{ 17 comments… read them below or add one }
Thanks for the update – glad Apple fixed the issue. Are there any other issues with iPhone 4 and Exchange?
We’re still having issues after updating the config!
We had issues with the 4.0 upgrade. This one wasn’t our problem. We had server config problems. We got ours fixed by TECHNOKOZ. I’m glad we found them
What was the timeout value in iOS 3.x?
ios3 was 240 seconds
Still not working for me either with the update. Does size of your e-mail account have anything to do with this? I can get my folders and can actually send e-mail from my phone – but I still can’t receive e-mails or see them in my inbox or other folders.
I spoke too soon – after letting the phone sit for about 20-30 minutes it ended up downloading my messages and seems to be working. This might be the fix I needed afterall. Thanks for the posts!
I installed the fix and still cant connect to my exchange server… why did I leave my Bberry!!!!
Same here – applied update but no joy yet! Come on Apple, step up and fix the issue! Wish I’d stuck with the 3GS but I do like the iPhone 4, and haven’t noticed any reception issues.
To all those the say it does not work: Did you REBOOT the PHONE after you installed it (a noted in the kbase!)
@Jakob: Yes, rebooted a few times.
updated from apple and changes the timout to 640 sec but still not verifying my account. i reboot and tried again and again, anyone else still having a issue?
Same issue for me…downloaded the apparent apple fix. Rebooted the iphone 3Gs with IOS4…and the issue still comes back every so often.
Exchange 2007 SP3 has a “Fix” that stops Apple Mail from accessing my work Exchange account. Apparently Apple Mail could immitate OWA access, but now this is considered a security risk and has been fixed so I can no longer use my iMAC. Cheers !
I just changed jobs and tried to load my new work email on my phone with no luck.
Email address: [email protected]
Server: owa.company.com/exchange (same as if I was using my desktop)
Domain: nothing
Password :*******
I’ve tried it with SSL on and off. I can access my worl email from my desktop but not on my phone. Please slap me up side the head and help.
Sorry forgot to mention the sever is exchange 2003 SP2. thanks
Try Pop3, i use this for the meantime Apple has not found fix yet. Better show all the config for the Exchange, maybe that will solve the issue – for the MS Exchange programmers.
Good luck.
{ 6 trackbacks }