Just checked, and we don't have any users with delegates. We're a SMB (99 employees), so it was an easy check.![]()
27,000 here.
(About to add 50,000 more)
Just checked, and we don't have any users with delegates. We're a SMB (99 employees), so it was an easy check.![]()
Which I'm sure they will, because American business runs on Exchange.
Which is what I think is wrong with American business most times.
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).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.![]()
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.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?
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.
As much as I like Apple, it seems they've never treated EAS as a priority. They screw it up almost every major release.
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.
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).
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.
I would hope a company of these sizes would not be recommending any x.0 software updates.
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...
yes, I noticed it last week.Anyone actually test this and verify it works?
Anyone actually test this and verify it works?
OK corporations, switch to hotmail.
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.
who the hell still uses exchange Jeeps!
pls join the 21st century
it's not 1995 anymore
Having worked at Microsoft...I'm not surprised.
Edit: just noticed you're in Seattle....working for MS?
I did two years in their Cloud Computing Group supporting smartphones.![]()
Exchange seems to be an issue affecting both iOS and OS 10.8.2 -- Way too buggy.
Apple needs to crank out 6.0.1 ASAP.
wish i didnt upgrade next time i will wait![]()
who the hell still uses exchange Jeeps!
pls join the 21st century
it's not 1995 anymore
who the hell still uses exchange Jeeps!![]()