Menu
BYOD nightmare: iOS devices hobble Exchange servers when they synch

BYOD nightmare: iOS devices hobble Exchange servers when they synch

A problem has arisen that slows Exchange servers to a crawl when the devices try to synch

Microsoft and Apple recommend that businesses deny certain iPhones, iPads and iPods access to Calendar items until the companies can clear up a problem that slows Exchange servers to a crawl when the devices try to synch.

The problem reveals itself to end users as an error message when they try to update items with Exchange Server 2010 that says "Cannot Get Mail" and "The connection to the server failed," according to a Microsoft support notification. The only option presented to users is to choose "OK," Microsoft says.

[SIMILAR PROBLEM EARLIER: Exchange Outlook Calendaring Problems

[EXCHANGE 2013: What's new? (An early adopter's perspective)

More problematic for IT is that server CPU use jumps, affecting performance for all users. Microsoft describes the problem like this: "When a user syncs a mailbox by using an iOS 6.1-based device, Microsoft Exchange Server 2010 Client Access server (CAS) and Mailbox (MBX) server resources are consumed, log growth becomes excessive, memory and CPU use may increase significantly, and server performance is affected."

IOS 6.1 comes on iPhone 3GS, 4 and 5; fourth and fifth generation iPod Touch; iPad 2, third generation and fourth generation iPads; and iPad Mini. This makes for a major inconvenience for workers who use these devices at work primarily as a way to access emails and calendaring information.

Microsoft recommends that users facing this problem open trouble tickets with Apple to report the problem and diagnose what's causing the problem. "Apple and Microsoft are investigating this issue. We will post more information in this article when the information becomes available," Microsoft says.

The workaround is not to try accessing Calendar from the affected devices. If a user runs into the problem, rebooting the device may clear it up, Microsoft says. If not three other options might work: remove the Exchange account from the Apple device, wait half an hour and reinstall it; throttle the number of iOS devices that can access the server at the same time; and block all iOS devices from the server.

The second option will help protect server performance, but won't prevent the error messages, Microsoft says.

The support notification also advises how to detect whether the problem exists in a particular network.

Tim Greene covers Microsoft for Network World and writes the Mostly Microsoft blog. Reach him at tgreene@nww.com and follow him on Twitter https://twitter.com/#!/Tim_Greene.)

Read more about software in Network World's Software section.

Follow Us

Join the New Zealand Reseller News newsletter!

Error: Please check your email address.

Tags consumerization of ITBYODAppleNetworkingMicrosoftwirelesssoftwareIT management

Upcoming

Slideshows

In Pictures: Houston, we have a bug - 9 famous software glitches in space

In Pictures: Houston, we have a bug - 9 famous software glitches in space

There’s never a good time to run into software bugs, but some times are worse than others - like during a mission to space. Spacecraft of all shapes and sizes rely heavily on software to complete their objectives. But those missions can be quickly ended by the simplest of human errors when writing code. The omission of an overbar here or overflow error checking code there can mean the difference between success or failure, not to mention the loss of hundreds of millions of dollars, years of work and, on manned missions, human life. Use the arrows above to read about 9 examples that show that, despite the care with which these systems are built, bugs have occurred in spacecraft software since we started to fling rockets into space - and will, no doubt, continue to crop up.

In Pictures: Houston, we have a bug - 9 famous software glitches in space
Show Comments