Start quickly with the most recent versions of Word, Excel, PowerPoint, Outlook, OneNote and OneDrive —combining the familiarity of Office and the unique Mac features you love. Work online or offline, on your own or with others in real time—whatever works for what you're doing. Microsoft Exchange Server 2010 For Mac, Indesign Cs4 Scripting Guide, Full Version Solidworks 2009 Premium SP4, Autodesk AutoCAD LT 2015 Information. Adobe Photoshop CC Latest Version Free Download. WinRAR (64-bit). It does indeed look like Outlook 2016 for Mac (included in Office 365 for Mac) supports Exchange 2010, but it needs to be Exchange 2010 SP3; this means previous Exchange 2010 versions might or might not work, but they are not supported. Solution: Contact your Microsoft Exchange account administrator. Ask your Microsoft Exchange account administrator to tell you which proxy server to use to connect to the Microsoft Exchange server. For information about how to configure a connection to a proxy server, see Mac OS Help.
Microsoft has plugged some key gaps in its 'new Outlook' for macOS, currently in preview and given a fresh update just a few days ago, but the product still has puzzling omissions that drive users back to the old version.
The following instructions step through the process of configuring your Office 365 Exchange Online account with Outlook 2016 for macOS.
The revised Mac Outlook was first revealed at the Ignite event in late 2019. It appears to be a complete rebuild of the Mac email client, geared towards Office 365, but the question administrators will be pondering is whether important features in the existing Outlook will ever appear in the new one.
The history of Outlook on the Mac is inglorious. Microsoft and Mac go back a long way. Excel, for example, was a Mac application two years before it appeared on Windows. When it came to Outlook though, Mac users lost out. Outlook on Windows goes back to 1997, but the first full Mac version did not appear until Outlook 2011, and even that was not very good, slower than the Windows version and missing some features, such as Visual Basic for Applications (VBA).
VBA has never come to Outlook on the Mac, but a 2014 release was much improved, as Microsoft began to push the idea of Office 365 everywhere rather than keeping users hooked on Windows.
The new Outlook for the Mac in its first preview (click to enlarge)
Fast-forward to today, and there is not that much missing in Outlook 365 for Mac versus Windows, VBA aside.
All that is set to change with the latest new Outlook Mac as the pendulum swings away from making the Mac Outlook close to the Windows one, and towards giving Mac users a more distinct experience. It is also a matter of protocols. The existing Outlook Mac uses Exchange Web Services (EWS) which is being phased out.
Outlook on Windows generally uses MAPI over HTTP, perhaps the nearest thing to a native Exchange protocol. Microsoft is not happy with either and for its 'modern' mail client in Windows 8 and Windows 10 it developed a new sync protocol. In the past this was sometimes called Hx but it seems now to go by the name Microsoft Sync.
When Microsoft acquired Accompli in 2014, whose product became Outlook Mobile, it used its own protocol but that too now uses Microsoft Sync. According to presentations at Ignite 2019, this new sync protocol is designed specifically for mail-related data and makes the best even of poor connections, prioritising recent data.
The move from EWS to Microsoft Sync enables new features and improved performance, and no longer downloads the entire mailbox to the local machine. System requirements are for macOS 10.14 Mojave and Office 365, Outlook.com or Gmail email accounts.
The snag with a rebuilt Outlook for Mac is that having nearly caught up with Windows Outlook, it is now far behind in terms of features. It is in preview and some will reappear, but it is unlikely to be the full set. It hardly qualifies as a mail client in its current incarnation, with no support for standard protocols like POP3 and IMAP, nor any way of connecting to on-premises Exchange.
Imagine OLE reinvented for the web and that's 90% of Microsoft's Fluid Framework: We dig into O365 collaborative tech
READ MORE'We don't support on-prem yet but it's going to come soon,' said Microsoft in November 2019; six months on it is not there yet. On the plus side, it not only looks pretty, with full support for the Mac's Dark Mode on Catalina, but also performs well, with a fluidity that frankly feels unusual in a Mac Outlook product.
Features of the new Outlook for Mac include a new unified inbox view that avoids clicking between accounts, if you have several configured. You can now reply to emails inline ('nested compose'), a convenience feature that has been in Windows Outlook for some time. There is a new 'ignore conversation' option. Creating meetings uses a new simplified dialogue that you can expand as needed.
As for the new features added in the June update, these include add-in support (a big deal), sensitivity labels for classifying confidential data, a People view for managing contacts, an option to create an event directly from an email, read receipts, and a 'coming soon' promise of the ability to open shared calendars and to encrypt emails with S/MIME.
The actual preview release did not quite live up to the promise. In particular, the People view is not yet enabled, thanks to some last-minute bug that was discovered. One gets the new Outlook by signing up to the Office 'Insider Fast' channel, and after the new version downloads and installs, one can switch back and forth by toggling a 'New Outlook' switch. If the user attempts to use a feature such as the People view, a message pops up inviting the user to switch back, wrecking the fluid experience but that is what one gets for trying a preview.
The current preview is not fully usable, but fortunately switching back is quick
The problem of Outlook on Windows being different from Outlook on Mac will get worse
Microsoft has not specified a release date for the new Outlook Mac but a few things are clear. First, it will be the best Outlook yet, perhaps on any platform, in terms of appearance and design. This is not a high bar: Outlook on Windows is a mess from a user interface perspective, and has dialogues buried within that have not changed for decades. Performance also looks promising.
Second, Outlook Mac will be focused on cloud, especially Office 365, though it also already has good support for Google mail. Teams integration will also be strong and Microsoft has demonstrated features like converting an event to a Teams meeting, handy in times of lockdown.
Lastly, the problem of Outlook on Windows being different from Outlook on Mac will get worse. What if Microsoft replaces the Windows version with a similarly rebuilt product? Perhaps it will; but the difficulty is that Outlook is baked into the Windows ecosystem and forms part of workflows, some automated with COM technology, that will break if Microsoft replaces it. Custom add-ins, VBA projects, ancient APIs that remain for legacy reasons, all mean this will be a tricky application to replace.
Creating a meeting in the new Outlook Mac: just drag in the calendar and this simple dialog pops up
Outlook on Windows is perhaps the most annoying of Microsoft's Office products, yet the job it does is a critical one, bringing together email, calendar and tasks, and providing collaboration features like shared calendars and contacts. Some legacy features, like Exchange public folders, made their way into Office 365 where they have become something of a burden to Microsoft.
The new Outlook for Mac, when it comes out of preview, will represent Microsoft's current thinking on how Outlook should look and behave in the cloud era, but it will be some time before that can apply in Windows as well. ®
Applies to: Exchange Server 2013
Learn about the Exchange 2013 requirements that you need to know before you install Exchange 2013. For example, you'll learn about the hardware, network, and operating system requirements.
Before you install Microsoft Exchange Server 2013, we recommend that you review this topic to ensure that your network, hardware, software, clients, and other elements meet the requirements for Exchange 2013. In addition, make sure you understand the coexistence scenarios that are supported for Exchange 2013 and earlier versions of Exchange.
Supported coexistence scenarios
The following table lists the scenarios in which coexistence between Exchange 2013 and earlier versions of Exchange is supported.
Coexistence of Exchange 2013 and earlier versions of Exchange Server
| Exchange version | Exchange organization coexistence |
|---|---|
Exchange Server 2003 and earlier versions | Not supported |
Exchange 2007 | Supported with the following minimum versions of Exchange:
|
Exchange 2010 | Supported with the following minimum versions of Exchange:
|
Mixed Exchange 2010 and Exchange 2007 organization | Supported with the following minimum versions of Exchange:
|
1 If you want to create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, you need to install Exchange 2007 SP3 Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
2 If you want to create an EdgeSync Subscription between an Exchange 2010 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, you need to install Exchange 2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport server.
Supported hybrid deployment scenarios
Exchange 2013 supports hybrid deployments with Microsoft 365 or Office 365 organizations that have been upgraded to the latest version of Microsoft 365 or Office 365. For more information about specific hybrid deployments, see Hybrid deployment prerequisites.
Network and directory servers
The following table lists the requirements for the network and the directory servers in your Exchange 2013 organization.
Network and directory server requirements for Exchange 2013
| Component | Requirement |
|---|---|
Schema master | By default, the schema master runs on the first Active Directory domain controller installed in a forest. The schema master must be running one of the following:
|
Global catalog server | In each Active Directory site where you plan to install Exchange 2013, you must have at least one global catalog server running one of the following:
For more information about global catalog servers, see What is the Global Catalog. |
Domain controller | In each Active Directory site where you plan to install Exchange 2013, you must have at least one writeable domain controller running one of the following:
|
Active Directory forest | Active Directory must be at Windows Server 2003 forest functionality mode or higher.2 |
DNS namespace support | Exchange 2013 supports the following domain name system (DNS) namespaces:
For more information about DNS namespaces supported by Exchange, see Microsoft Knowledge Base article 2269838, Microsoft Exchange compatibility with Single Label Domains, Disjoined Namespaces, and Discontiguous Namespaces. |
IPv6 support | In Exchange 2013, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2013 is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses. For more information, see IPv6 support in Exchange 2013. |
1 Windows Server 2012 R2 and Windows Server 2016 are supported only with Exchange 2013 SP1 or later.
2 Windows Server 2012 R2 or Windows Server 2016 forest functionality mode is supported only with Exchange 2013 SP1 or later.
Directory server architecture
The use of 64-bit Active Directory domain controllers increases directory service performance for Exchange 2013.
Note
In multi-domain environments, on Windows Server 2008 domain controllers that have the Active Directory language locale set to Japanese, your servers might not receive some attributes that are stored on an object during inbound replication. For more information, see Microsoft Knowledge Base article 949189, A Windows Server 2008 domain controller that is configured with the Japanese language locale may not apply updates to attributes on an object during inbound replication.
Installing Exchange 2013 on directory servers
For security and performance reasons, we recommend that you install Exchange 2013 only on member servers and not on Active Directory directory servers. However, you can't run DCPromo on a computer running Exchange 2013. After Exchange 2013 is installed, changing its role from a member server to a directory server, or vice versa, isn't supported.
Hardware
The recommended hardware requirements for Exchange 2013 servers vary depending on a number of factors including the server roles that are installed and the anticipated load that will be placed on the servers.
Mac Os Servers
For detailed information on how to properly size and configure your deployment, see Exchange 2013 Sizing and Configuration Recommendations.
For information about deploying Exchange in a virtualized environment, see Exchange 2013 virtualization.
Hardware requirements for Exchange 2013
| Component | Requirement | Notes |
|---|---|---|
Processor |
| See the 'Operating system' section later in this topic for supported operating systems. |
Memory | Varies depending on Exchange roles that are installed:
| None. |
Paging file size | The page file size minimum and maximum must be set to physical RAM plus 10 MB, to a maximum size of 32778MB if you're using more than 32GB of RAM. | For detailed pagefile recommendations, see the 'Pagefile' section in Exchange 2013 Sizing and Configuration Recommendations. |
Disk space |
| For detailed information on storage recommendations, see Exchange 2013 storage configuration options. |
Drive | DVD-ROM drive, local or network accessible | None. |
Screen resolution | 1024 x 768 pixels or higher | None. |
File format | Disk partitions formatted as NTFS file systems, which applies to the following partitions:
Disk partitions containing the following types of files can be formatted as ReFS:
| None. |
Operating system
The following table lists the supported operating systems for Exchange 2013.
Important
We don't support the installation of Exchange 2013 on a computer that's running in Windows Server Core mode. The computer must be running the full installation of Windows Server. If you want to install Exchange 2013 on a computer that's running in Windows Server Core mode, you must convert the server to a full installation of Windows Server by doing one of the following steps:
Windows Server 2008 R2: Reinstall Windows Server and select the Full Installation option.
Windows Server 2012 R2 or Windows Server 2012: Convert your Windows Server Core mode server to a full installation by running the following command.
Supported operating systems for Exchange 2013
| Component | Requirement |
|---|---|
Mailbox, Client Access, and Edge Transport server roles | One of the following:
|
Management tools | One of the following:
|
1 Windows Server 2012 R2 is supported only with Exchange 2013 SP1 or later.
2 Windows 8.1 is supported only with Exchange 2013 SP1 or later.
Supported Windows Management Framework versions for Exchange 2013
Exchange 2013 only supports the version of Windows Management Framework that's built into the release of Windows that you're installing Exchange on. Don't install versions of Windows Management Framework that are made available as stand-alone downloads on servers running Exchange.
.NET Framework
We strongly recommend that you use the latest version of .NET Framework that's supported by the release of Exchange you're installing.
| Exchange 2013 version | .NET Framework 4.8 | .NET Framework 4.7.2 | .NET Framework 4.7.1 | .NET Framework 4.6.2 |
|---|---|---|---|---|
| CU23 | X | X | ||
| CU21, CU22 | X | X | ||
| CU19, CU20 | X | X | ||
| CU16, CU17, CU18 | X | |||
| CU15 | X |
Note: For older versions of the .NET Framework, see the Exchange Server supportability matrix
Supported clients
Exchange 2013 supports the following versions of Outlook and Entourage for Mac:
- Microsoft 365 Apps for enterprise
- Outlook 2019
- Outlook 2016
- Outlook 2013
- Outlook 2010
- Outlook 2007
- Entourage 2008 for Mac, Web Services Edition
- Outlook for Mac for Office 365
- Outlook for Mac 2011
For a list of Outlook releases that Exchange supports, see Outlook Updates.
Important
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.
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.
Mac Server App
Outlook Web App supports several browsers on a variety of operating systems and devices. For detailed information, see What's new for Outlook Web App in Exchange 2013.
