Exchange under Mountain Lion

Seems my response to the account exective worked. I have another call scheduled with the engineer tomorrow. Yes, it's taking a lot of time, but if we can get somewhere for the good of the entire mac having exchaging using community then it will be worth it.

Here's a test of the "exchange is what did it" theory. I booted from a lion clone on the same machine, same location, same settings mail worked fine. The clone was made 10 minutes before the upgrade as an emergency backup - just in case.

Same settings work fine in IOS - iPad and iPhone have no problem connecting - thank goodness.

Something was changed in ml - because it worked in earlier builds.

I had a similar, but different problem with Exchange and ML. My mail worked just fine in Mail.app, but my calendar stopped syncing about a day after installing ML. I tried deleting the account from Calendar and re-adding it, but then it just showed the account name without any actual calendars listed:

The title "Exchange" was there, but no line for "Calendar". I tried deleting the account completely and selectively (within the Calendar app), but nothing made a difference.

Then I read one of the posts that mentioned there are background processes in both Mail and Calendar and so a reboot might be needed to get the new settings to take effect. So I rebooted and things appear to now be working: as you can see above, the calendar now appears and I just verified that it is syncing to our Exchange server. We'll see whether this recurs.

- Dave

Hi All. I visited NextByte (Mac Shop) today re: my burnt out MacPro A1186 motherboard, which was a fun experience, $1500.00 AUD replacement. What a joke! Anyway, I asked about the exchange issue, and he verified with me that they'd had to change the Exchange Code (as discussed earlier in this post) in quite a few school machines to get them working as it was the only available solution. However, he did let me know that a 10.8.2 or 1, not sure, patch had been released to delelopers yesterday. So I'd say there's an update in less than a week away, his words, not mine. We can only hope. Good luck with it all everyone.

I am actually getting more and more confused. Apple sent out a message yesterday on this issue http://support.apple.com/kb/TS4363

The message states that the 'autodiscovery' resets the exchange connection to what is needed. I need to be honest here...What if autodiscovery does not do the right thing. The result is that still nothing works. Mail is not synced, calendar is not synced, mailbox sometimes fetches (old) messages. When I switch to another mail box and back to the exchange one, all messages are gone (again).

Mails that I send (not throught exchange) are only sent when closing Mail en reopen...

Apples message TS4363 actually does say that there are issues, but does not solve te problem...I want to add value so I keep on posting any work arounds or issues.

http://support.apple.com/kb/TS4363

simply says that apple returns the issue to microsoft or the exchange admins. In my eyes they will not fix the issue.

the worst case scenario will be that they also break exchange - autodiscover features in the new iOS 6 for mobile devices.

There's nothing wrong with Autodiscover or Exchange on our site. People that are on Lion or Snow Leopard have no problems at all. Those that have upgraded to Mountain Lion have. In that equation only one thing changed: Mountain Lion (and thus Mail). By issueing that article, Apple are saying there might be an issue with autodiscover settings, which could in fact be true for some sites. But they refuse to acknowledge that there might also be a majority of sites that have Autodiscover and Exchange configured correctly, like our site. In a previous post someone mentioned this behaviour did not exist in previous builds of Mountain Lion. But now it obviously does. That might keep Apple from actually believing something is wrong in the released build of Mountain Lion.

I emphasized to our Exchange admins to NOT change a single bit, not for this reason.

Auha, but this is really measured by the Lords with the apple.

If this is not really fixed I replace my entire infrastructure from ThinkPads.

The theater has been going on for over a year. Since only help I believe the consequences.

Greeting Kolobok

it's a shame for apple. since lion we have issues with exchange and they were not able to fix it. the only thing they are doing is crying like kids and blame others for there own issues und bugs.

Exchange and autodiscovery are working well, you can tell as the correct server entries appear in the internal/external server fields in the account settings.

The problem is that after the initial account setup mail defaults to the internal server address. You can see this happening from the activerty window.

It is correct the update the settings each time you run mail, this helps if admins have to make changes to the exchange system and is in fact the way it should work. However, an override would be helpful.

The problem is mail defaults to the interal sever address, which should be fine if you sit on the internal network and can access the subnet that the autodiscover settings allude to. If you operate externally or have a commercially hosted exchange service you will be unable to ever reach the internal server.

Mail is failing to recognise that you need to use the external server address which works fine. The host file edit with fix that issue but is a workaround and not a fix.

Other problems - folders and connectivity thy are being mentioned in this thread wil relate to the performance of EWS - most likely!

Hope it helps, big thanks to the community really great to see the involvement from you all!

Hi Thomas,

You are absolutely right...as this is the message 'behind' the message. But it does say 'Resolution'. So if they do not propose a resolution but merely a 'not transparant message' of 'ask microsoft' they should not have posted TS4363.

I want a real solution...

I'm already in over a year with my Exchange hosting in contact because of this tragedy.

Their setup is designed to Exchange textbook and is completely up to date

There is no guilt in this very good working hosters. The solution has brought out only Apple. And they know their business customers but ignore. This is a mistake to show what effect.

Here´s a temporary fix that works:

Open Mail.

Adjust your settings as desired in your account preferences.

Open Terminal, located in /Applications/Utilities.

Set the re-autodiscovery interval to something like 100 days by pasting or typing this command in Terminal, followed by Enter:

defaults write com.apple.mail ReautodiscoveryTimerInterval 8640000

Hi BiffqrgRwrzhwrerz,

your solution will not fix the issue that the apps are not recognizing that they should use the external server and not the internal one.

True, but it's a fix thats works! If you know your external server, it's a great and simple workaround.

😁 So, that was disappointment #~

Message was edited by: Rogier!