Fortune 500 Company Urging Employees Not to Upgrade to iOS 6 Over Exchange Bug

[nefan65]

Dude... the point you're missing here is:

Yes it works for you, but it doesn't for many others.

THAT MEANS IT'S BUGGY AS HELL.

Imagine you buy a car and it drives fine for your wife, but whenever you drive it something doesn't seem right. Are you going to put up with that? I don't think so.

Why is it only with apple products, people seem to think everything is justified. "Give it time"? Pfft.

It should never have been released in the first place.
There's no excuse. The list of problems with iOS6 grows by the day.

.

Dude...I think you're missing the point. It does work for me, and a lot of others.

Bad analogy about the car...wow...

If it's that bad, go to something else.

----------

Apple released a beta version of iOS 6. Apple management is way out of their league now. SJ would have had management raked over the coals for the screwups with iOS 6. And, he would have used iOS 6 himself and found all the bugs before it went out.

Management at apple today must only look at their paychecks, stock options.

Bugs within Exchange existed long before iOS 6, and with non-Apple products. Again, massive generalization. "If I have this issue, EVERYONE has it". We run Exchange 2010 in-house, with a number of iPhone users [w/ iOS 6]. We have yet to run into this, and we have tested it.

 

[pondosinatra]

It really makes you wonder if Apple even bothers testing these things before releasing them to the public.

That said someone mentioned the problem is delegates. And delegates have been a PITA ever since Outlook first came out...

 

[aliensporebomb]

Thoughts

We have been using IOS since 3 I think here. I'm on IOS6 but typically just accept the meetings I get, I've never had to decline or put off a meeting on my phone as yet.

We are running Exchange 2003, multiple servers, multiple domains, thousands and thousands of users across the United States. We're not replacing 2003 until Q1 2013 for budgetary reasons I imagine.

We also are using BES, were using Good (I think the last Good user on a Treo
shutdown earlier this year when they got an iPhone) and EAS for iPhone, Android and Windows Phones.

Honestly, it's the Android users who have had the biggest problems - dropping off the server, not getting email, sending out multiple copies of single emails for no reason. Up until I heard of this the iPhone was the least painful phone out there since it would stay connected to the server and send and receive email.

These two new problems could change that. They definetely need a .1 release or corporate america could turn on these things and we don't want that.

Nobody really wants to go back to their blackberries. Speaking of phones: our company makes us buy them and be responsible for their bills yet they are used for work. We do get some reimbursement. Gotta love corporate america.

 

[nd4ever]

Not a Microsoft bug...

This is not an Exchange bug but rather a result of they way Apple developed EAS on the iPhone. EAS is licensed by Microsoft to Apple to develop on their phones.

And this in not a problem with just iOS 6. It happens in previous versions as well.

 

[Geckotek]

We can't reproduce, Exchange 2007 SP3.

Did anybody actually get this bug at all? The thread is too full of people jumping the gun and trolling Apple to know.

Yes, we've seen it at my company. My post confirming it was just 2 above yours......

 

[lwapps]

And yet another reason not to upgrade.

----------

It really makes you wonder if Apple even bothers testing these things before releasing them to the public.

That said someone mentioned the problem is delegates. And delegates have been a PITA ever since Outlook first came out...

They beta test to developers!!

 

[zama36]

If you hook up your private phone to your companies then its your problem and not the admins. If they do that to your work phone, then again, not your issue.

You clearly never worked for a corporate.

If you never used a IT solution that doesn't enforce its own protocols then you clearly never used a Microsoft product.

Granted Apple screwed up the coding, but Microsoft products shouldn't be allowing actions that contradict Microsoft protocols.

 

[Geckotek]

If you never used a IT solution that doesn't enforce its own protocols then you clearly never used a Microsoft product.

Granted Apple screwed up the coding, but Microsoft products shouldn't be allowing actions that contradict Microsoft protocols.

After some research on the issue, it's not the original meeting that's being edited. These devices are actually sending cancellations to the other attendees and cancelling the copy of the meeting in their calendar. If you know anything about how messages are stored in Exchange and how the ACLs work, then you'd realize this isn't really a break down on the Exchange side, it's just how the calendaring works (calendar items are actually just a specially formed message in another folder within your mailbox).

So while I'm quick to blame MS where they deserve it, I don't think that's the case here. It's just a limitation in how calendar items are stored in each meeting attendee's inbox.

 

[mac-1980]

Its not a Exchange bug

The title of the article is wrong, its IOS bug and not a Exchange bug

 

[zama36]

After some research on the issue, it's not the original meeting that's being edited. These devices are actually sending cancellations to the other attendees and cancelling the copy of the meeting in their calendar. If you know anything about how messages are stored in Exchange and how the ACLs work, then you'd realize this isn't really a break down on the Exchange side, it's just how the calendaring works (calendar items are actually just a specially formed message in another folder within your mailbox).

So while I'm quick to blame MS where they deserve it, I don't think that's the case here. It's just a limitation in how calendar items are stored in each meeting attendee's inbox.

So that was my point. Apple screwed up the coding and in turn the messages being sent, but Exchange isn't enforcing the protocol since the messages are getting past the Access Control Lists (ACLs) on the Exchange server.

Essentially any Exchange client can screw up one of the primary functions of Exchange because Exchange server doesn't have a method in place to enforce the protocol. Seems like it would be in MS's best interest to fix it since it's affecting not just iOS device owners.

 

[Geckotek]

So that was my point. Apple screwed up the coding and in turn the messages being sent, but Exchange isn't enforcing the protocol since the messages are getting past the Access Control Lists (ACLs) on the Exchange server.

Essentially any Exchange client can screw up one of the primary functions of Exchange because Exchange server doesn't have a method in place to enforce the protocol. Seems like it would be in MS's best interest to fix it since it's affecting not just iOS device owners.

No, the protocol doesn't control the editing of the meetings in the destination folder, only the originators folder. There is nothing incorrect about the way the protocol is being enforced.

Trust me when I tell you that Exchange DOES in fact enforce its protocols and ACLs the way they were written. I have specific experience on the subject.

Edit: The problem here is that a rejection of the meeting should only go to the originator, not the other recipients. But since the meeting rejection is a message like any other, the protocol cannot prevent the sender from sending messages to other recipients, it's up to the client to perform the task as intended.

 

[jtara]

Originally Posted by jtara
IMAP has no provision for push. You get instant notifications on your desktop email client only because your client is constantly connected to the server.

Actually It does.

http://en.wikipedia.org/wiki/IMAP_IDLE

OK, I didn't state that quite accurately.

IMAP does have provisisons for push. But it is not usable on iOS. It depends on having a constant socket connection from the client to the server. Your desktop email client can do this. The iOS mail client doesn't.

Apple made a decision (and a right one, I think) quite some time ago that they would not permit apps to do arbitrary background processing. Instead, they provide system services for common background-processing and background-notification scenarios, so that it can be efficiently done in a central place in the OS.

(Certain classes of apps are able to do true background processing. For example, audio players. But they have to actually be audio players. Apple long ago started shooting-down apps that played a silent audio in order to skirt the restriction.)

You can only get push email in iOS if the server is able to send push notifications to the Apple push service, AND if the iOS mail client knows what to do with the push.

Exchange has the ability to do this, and the iOS email client knows how to deal with Exchange push messages.

 

[DeepIn2U]

Notify link uses exchange service on the iPhone. At work we use GroupWise. The only way to get email on an iphone is thru a third party software like Notify Link. Notify Link uses the exchange services to communicate with the GroupWise post offices. Notify Link does not support the latest iOS for 30 days.

Then that is an issue with your 3rd party software - since GroupWise does NOT support ActiveSync in the first place.

----------

[/COLOR]

Yeah, it's called Good.

Good Technologies is not the only solution; many reviewed and recommended by Gartner support sandboxing of corporate information: over 20 really. It all depends on your global environment as some locations its not feasible to install servers or the heartbeat talking back to the service is too high and latency could cause issues: I'm talking about locations where satellite and mesh is in use for an office; really rural locations like Magadan or Kupol, etc.

 

[Geckotek]

Good Technologies is not the only solution; many reviewed and recommended by Gartner support sandboxing of corporate information: over 20 really. It all depends on your global environment as some locations its not feasible to install servers or the heartbeat talking back to the service is too high and latency could cause issues: I'm talking about locations where satellite and mesh is in use for an office; really rural locations like Magadan or Kupol, etc.

Yeah, I know this...just listing one of the more well known options as an example.

 

[pragmatous]

the bug also affects the 3rd party software

Then that is an issue with your 3rd party software - since GroupWise does NOT support ActiveSync in the first place.

----------



Good Technologies is not the only solution; many reviewed and recommended by Gartner support sandboxing of corporate information: over 20 really. It all depends on your global environment as some locations its not feasible to install servers or the heartbeat talking back to the service is too high and latency could cause issues: I'm talking about locations where satellite and mesh is in use for an office; really rural locations like Magadan or Kupol, etc.

 

[DeepIn2U]

the bug also affects the 3rd party software

Do you have an example that affects first party software: Apple's Mail & MS Outlook or IBM's Lotus Notes/(server) ??

 

[pragmatous]

What are you talking about? The bug has to do with the iphones exchange service on the device itself.

I work for the company and have seen the problem first hand. People have upgraded to iOS 6 after telling them not to and they have problems communicating with the groupwise email serve. They were experiencing the same exact issues this article talks about.

Enough is said about it. iOS 6 is the worst upgrade to ever reach the market. Steve Jobs would have never released such a piece of crap in the market.

There is another bug where after you update to iOS 6 all the contacts are gone and you can't restore from itune. Says database is corrupted. You have to do some ridiculous hack to get it to work.

If you haven't noticed I work in the IT department. Oh ya iOS 6 is awful. Especially when upgrading from iOS 5 to 6. So many problems and so many phone calls.

Do you have an example that affects first party software: Apple's Mail & MS Outlook or IBM's Lotus Notes/(server) ??

 

[Geckotek]

What are you talking about? The bug has to do with the iphones exchange service on the device itself.

I work for the company and have seen the problem first hand. People have upgraded to iOS 6 after telling them not to and they have problems communicating with the groupwise email serve. They were experiencing the same exact issues this article talks about.

Does Groupwise use EAS?


OMG, he said "Steve Jobs would never..." Sorry, don't bother with a reply. Can't take you serious after that crap. iOS 6 is no wore than any previous release. Almost every single release has jacked up EAS in some way. Almost always related to and ling meetings.

If what you say about iOS 6 is true, why am I not hearing more complaints from the 80% of our 1,700 iPhone users that have already upgraded?

Oh, and 175 iPhone 5s on the server in 2 weeks. Faster than I expected.

oh yeah, I work in IT as well...supporting a real mail server.

 

[pragmatous]

It doesn't matter companies have decided. Nothing you can do about it. Stop being a control freak.

Probably because the 80% of your 1700 iphone users aren't upgrading to ios 6.

Does Groupwise use EAS?


OMG, he said "Steve Jobs would never..." Sorry, don't bother with a reply. Can't take you serious after that crap. iOS 6 is no wore than any previous release. Almost every single release has jacked up EAS in some way. Almost always related to and ling meetings.

If what you say about iOS 6 is true, why am I not hearing more complaints from the 80% of our 1,700 iPhone users that have already upgraded?

 

[Geckotek]

It doesn't matter companies have decided. Nothing you can do about it. Stop being a control freak.

Probably because the 80% of your 1700 iphone users aren't upgrading to ios 6.

Apparently you didn't read my post. We pulled a report this week due to the meeting issue. 80% are on iOS 6.

Nt sure what your talking about re: companies decisions and control freaks.

Do you plan to answer my original question re: Groupwise and EAS?

 

[pragmatous]

Because this argument is retarded. It's so retarded I have doubts you or palm or pron whatever his tag name is even have 1700 iphones users and I have my doubts you both work for a fortune 500 company. No one in IT would waste their time unless you're like me who's browsing mac forums because it helps time fly by waiting for my iPhone to deliver on Oct 19th.

Apparently you didn't read my post. We pulled a report this week due to the meeting issue. 80% are on iOS 6.

Nt sure what your talking about re: companies decisions and control freaks.

Do you plan to answer my original question re: Groupwise and EAS?

 

[Geckotek]

Because this argument is retarded. It's so retarded I have doubts you or palm or pron whatever his tag name is even have 1700 iphones users and I have my doubts you both work for a fortune 500 company. No one in IT would waste their time unless you're like me who's browsing mac forums because it helps time fly by waiting for my iPhone to deliver on Oct 19th.

Doubt it or not, it's true. In fact, my company was Fortune 100 but I believe we dropped in that ranking (confirmed, we are in the 100+ range). We have 27,000 mailboxes and about to roll out another 50,000. Need to see my resume? How about I describe my job at Microsoft in Dallas (Las Colinas actually) supporting Exchange. I was on the XADM team in PSS. I was one of the first guys in the building to carry an iPhone because A) I was a contractor so didn't give a **** and B) WinMo 6.5 sucked.

I browse these forums because I have used/owned iPhones since the 3GS. So I don't feel it's a waste of time. It's informative and entertaining.

What's your excuse?

By the way, I never argued with you, I asked you a question that you have continued to ignore and I also stated you were wrong for implying iOS 6 is any worse than any previous release. Steve Jobs has already released plenty of buggy versions before his passing.

Edit: CRAP! I don't know what I was thinking. That 1700 number was only a certain model (I think the 4s). We actually have just over 4400 iOS devices connecting to the server in the months of August and September. Sorry for the misleading claim of 1700. It's late and I wasn't thinking.

 

[DeepIn2U]

What are you talking about? The bug has to do with the iphones exchange service on the device itself.

I work for the company and have seen the problem first hand. People have upgraded to iOS 6 after telling them not to and they have problems communicating with the groupwise email serve. They were experiencing the same exact issues this article talks about.

Enough is said about it. iOS 6 is the worst upgrade to ever reach the market. Steve Jobs would have never released such a piece of crap in the market.

There is another bug where after you update to iOS 6 all the contacts are gone and you can't restore from itune. Says database is corrupted. You have to do some ridiculous hack to get it to work.

If you haven't noticed I work in the IT department. Oh ya iOS 6 is awful. Especially when upgrading from iOS 5 to 6. So many problems and so many phone calls.

Sorry ... I know what I'm talking about.

Prior to our DB migration and thereafter Exchange Server 2010 with latest udpates, Outlook 2010 again latest updates, iPhone 6 Beta2 to the current GM and official release ... 24 iPhone 4S, iPhone 4 or iPad 2's or 3s at corporate office, and another 435 iPhone 4S's or iPhone 5s and NOT ONE SINGLE PERSON affected! We also use AirWatch for the 24 units at corporate. Again nobody affected.

Take a look at your environment first before blaming a third party!

EDIT: GroupWise did NOT support ActiveSync NATIVELY until GroupWise 2012 (that last remaining enterprise server to do so: http://www.novell.com/products/groupwise/features/mobile-email-sync.html). Are you on GroupWise 2012 or using a third party implementation on older GroupWise to enable ActiveSync?

You may work for a company that witnessed it first hand; I'm in IT (albiet lower level with Exchange Server access) and have yet to see it at the company I work for. I provision accounts directly and have yet to see this.

EDIT two: For Christ's sake stop using such dribble as "Steve Jobs would have never released such a piece of crap in the market." Let the man rest in peace already.
Some products he allowed released as CRAP in the market:
PowerMac G4 Cube (Acryllic cracks and bubbles)
PowerBooks upside down logo's until Titanium.
Promising 3Ghz G5s' which never delivered 1yr before realizing tech was not yet there to deliver.
.Mac & MobileMe (jokes before iCloud delivered on what those promised; and their still paying for it: delivering more storage to those that have been migrated)

Shall I go on?!

 

[DeepIn2U]

Because this argument is retarded. It's so retarded I have doubts you or palm or pron whatever his tag name is even have 1700 iphones users and I have my doubts you both work for a fortune 500 company. No one in IT would waste their time unless you're like me who's browsing mac forums because it helps time fly by waiting for my iPhone to deliver on Oct 19th.

I'm Prom1 and I never claimed 1700 users as Geckotek just corrected. No its not a waste of time since I work for IT at the corporate headquarters of a Gold Mining corporation here in Toronto ... There are 3 big ones and I work for one ... take your guess! I support not just corporate end users but also our executives amongst 5 other of my colleagues for 300 users, another 25 remote dedicated at our office, another 42 for Vancouver split between another IT team in the USA and another 4000+ users in tandem with regional IT support teams 24/7. Related to Exchange/iOS6 (any version beta inclusive)/iPhone 4 or 4S/iPad 2 or 3 ... we're NOT affected.

 

[z-paulb]

Well you can actually work around the IOS6 bug by feeding some additional info to the IOS6 device as the open source server-side implementation of active-sync called Z-push has found the cause and how Apple should fix it:

http://www.zarafa.com/blog/post/201...-open-source-activesync-implementation-z-push