Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Fortune 500 Company Urging Employees Not to Upgrade to iOS 6 Over Exchange Bug
- Thread starter MacRumors
- Start date
- Sort by reaction score
Then don't connect your personal device to your company's mail servers.
----------
Second thing I saw this morning was a cancelled meeting. I loudly said "I love cancelled meetings" and got several chuckles from nearby cubes.
Nothing to do with Microsoft exchange or iphone.
An Admin can delete you from a corporate network with one click.... for all your devices.
And given they should only allow corporate phones on their network, if not your device, and they need the ability to remote whipe a device if its lost. And of the day it not your device or data, its that of the corporation.
Its not BS, its IT/data security device is not an issue.
I'm just saying I'd like to know which large company sent out that memo to all of their employees.
https://forums.macrumors.com/posts/15953005/
Last edited:
Ask yourself why you need a username and password to login into your work machine. Its data security, and it seems your company cares about it.
So one person declining a meeting cancels the entire meeting? How can anyone who didn't create the meeting, cancel it?
This sounds like something that exchange should not ever allowed to happen.
----------
I would test it out first.
This sounds like something that exchange should not ever allowed to happen.
----------
I would test it out first.
Exactly. Even if the client has a bug that is sending some sort of a "delete meeting" message, the back-end server should never honor that for a meeting that was created by someone else.
It sounds to me like a classic case of relying too much on validation happening on the client side and not enough on the server side.
Well said!!
As the manager of Messaging team here in NA for more than 350k mailboxes, I have to say you nailed it. If my team had free time to worry about wiping peoples devices, I would make them L1/L2 support.
Furthermore, if OWA is deployed properly, the end user can wipe their own devices if they needed to.
FWIW - as much as I despise Blackberry, it has presented itself as a much more stable mobile platform than Apples deployment of Activesync. Multiple iOS's have had issues, so it's no surprise that iOS 6 has them too. What makes matters worse is that BYOT is becoming more prevalent, making my teams job that much harder to deal with.
As the manager of Messaging team here in NA for more than 350k mailboxes, I have to say you nailed it. If my team had free time to worry about wiping peoples devices, I would make them L1/L2 support.
Furthermore, if OWA is deployed properly, the end user can wipe their own devices if they needed to.
FWIW - as much as I despise Blackberry, it has presented itself as a much more stable mobile platform than Apples deployment of Activesync. Multiple iOS's have had issues, so it's no surprise that iOS 6 has them too. What makes matters worse is that BYOT is becoming more prevalent, making my teams job that much harder to deal with.
There's a new Microsoft cloud based solution for managing "unmanaged" devices coming along that may make this a bit easier.
With as many bugs as they're finding, may as well just wait for the 6.1 update
iOS devices are different from PCs, in that iOS devices are "personal" and corporate IT can't really control them. All IT really can do is try to slow users down. I know--I work in a Fortune 200 company that still has us on Windows XP, but only put a 72 hour hold recommendation on iOS 6.0--because that's about all users would stand for.
What makes you think the IT guy couldn't have the iCloud passwords for a company-owned iPhone?
There is absolutely no reason they couldn't do it with iCloud just the same as with Exchange.
Stupid forum timeouts eating my detailed reply. So now you get the short version.
In fact, I can confirm that this exact same behavior can be reproduced in an all-MS IT infrastructure. We've started seeing this problem the last couple weeks here, and it seems to stem from interactions between Exchange Server 2003 and Exchange Server 2010 [everyone is on Outlook 2010, but we're in the middle of a server migration, so some people are still on the older servers].
I personally confirmed that the person who declined did so on her computer (not on a smartphone), and according to the IT dept, her account is on Exchange 2003, while the other affected parties that I checked on are on Exchange 2010. (I didn't check every single one of over a 100 included people.)
Outlook/iOS/Exchange Server problems also aren't new with iOS 6. We've had a standing corporate policy not to interact with meetings via iOS for as long as it has existed--it just used to only screw up the calendar of the person who did it, not others.
If we can't be rid of Outlook, I wish MS and/or Apple could sort out these problems. Given that, according to MS, Exchange Server can't reliably manage recurring meetings with more than about 13 recurrences, I'm inclined to suspect that it's MS at fault here, but I won't be at all surprised to find out it's Apple or both of them.
(In researching the pre-iOS6 problems, I found more than one person who claimed to have traced the problems to a bug in how Exchange Server 2003 implemented the ActiveSync/Exchange protocol. They said that the bug was still there in 2007, but fixed with Exchange Server 2010.)
In fact, I can confirm that this exact same behavior can be reproduced in an all-MS IT infrastructure. We've started seeing this problem the last couple weeks here, and it seems to stem from interactions between Exchange Server 2003 and Exchange Server 2010 [everyone is on Outlook 2010, but we're in the middle of a server migration, so some people are still on the older servers].
I personally confirmed that the person who declined did so on her computer (not on a smartphone), and according to the IT dept, her account is on Exchange 2003, while the other affected parties that I checked on are on Exchange 2010. (I didn't check every single one of over a 100 included people.)
Outlook/iOS/Exchange Server problems also aren't new with iOS 6. We've had a standing corporate policy not to interact with meetings via iOS for as long as it has existed--it just used to only screw up the calendar of the person who did it, not others.
If we can't be rid of Outlook, I wish MS and/or Apple could sort out these problems. Given that, according to MS, Exchange Server can't reliably manage recurring meetings with more than about 13 recurrences, I'm inclined to suspect that it's MS at fault here, but I won't be at all surprised to find out it's Apple or both of them.
(In researching the pre-iOS6 problems, I found more than one person who claimed to have traced the problems to a bug in how Exchange Server 2003 implemented the ActiveSync/Exchange protocol. They said that the bug was still there in 2007, but fixed with Exchange Server 2010.)
Seems to be related to users with Delgates
I work for a major company that is privately owned (if you travel or wrecked your car recently you've heard of us) but would probably be a Fortune 500 company if it was public. Long story short they sounded the alarm on this one ahead of the release... Being the rebellious spirit that i am I upgraded anyway. After a 4-day quarantine they discovered that it only occurs (at least on our setup) when an user has a delegate set up. They have since re-enabled access to those of us without a delegate.
I work for a major company that is privately owned (if you travel or wrecked your car recently you've heard of us) but would probably be a Fortune 500 company if it was public. Long story short they sounded the alarm on this one ahead of the release... Being the rebellious spirit that i am I upgraded anyway. After a 4-day quarantine they discovered that it only occurs (at least on our setup) when an user has a delegate set up. They have since re-enabled access to those of us without a delegate.
MS's enterprise support, when we were having problems with long-recurring meetings getting corrupted, said that this was a known problem, and recommended that we keep all recurring meetings to 13 or fewer occurrences to avoid the problem. This was a known problem as of Outlook/Exchange 2003, and is still considered a limitation in Outlook/Exchange 2010, according to MS enterprise support. If they can't "implement properly", who can?
Anyway, for syncing and versatility, Google Calendars has Outlook/Exchange beat, without even trying. But, you're right, nowhere near the level of control. I work in healthcare, so the level of control is probably actually needed--but in lots of other instances, I think it's a poor choice (giving up the functionality for security/control, I mean).
Well, then they'll have to fix it.
Which I'm sure they will, because American business runs on Exchange.
Which is what I think is wrong with American business most times.
Which I'm sure they will, because American business runs on Exchange.
Which is what I think is wrong with American business most times.
I would really like to disagree, and say it was a great new version of iOS, but it's not.
No way.
I'm really tired of so many issues, and so much negativity from Apple. Yet I will do what I always do, remain loyal.
As a serious enthusiast, I used to truly enjoy being able to speak highly of Apple.
My APPL stock alone has put me in a very strong position. Due to it's astronomical increase in value since I began investing in 1991, all my Apple purchases are now as good as free. With reserves beyond my wildest dreams. I would have never imagined anything like it.