Exchange under Mountain Lion

Correct. The option for Push exists for iCloud but not Exchange (MacBook Pro, Calendar v6.0, OS X v10.8.2). However, you can set exchange to Push every 1 min.

I manage an Exchange 2007 and I have been having this issue for over a month. It was effecting all of the Mac Computers that we support. The good news I was able to fix it last night after reading about a similar problem with Blackberry phones. Unfortunately, you will need to either be the Exchange admin or have influence in your IT Department.

On the Exchange server the Performance Counters need to be verified and it is found in the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Perflib\009

When you viewing the key in explorer mode I found that it was basically blank. It should read like the following:

1 1847 2 System 4 Memory 6 % Processor Time...

If its blank it corrupted.

Supposidly this was caused by the update to Service Pack 2 upgrade... However, I did that a 6 + months ago. The only change since then was that the server was virtualized to VMware.

Here is what you do to fix this:

(Note: This was done on a Windows 2008 R2 Sever... However, it should work on 2003 and 2008 as well)

1. Launch the Windows Command Prompt (cmd), ensure that you run the Command Prompt as the Administrator. For example, click Start, click All Programs, click Accessories, right click Command Prompt and click Run As Administrator.
2. Change Directory to <root drive>\Windows\System32, the root drive is typically C:. Run the following command
   lodctr /R
   This will restore the base or core counters
3. Check the registry value under HKLM/Software/Microsoft/WindowsNT/CurrentVersion/Perflib/009and ensure that the value Counter is no longer corrupted.
4. In the Command Prompt window, run the following command:
   wmiadap /f
   This will force the reload of all counters in to the WMI repository.
5. Open Performance Monitor (perfmon.exe) and click the green + to Add,this will open Add Counters. Verify that the MSExchange counters exist and have Instances populated.
6. Restart the Microsoft Exchange Server computer.
   NOTE: This step is required.

Hope this helps someone!

Guys, does mail connect to exchange server without security certificate? I cant get mail to connect to my exchange server no matter what I do!

htabbach wrote:

Guys, does mail connect to exchange server without security certificate? I cant get mail to connect to my exchange server no matter what I do!

That depends on how the Exchange is set up, if certificates are required, or not.

I have no problem connecting from my iphone, we do not require SSL, in fact, on my iphone i configured mail to not use SSL but do not know how to do that on my MBA, i just bought the MBA yesterday and it is my first ever MAC but it looks like it is going back today, I must be able to connect to my work exchange.

System Preferences>Mail, Contacts and Calendars. Enter it there.

I give up. I've tried a awful lot of the suggestions listed in this post with no joy. (I've wiped out the OS and reinstalled to try to get it to work!) It seems that my exchange server just took to hating my ML MBP. It's strange because numerous other ML machines in our shop are perfectly happy.

I'm utterly dismayed at the lack of ANY tooling to diagnose what isn't working with Mail talking to Exchange. That is the part that I find completely and utterly unexcuasable. Seriously, I would think by now *EVERY* tech company, Apple too, would have learned to leave the diagnostics tools in place.

Thing is, I can't continue. Email is the lifeblood of my job. I'm going to go back to trying to get Thunderbird to talk to my Exchange server, but if that doesn't work out - I will have to change platforms.

It's sad really - my older MBP with an older Mac OS release, Apple Mail still works fine there talking to the Exchange server.

Thunderbird *****, but at least I already have Thunderbird talking IMAP to the Exchange server and getting email - which is more than I can say for Apple Mail.

I feel your pain.. I'm have no idea what changed but as soon as I upgraded to ML my connection to Exchange quit working. I was able to get it working for a short time with the host entry but then that started failing and nothing else worked. Since the company I work for doesn't support Mac I gave up. Two weeks ago the company upgraded the Exchange servers to 2010 and I am back in business again. I only unchecked the autodiscovery box and changed the address to what I knew worked and i'm back in business.

I'm telling you this because it might be a issue with your server that you will not be able to fix.

I'm roughly in the same situation. Mac isn't supported and we unfortunately are running some hybrid of both exchange 2010 and 2007(?) maybe. One front end, a different back end during migration.

My rough thinking is that, in my case, there is an error in TLS negotiation - but with the amazing error reporting, how would anyone know.

Under Mountain Lion, have found that deleting the individual accounts under the applications and then recreating said accounts under the applications does not alleviate the issue.

Have found that the issue seems to be fixed when I delete the account under the application and then go to System Preferences -> Mail, Contacts and Calendars and create the account there. This injects the account into the application and then the application does not misbehave as much. (key: as much)

For example, I did this with Calendar connecting to Exchange 2007. With no change to the Exchange 2007 server, Calendar started becoming more reliable when connecting to the server. Retries on connections actually started to work. Still dont' know why the Exchange calendar in the list of calendars jumps up from the bottom to the top and back to the bottom but at least the calendar can now work against the server almost as well as it did in Lion.

Mail still stinks but crashes less.

Contacts has not been an issue through out the trials and mostly tribulations with Mail and Calendar.

Next question, where do we send our bill to Apple for the time spend doing their Q&amp;A? :->

Cerniuk wrote:

Under Mountain Lion, have found that deleting the individual accounts under the applications and then recreating said accounts under the applications does not alleviate the issue.

Have found that the issue seems to be fixed when I delete the account under the application and then go to System Preferences -> Mail, Contacts and Calendars and create the account there. This injects the account into the application and then the application does not misbehave as much. (key: as much)

That is the correct procedure (as Apple state), well done for finally doing it the recommended way.

Cerniuk wrote:

Next question, where do we send our bill to Apple for the time spend doing their Q&amp;A? :->

😁😁😁

I managed to get Exchange + Mail on OS X 10.8.2 working by doing the following:

1. changed username to DOMAIN\USERNAME format
2. removed all entries in the login keychain that were not in the above format
3. i tried to uncheck auto-discover but it reenabled itself automatically....things are still working for me regardless
4. saved the account config in Mail preferences
5. restarted mail

I believe 1 and 2 are the key points.

bpossolo,

Do you have more than one exchange account setup in Mail? I ask, because the issues seem to get magniffied when you have multiple exchange accounts setup.

Rich364 wrote:

bpossolo,

Do you have more than one exchange account setup in Mail? I ask, because the issues seem to get magniffied when you have multiple exchange accounts setup.

There are problems whn using multiple Exchange accounts, not just in Mail either, they can appear in Outlook as well. In Windows Outlook 2010 and 2013 support multiple accounts well, 2007 and earlier (especially earlier) do not.