Exchange under Mountain Lion

well mr csound, how come i have an email from apple confirming the same (in Dutch)? and why does mail fail to work properly with exchange since 10 months? Read this discussion thread and you will be shocked by our firends in Cupertino

I do not believe you,

Post the email here.

Here you go. Good luck translating. I blanked out all names for privacy reasons.

Geachte heer x,

Bijdeze de mail met gegevens:

Email programma:

http://www.mozilla.org/nl/thunderbird/

Add on voor exchange:

http://www.techrepublic.com/blog/apple-in-the-enterprise/how-to-connect-lion-to- exchange-servers/

Hopenlijk biedt dit u de gewenste oplossing.

Helaas zijn de procedures van Apple heel strikt.

Wij kunnen enkel en alleen Apple software ondersteunen.(Net als andere bedrijven zoals Microsoft bijvoorbeeld.) Dit houdt in dat wanneer het niet zou werken wij als Apple zijne u niet verder kunnen helpen.

Maar ik wil toch mijn contact gegevens aanbieden betreffende dit probleem, dat wanneer u nog een vraag heeft u mij kunt mailen naar x@apple.com onder vermelding van het zaaknummer.

Zo kunnen we altijd nog even samen kijken naar een oplossing.

Hopende u afdoende te hebben geïnformeerd,

Met vriendelijke groet,

x

Senior Advisor Apple Care

That email says that you need to contact Microsoft for Exchange technical support. It does not say that OSX does not support Exchange.

Apple do not provide tech support for Microsoft products, just as Microsoft does not provide tech support for Apple products.

Just as I said before, your information is incorrect, please stop misleading people.

It doesn't say that, it says Apple only supports Apple software. Anyway the result is the same, isn't it, exchange doesn't work on my Macbook using Apple Mail, while it works on any other device I own (Windows, iOS) and the recommended solution by Apple Care, Thunderbird, guess what: it works too on my Macbook. So where is the problem.

benveen wrote:

It doesn't say that, it says Apple only supports Apple software. Anyway the result is the same, isn't it, exchange doesn't work on my Macbook using Apple Mail, while it works on any other device I own (Windows, iOS) and the recommended solution by Apple Care, Thunderbird, guess what: it works too on my Macbook. So where is the problem.

Believe as you please, I have an office full of users with iMacs, Mountain Lion, Mail and MS Exchange, are we all dreaming.?

Expect to be challenged whenever you post such erroneous and misleading information.

The fact that you can not get it to work on your Mac is your failing, not a general failing. If you dropped the attitude you might be able to get a solution to what is not an uncommon issue.

But it will have to come from someone else, or just take a look at the 'More Like This' section.

Well, we solved all the issues installing Exchange SP3 and Rollup 1

It does a horrible job of it.

I know, it is the world that works like microsoft

We have thousands of employees all using MS Exchange. A small percentage of our employees (roughly 5,000) are Mac users. The Mac users that are trying to use Exchange 2007 with Mail.app, Calendar.app and Contacts.app (Mac OS X 10.7 to 10.8) are suffering a number of crippling issues. Mail constantly PWODs (PinWheelOfDeath), seemingly if you just look at it the wrong way. The condition I find most ironic is Mail trying to verify services that cannot possibly be reached when not in the private IP address range of the corproate intranet.(for those not familar, if the Mac has no interface on 10.x.x.x, Mail still checks (and shouldn't) for servers and services on 10.x.x.x which is a non-routeable network address range)

Then there is the Calendar which, once it gets into a mode of error, cannot be recovered without data loss. Case in point, once you get this message below, your local calendar setup is toast and you have little recorse but to delete all of your local calendar data and start over:

Then there is Contacts which cannot accurately search Active Directory for names, returning fewer results than the Microsoft Windows Outlook address book for the same search.

If you want some real fun, bind a Mac OS X Server from 10.4 to at least 10.6.8 to Microsoft Active Directory. Watch DirectoryService in Activity Monitor. At some point, maybe hours maybe months later, you will see Directory Service start to consume vast amounts of CPU resources eventually crippling an 8 processor MacPro. I am dealing with that right at this very moment on a tiny MS Active Directory system handling only 700 (and change) user objects.

While Apple states that they are compatible with MS Exchange/MS Active Directory, the fact of the matter is that they are not. Simple searches across the internet for probelm lists like this reveal that you are lucky to have it working in small enviroments and that is about it. Changes are coming and it is getting better but ...

The only reliable work around at this point is to use the OpenSource DavMail which has much greater MS Exchange compatiblility than Apple has ever mustered. Were I Apple, I would be embarrased enought to hire the DavMail folks and find something else for the Apple MS Exchange compatibility programmers to do :-\

Apple does a lot of things "insanely great" but MS compatiblity, on any level, is not one of them. Abort, Retry, Fail

http://davmail.sourceforge.net

I do not think it is appropriate to judge the world rather than the worlds microsoft mac, I can only confirm that both platforms have worked together with no problem, everything is created by installing the servicepack2 of exchange, then the mac stopped working, then ip, routing, and the other has not changed, we performed 3 upgrade service packs added rollup and everything started to work again. To understand what's inside the rollup requires that Microsoft knows only the engineers microsoft

I too am having trouble on a new MacBook Pro running 10.8.4 connecting to Exchange.

I am using a university-owned MacBook. When I'm at work, everything works great.

However, at home, my Safari works great (so my network is functional); however, it takes 10 min for MacMail to sync with my Exchange mail. Oddly enough, it takes the same amount of time for iCal to work with iCloud.

Once it works, I'm good until the computer sleeps. Then I'm 10 minutes out again.

I am wondering if it has something to do with the way I am forced to log in to the computer. I have suspicions that IT dept is using Exchange to host my computer login credentials...

Any thoughts?

Thanks,

Dan

ps- I'd have to say, this is the WORST OS and the WORST Mac I've ever had. I am reluctant to give up my trusty 2008 MacBook Pro.

This sounds like it could be a problem with the server configuration. There are so many posts that this tip might have been overlooked:

Tip 11 from 21 March:

Refer your Exchange server administrator to http://premnair.wordpress.com/2010/07/03/configure-ews-autodiscover-owa-oab-ecp- on-exchange-server-2010/

If any user has tried this please post your outcome (fixed or not)

Excllent info, thanks for the repost.

In our case we have 100's of thousands of working users and the Mac's are the only ones having the issues.

One issue just uncovered was a broken up repeating event that was causing this sort of dialog which appears over and over and over.

So the solution looked to be to go into MS Outlook on Windows and delete the events that cause this. Mind you, this event does not present a challenge to MS Outlook on Mac, MS Outlook Web Access, MS Outlook on Windows, BlackBerry Enterprise Server, Good Enterprise Server. Can only conclude that if it works everywhere else, must be Mac problem. We have rougly 5% Mac users with barely any of them using Apple Mail / Calendar / Contacts. It makes it much easier for our IT people to convince them out of Mac and go back to Windows which happens as there is no intrinsic benefit to the MS Office user to use Mac. Expanding the user's horizion with great interfaces and functionality in Apple Mail / Calendar / Contacts takes them out of MS jail into a brand new exicting world. Bugs like this ... well, not so much. :-(