Install Microsoft Entourage Mac
-->
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.
Jan 09, 2018 Question: Q: microsoft entourage 2008 to outlook 2016. However you are using a Mac and Microsoft slime balls that they are do not allow Entourage nor even Outlook on the Mac to create PST files. Converting from Mac Entourage e-mail to a PST file for import into Mac Outlook 2016.
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:
|
Note 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.
Note 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 Office 365 tenants that have been upgraded to the latest version of 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 higher2. |
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 is supported only with Exchange 2013 SP1 or later.
2 Windows Server 2012 R2 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.
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. |
Microsoft Entourage 2008
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:
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, see Exchange Server supportability matrix
Supported clients
Exchange 2013 supports the following versions of Outlook and Entourage for Mac:
Office 365 ProPlus
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.
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.
Upgrading to Outlook 2011 for Mac from Entourage 2008 or 2004 is simple. After you install Office 2011 for Mac and close the welcome screen, Outlook automatically upgrades your Entourage Identity into a new 2011 Identity. Your old Entourage Identity remains on your drive unchanged.
Later, when you’re satisfied that Outlook brought forward everything you need from your old Identity, you can save your old Entourage Identity for posterity or trash it. Your old Identity can be found in DocumentsMicrosoft User Data folderOffice 2008 (or 2004) Identities. Identities can be large, so when you’re satisfied that your Identity is working fine in Outlook, deleting your old Identity can free a considerable amount of disc space.
Microsoft Entourage For Mac
Here are some fine details about upgrading from Entourage 2008 or Entourage 2004:
Categories, calendars, calendar events, tasks, and notes are all supported in Outlook and will be carried forward.
Outlook upgrades only one Identity automatically.
If you have any Project Center documents, they’re left undisturbed. If your project documents are not already in shared locations and you need to share them, consider moving your documents to SkyDrive, SharePoint, Mac OS X sharing, or Windows shared folders.
Project Center projects will be lost because Entourage Project Center is not supported in Outlook.
Outlook does not support Entourage’s link feature. Links that were in Entourage will be abandoned when upgrading.
If you’re using a version of Entourage older than 2004 or 2008, Outlook may not be able to import your Entourage Identity. To find out which version of Entourage you have, choose Entourage→About Entourage. Before installing Office 2011, in Entourage choose File→Export to save your Identity as an Entourage Archive file (.rge). See Entourage help for details about how to do this. In Entourage, choose Tools→Accounts and gather all the account information. You’ll need to re-create your accounts in Outlook. After installing Office 2011, open Microsoft Outlook.
Follow these steps to import your Identity into Outlook from the .rge file using a wizard-like series of setup dialogs:
Microsoft Entourage Email
In Outlook, choose File→Import from the menu bar.
Select the Entourage Information from an Archive or Earlier Version option and then click the right-arrow button at the lower-right corner of the dialog.
Select the Entourage Archive (.rge) option and click the right-arrow button at the lower-right corner of the dialog.
Navigate to the saved Entourage archive .rge file and click the Import button.
Outlook imports your Identity. If it seems like nothing is happening and the progress bar got all the way to the end, just keep waiting. Eventually you see the Done button.
Click Done.
In Outlook, choose Tools→Accounts from the menu bar.
Enter account information to restore your accounts.