Exchange 2013 Outlook For Mac

Posted : admin On 1/31/2022

Exchange Server 2013 supports the following minimum versions of Microsoft Outlook and Microsoft Entourage for Mac:

  • Outlook 2013 (15.0.4420.1017)
  • Outlook 2010 Service Pack 1 with the Outlook 2010 November 2012 update (14.0.6126.5000).
  • Outlook 2007 Service Pack 3 with the Outlook 2007 November 2012 update (12.0.6665.5000).
  • Entourage 2008 for Mac, Web Services Edition
  • Outlook for Mac 2011

Although these are the minimum versions please also take into consideration this important note from Microsoft:

Exchange 2013 Outlook For Mac

Open Outlook 2016 on your Mac. If you are setting up your first mailbox, there are some initial Welcome screens to navigate through. During these you can choose a colour theme for Outlook. We have selected the default 'Colorful'. Outlook 2016 will now load. Select Accounts. Select Exchange. For Mac (OS) If you’re using a Mac, you have nothing to worry about. After all, the concept of setting up auto-forwarding is the same in.

The information above provides the minimum versions required for a client to connect to Exchange and Exchange Online. We strongly recommend that you install the latest available service packs and updates available so that your users receive the best possible experience when connecting to Exchange and Exchange Online.

Outlook clients earlier than Outlook 2007 are not supported. Email clients on Mac operating systems that require DAV, such as Entourage 2008 for Mac RTM and Entourage 2004, are not supported.

Support for Outlook Web App on the wide variety of operating systems and devices is also documented by Microsoft here.

Updated information on the latest available updates for Outlook is documented by Microsoft here. Unless there is some other reason in your environment not to, it is recommended to deploy the very latest available updates for Outlook and Office when planning to deploy Exchange Server 2013.

Knowing the minimum Outlook versions supported we can now look at what versions are running in our environment as we plan the upgrade to Exchange Server 2013.

Often customers have no software inventory system that can provide a fast and accurate report of this information, so other tools need to be used instead. Here are two methods.

Using the Exchange User Monitor (ExMon) to Discover RPC Client Versions

The Microsoft Exchange Server User Monitor can be used to display the client versions for connected users.

Simply install and run the tool on your Exchange servers and observe the client versions connecting in real time.

You can use the “By User” tab to identify specific users of any client versions that need further attention from you.

More detailed information on how to use ExMon is available on TechNet.

Using Log Parser to Discover RPC Client Versions

Another method for discovering client versions is to use Log Parser to analyse the RPC Client Access logs on the Client Access servers.

The RPC Client Access logs are stored in the LoggingRPC Client Access folder of the Exchange installation path, eg C:Program FilesMicrosoftExchange ServerV14LoggingRPC Client Access.

The log files are in CSV format and therefore can be analysed using Log Parser. Two of the fields of interest are:

  • client-software
  • client-software-version

So a Log Parser query to show us the number of hits per client software version would look like this.

2
4
6
8
10
12
-------------------------------------------------------
OUTLOOK.EXE12.0.6606.100047
OUTLOOK.EXE14.0.6126.50006969
OUTLOOK.EXE14.0.7010.1000995
OUTLOOK.EXE14.0.7108.5000583320
OUTLOOK.EXE15.0.4551.1004388

If you spot versions of Outlook that do not meet the minimum supported version you can run additional queries to find the specific user accounts for those versions so that you can investigate further.

For example, this query will return the client names for any version 11.x or 12.x client software that is appearing in the logs.

'C:Program Files (x86)Log Parser 2.2logparser.exe''SELECT EXTRACT_SUFFIX(client-name,0,'=') as Name,client-software as Software,Client-software-version as Version,Count(*) as Hits FROM *.log WHERE Version LIKE '11.%' OR Version LIKE '12.%' GROUP BY Name,Software,Version ORDER BY Name'-i:CSV-nSkipLines:4-rtp:-1

Summary

As you can see even without robust software inventory tools we can still gather information about the names and versions of software connecting to Exchange when planning an Exchange Server 2013 migration.

Paul is a Microsoft MVP for Office Apps and Services and a Pluralsight author. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server.

Currently I’m upgrading an Exchange 2013 environment to Exchange 2016. In general this upgrade runs very smoothly and is almost seemless for user. It’s a complete different story when you’re coming from Exchange 2010.

So far I got only positive feedback and no issue were reported. Until a bunch of shared mailbox have been migrated.

Users complained they cannot access these mailbox anymore. First I couldn’t reproduce the issue, until I got another important detail:

All these user are using Outlook for Mac and indeed I could reproduce the behavior.

This issue is fixed in version 15.38 (170815) of the Insider Fast Build as of August, 16:

A user with a mailbox on Exchange 2013 was granted FullAccess to a mailbox on Exchange 2016. When he tries to access the mailbox using method 3 as described in this KB article, only the folder structure is visible, but no items.

As we were talking about Outlook for Mac, which uses EWS, I used my script Get-EWSStats.ps1 and pulled the data from the logs. But the result were not really clear as the logs were full with the error ErrorInvalidServerVersion

You can find a list of ResponseCode here. But the error

Exchange 2013 outlook for mac os

“This error indicates that an invalid request server version was specified in the request.”

was not really helpful. Therefore I decided to use Fiddler. I think this is the best tool to analyze EWS request as it’s easy to configure and has the built-in ability to display XML data. And now the previous error makes perfect sense:

Outlook for Mac requests version V2016_07_13 when it’s sending GetItem SoapCommand. The problem is that Exchange 2013 doesn’t know this version and the response is as expected: ErrorInvalidServerVersion

The only workarounds are the following ones:

  • migrate the user to Exchange 2016
  • use Outlook for Windows

Looks like someone missed a test scenario. This is definately an issue, which needs to be fixed on client-side. It’s how Exchange works since version 2013:

In Exchange 2013 we still have the Client Access Server role and with Exchange 2016 we have Client Access Services. Both authenticate the incoming request and route the request to the Mailbox server, which has the active copy of the database hosting the mailbox. You can read the full details in this EHLO post.

Thus means the request will never go directly to the mailbox, where the user has FullAccess to. The request get proxied via his Mailbox server.

A possible solution would be Outlook for Mac is using the version of the main mailbox instead of the target mailbox. The way around from Exchange 2016 to 2013 works as expected.

Exchange 2013 Outlook For Macs

I opened a PSS case and the issue is under investigation.