Apple fixes iOS 6.1 bug that hit Microsoft Exchange users

Last week, we reported that people who used an iPhone or iPad with iOS 6.1 had problems connecting to s Microsoft Exchange-based server. Microsoft said that action caused the server's resources to take a performance hit with both memory and CPU usage increasing by a large amount.

Today, CNet.com reports that Apple has now released iOS 6.1.2 for those device owners. The brief release notes state that the new version fixes "an Exchange calendar bug that could result in increased network activity." The new version also fixes an issue which could have caused iOS products to have their battery life cut down by connecting to Microsoft Exchange servers.

The bug was first discovered by some users in late January but didn't get a lot of attention until last week. Microsoft gave some workarounds that helped some iOS users before today's update. They included removing and later re-creating the Exchange account connection for the iOS 6.1 product, while another was for the administrator of the Exchange server to create a custom throttling policy for those same users.

The third solution was to have IT workers block access to Microsoft Exchange servers from being used by iOS devices. With the new patch in place, those IT employees can now go ahead and let those users connect to the servers once again.

Source: CNet.com | Image via Microsoft

Report a problem with article
Previous Story

Apple was hacked, small number of Macs infected

Next Story

Microsoft Lync 2013 Skype support revealed; mobile app ports coming soon

18 Comments

Commenting is disabled on this article.

Brony said,
Exchange Server is a good example why "vendor lock" is evil.

uh, no one is forcing anyone to use exchange server...... and Exchange is a very good system... vendor lock.... bs... go use Notes and come back and tell me how great that is...

you want vendor lock, Apple is a prime example, use all our products!!!! and only our products!!!!! except if we don't have a product for that line... like exchange... or high end servers.. then go to MS....

Whoa Whoa Whoa. Lets not get crazy here. I don't care how bad this guy's comments have been in the past. No one..I mean no one should have to switch to Lotus Notes.

I mean come on... don't make anyone go to Notes :'(

jakem1 said,
All your posts are ridiculous.

becauuuuuse ____?
a) im a troll and i like to troll.
b) im not sure but i think that you are a troll.
c) random think.

neufuse said,

uh, no one is forcing anyone to use exchange server...... and Exchange is a very good system... vendor lock.... bs... go use Notes and come back and tell me how great that is...

you want vendor lock, Apple is a prime example, use all our products!!!! and only our products!!!!! except if we don't have a product for that line... like exchange... or high end servers.. then go to MS....

I used to do service for exchange server, the service is ABSURDLY EXPENSIVE, for example, sometimes i charge the migration of account from older version $50 - $100 per account. And sometimes it is not possible without leaving the old server just sitting duck in a corner.
So, it is not rare that some business are sticking with exchange 2003.

Exchange Server is only cool for a big business (with a big pocket) and only if it uses the whole pack, including Cisco IP phones.

However, it could be worst, for example Lotus Notes.

Brony said,

However, it could be worst, for example Lotus Notes.

Funny, as much as people bag Notes, the Domino email server was damn easy to maintain. I'd take it over having to fix Exchange any day of the week.

lkernan said,

Funny, as much as people bag Notes, the Domino email server was damn easy to maintain. I'd take it over having to fix Exchange any day of the week.

I never tested the server but the client (in java). May be most of the comments against Lotus is about the client.

Brony said,

I used to do service for exchange server, the service is ABSURDLY EXPENSIVE, for example, sometimes i charge the migration of account from older version $50 - $100 per account. And sometimes it is not possible without leaving the old server just sitting duck in a corner.
So, it is not rare that some business are sticking with exchange 2003.

Exchange Server is only cool for a big business (with a big pocket) and only if it uses the whole pack, including Cisco IP phones.

However, it could be worst, for example Lotus Notes.

Uhm...
2003 -> 2007
http://exchangeserverpro.com/exchange-2007-transition-guide

2007 > 2010
http://technet.microsoft.com/e.../ff805032(v=exchg.141).aspx

And from 2010 to 2013 will be similar as the 2007 > 2010 upgrade.

So why are companies staying on 2003?
No reason to charge 100 bucks per account, you're ripping people off.

Brony said,
I used to do service for exchange server, the service is ABSURDLY EXPENSIVE, for example, sometimes i charge the migration of account from older version $50 - $100 per account. And sometimes it is not possible without leaving the old server just sitting duck in a corner.
So, it is not rare that some business are sticking with exchange 2003.

Exchange Server is only cool for a big business (with a big pocket) and only if it uses the whole pack, including Cisco IP phones.

However, it could be worst, for example Lotus Notes.

Hey bud who used to service Exchange. Bud who services exchange here. Let me intro you to Office365 for those small businesses that don't need full on-prem exchange.

lkernan said,

Funny, as much as people bag Notes, the Domino email server was damn easy to maintain. I'd take it over having to fix Exchange any day of the week.

My company's big issue is that we were using a super out of date version on a freaking Windows 2000 server. (We're not a small business so we had to keep certain servers in check with Global CHQ standards, email servers were one of them. Dont get me started on how lame it was...) So it just lead to a lot of stability issues. Once we switched to a 2k3 server it stopped having as many crashes on Domnio's side. However the Outlook client is still better than the Notes client IMO. Like night and day.

Who was screaming where exactly? Here? Are you sure that "everyone" was?

All I ever saw was that this was a known iOS 6.1 bug... I never saw "everyone" screaming anything anywhere. Your post reeks of the typical hyperbole such as "Everyone says Apple products are perfect" ridiculous nonsense.

If exchange changed and that caused the problem, you could probably blame Exchange. But since iOS 6.1-6.1.1 were showing this issue, and not iOS 5.x, and no other devices (WP7/8, Android) then you can rest assured that the fix needed to come from Apple.

Shadrack said,
Who was screaming where exactly? Here? Are you sure that "everyone" was?

All I ever saw was that this was a known iOS 6.1 bug... I never saw "everyone" screaming anything anywhere. Your post reeks of the typical hyperbole such as "Everyone says Apple products are perfect" ridiculous nonsense.


Whole conversations about it on the previous post about it. Even outside Neowin it was Exchange's fault generally.

But yeah I should've added a /s or /t tag. Maybe it would be more clear.

Shadowzz said,

Whole conversations about it on the previous post about it. Even outside Neowin it was Exchange's fault generally.

But yeah I should've added a /s or /t tag. Maybe it would be more clear.

The only thing I object to in your post is your extrapolation to "everyone" when in reality it was "some folks" or most of the time "one particular person". Anyway, doesn't surprise me.

"Most folks" who talk negatively about Apple and/or their users tend to make such statements "some times" . Just realize that when you use language like that it is easy to show you are wrong.