Be Careful of that iOS6 Update, It’ll Ruin Your Exchange Server
If you have an iPad in the Enterprise and use your iPad with an Exchange Server you might want to hold off on that 6.1 upgrade – it’ll f@ck up your environment something fierce.
Apple has made yet another massive mistake with iOS and Calendaring. When you use ActiveSync it generates huge amounts of traffic, fills the log drive and more than likely will corrupt your calendar. If you’re a user, don’t connect that device. If you’re an IT admin, you better block that device.
Apple iOS 6.1 upgrades result in excessive transaction log growth
Is iOS6.1 causing Excessive logging? Anyone Else See this?
Controlling Exchange ActiveSync device access using the Allow/Block/Quarantine list
Blocking iOS 6.1 Devices on Exchange 2010
Circular Logging, Embrace It!
Come on Apple, what the hell are you thinking? If you want to be part of the Enterprise you might want to do some testing against an Enterprise Server. People use Exchange, it’s simply a reality, perhaps a little QA is in order. You cocked this up with iOS 4.x, 5.x and now 6.x. Look a trifecta of Epic Fail when it comes to ActiveSync! With all them billions of dollars you have squirreled away you could probably afford a dev that knows how to code to the ActiveSync spec. Or maybe you could hire an MS dev. Or pay for the MS SDK. Or maybe you could just ask how to code it correctly and stop looking like a buck of @#$%ing idiots.
Other articles of interest:
- This iOS6.1 fiasco could be the kiss of death for iPad in the Enterprise
- Isn’t it Microsoft who’s playing catch up?
- Let’s settle down on the fandom
- Sometimes technology really does amaze me
- Apple will charge for the iOS4 update for the iPad?
- Why you gotta give the iPad the stink eye?
- Here comes the iPad Mini
- World travelling iPad lands safely at my door before lunch time
- Will the iPad 5 be a step toward a gaming console?
- The iPad is my mobile workstation