Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yeah, not sure I want to touch 5.5 ever again and why would they not migrate straight to 2010? Meh....I'm looking in NYC anyway. :D
Ypu can't go 5.5 -> 2010 as the ADC is not supported so the only option is 5.5 -> 2003 (get rid of 5.5. servers) -> 2007/2010 -> 2013 (if you like living on the edge).

Think I heard they were going to extend SCCM functionality to cover Surface, but hadn't heard about EAS management. Will this be a true MDM?
I'm not sure of the exact details (not a SCCM guy) but I heard people talking about it at TechEd but the mobile device policies will be controlled from within SCCM rather than Exchange. The session videos are probably online if you are interested.
 
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.

iPhone configurator, Activesync policies, Good, Mobile Iron, Moxier, Touchdown... There may be more ways for IT to control an iPhone but those are the ones I'm familiar with.
 
As much as I like Apple, it seems they've never treated EAS as a priority. They screw it up almost every major release.

Which I admit I find interesting because the EAS client for iOS 4.x is one of three (yes, three) smartphone mail clients that have passed the Exchange ActiveSync (EAS) Certification Program. So you'd think if they got it right with iOS 4.x, they'd keep it right with iOS 5 and iOS 6...

Then again, Apple's not alone. Every time Microsoft releases a patch to Exchange 2010 it takes down a huge swath of Android smartphones (especially Samsung devices).
 
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.

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.

Yes. The server does what the client tells it to do. The issue might be that the client says it does have permissions or is the owner. Similar to devices that tell Activesync they support encryption when in fact they do not but are allowed to sync anyway. Too much reliance on the client side IMHO.
 
Ypu can't go 5.5 -> 2010 as the ADC is not supported so the only option is 5.5 -> 2003 (get rid of 5.5. servers) -> 2007/2010 -> 2013 (if you like living on the edge).

Well, I didn't mean it the way I said it.....I reailze you can't go direct. But I should have said continue the migration all the way to 2010.

Haven't touched E15 yet.

----------

I'm not sure of the exact details (not a SCCM guy) but I heard people talking about it at TechEd but the mobile device policies will be controlled from within SCCM rather than Exchange. The session videos are probably online if you are interested.

Thanks, I'll look them up.
 
Which I admit I find interesting because the EAS client for iOS 4.x is one of three (yes, three) smartphone mail clients that have passed the Exchange ActiveSync (EAS) Certification Program. So you'd think if they got it right with iOS 4.x, they'd keep it right with iOS 5 and iOS 6...

Having worked at Microsoft...I'm not surprised.

Edit: just noticed you're in Seattle....working for MS?
 
Anyone actually test this and verify it works?
yes, I noticed it last week.
The memo quoted here happens to be from the company I work for.
We are working to contain the problems this is already causing.
As you can imagine almost nobody in XXXXXX has a company iphone.
That's what Blackberries are for!:D


As far as "the ability to wipe a phone without permission". That is SOP. It is only used in the event of a phone being stolen or lost. We actually have the feature exposed in company webmail so a user does not have to involve helpdesk. Most phones are lost on weekends right?:rolleyes:
 
I see this as an Exchange problem. This is a privilege escalation issue. How can _I_ affect the other user's statuses? The problem might be triggered by iOS 6, but it seems to be an underlying issue with Exchange. This shouldn't be able to happen.

I think iOS is not touching Exchange directly with this bug. It is merely sending the decline email to the full distribution instead of just the sender.
 
This is where Apple really needs to develop a mechanism to allow users to enforce iOS versions as well as allow downgrades is IOS versions. Apple may not have very much market share in the corp world with the Macintosh, but it definitely does with the iPhone, and it would be nice if they would support it like a corp device.
 
I heard about this from my boss a couple weeks ago! But he said it was affecting the iphone 5 only and that it would never be fixed, so I didn't really take him seriously.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.