-->
Before you install Exchange Server 2019, we recommend that you review this topic to ensure your network, hardware, software, clients, and other elements meet the requirements for Exchange 2019. Also, make sure you understand the coexistence scenarios that are supported for Exchange 2019 and earlier versions of Exchange.
To actually install Exchange 2019, see Deploy new installations of Exchange.
Supported coexistence scenarios for Exchange 2019
The supported coexistence scenarios between Exchange 2019 and earlier versions of Exchange are described in the following table:
Exchange version | Exchange 2019 organization coexistence |
---|---|
Exchange 2010 and earlier versions | Not supported |
Exchange 2013 | Supported with Exchange 2013 Cumulative Update 21 (CU21) or later on all Exchange 2013 servers in the organization, including Edge Transport servers. |
Exchange 2016 | Supported with Exchange 2016 CU11 or later on all Exchange 2016 servers in the organization, including Edge Transport servers. |
Mixed Exchange 2013 and Exchange 2016 organization | Supported if all Exchange 2013 and Exchange 2016 servers in the organization meet the requirements as previously described in this table. |
Supported hybrid deployment scenarios for Exchange 2019
Exchange 2019 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 server requirements for Exchange 2019
The requirements for the network and the directory servers in your Exchange 2019 organization are described in the following table:
Component | Requirement |
---|---|
Domain controllers | All domain controllers in the forest need to be running one of the following versions of Windows Server: • Windows Server 2019 Standard or Datacenter • Windows Server 2016 Standard or Datacenter • Windows Server 2012 R2 Standard or Datacenter |
Active Directory forest | The Active Directory forest functional level is Windows Server 2012 R2 or higher. |
Active Directory site | The Active Directory site where you install the Exchange Server must contain at least one writeable domain controller that's also a global catalog server, or the installation will fail. Furthermore, you can't install the Exchange server and then remove the domain controller from the Active Directory site. |
DNS namespace | Exchange 2019 supports the following DNS namespaces: • Contiguous • Noncontiguous • Single label domains • Disjoint For more information about DNS namespaces that are supported by Exchange, see KB2269838. |
IPv6 | Exchange 2013 and later support IPv6 only when IPv4 is also installed and enabled on the Exchange server. If you deploy Exchange in this configuration, and your 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. |
Directory server architecture for Exchange 2019
Active Directory domain controllers on 64-bit hardware with a 64-bit version of Windows Server will increase directory service performance for Exchange 2019.
Installing Exchange 2019 on directory servers
For security and performance reasons, we don't recommend installing Exchange 2019 on Active Directory directory servers. Only install Exchange 2019 on member servers.
To learn more about the issues that you'll encounter when you install Exchange on a directory server, see Installing Exchange on a domain controller is not recommended [WarningInstallExchangeRolesOnDomainController]. After Exchange is installed, changing the server role from a member server to a directory server or vice-versa isn't supported.
Hardware requirements for Exchange 2019
For information about deploying Exchange in a virtualized environment, see Exchange Server virtualization.
Component | Requirement | Notes |
---|---|---|
Processor | Either of the following types of 64-bit processors: • Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T). • AMD processor that supports the AMD64 platform. Notes: • Intel Itanium IA64 processors are not supported. • Recommended supported processor sockets is up to 2 on physical machines. | See the Supported operating systems for Exchange 2019 section later in this topic for supported operating systems. |
Memory | Varies by Exchange server role: • Mailbox: 128 GB minimum recommended • Edge Transport: 64 GB minimum recommended. | Exchange 2019 has large memory support (up to 256 GB). |
Paging file size | Set the paging file minimum and maximum value to the same size: 25% of installed memory. | None |
Disk space | • At least 30 GB of free space on the drive where you're installing Exchange. • At least 200 MB of free space on the system drive. • At least 500 MB of free space on the drive that contains the message queue database. | None |
Screen resolution | 1024 x 768 pixels (XGA) or higher | None |
File system | NTFS: Required on partitions that contain the following types of files: • The System partition. • Exchange binaries. • Files generated by Exchange diagnostic logging. • Transport database files (for example, the mail queue database). ReFS: Supported on partitions that contain the following types of Exchange files: • Mailbox databases. • Transaction logs. | None |
Supported operating systems for Exchange 2019
Exchange component | Requirement |
---|---|
Mailbox and Edge Transport server roles | Windows Server 2019 Standard or Datacenter |
Management tools | One of the following versions of Windows: • Windows Server 2019 Standard or Datacenter • 64-bit edition of Windows 10 |
Notes:
- Installing Exchange 2019 on a computer that's running Windows Server Core is fully supported and recommended. The Desktop Experience feature is no longer required.
- Installing Exchange 2019 on a computer that's running Nano Server isn't supported.
Supported Powershell versions for Exchange 2019 servers
Exchange 2019 servers support the version of PowerShell that's included in the release of Windows Server where Exchange is installed. Don't install stand-alone downloads of WMF or PowerShell on Exchange servers.
Installing other software on Exchange 2019 servers
We don't support installing Office client or Office server software on Exchange servers (for example, SharePoint Server, Skype for Business Server, Office Online Server, or Project Server). Other software that you want to install on an Exchange 2019 server needs to be designed to run on the same computer as Exchange Server.
Supported .NET Framework versions for Exchange 2019
We strongly recommend that you use the latest version of the .NET Framework that's supported by the release of Exchange you're installing.
Important
• Releases of .NET Framework that aren't listed in the table below aren't supported on any release of Exchange 2019. This includes minor and patch-level releases of .NET Framework.
• The complete prerequisite list for Exchange 2019 is available here.
• The complete prerequisite list for Exchange 2019 is available here.
Exchange version | .NET Framework 4.7.2 or later |
---|---|
Exchange 2019 | Supported |
Supported clients (with latest updates) in Exchange 2019
- Office 365 ProPlus
- Outlook 2019
- Outlook 2016
- Outlook 2013
- Outlook for Mac for Office 365
- Outlook 2016 for Mac
Important
You need KB3140245 to apply registry keys to enable TLS 1.1 & 1.2 support for Windows 7, otherwise Outlook 2013 and 2016 will not work on Windows 7.
Lync/Skype For Business Server integration with Exchange 2019
If you're integrating Lync presence and instant messaging with Exchange Server, Lync Server 2013 Cumulative Update 10 or later is required. If you're integrating Skype for Business presence and instant messaging with Exchange Server, Skype for Business Server Cumulative Update 7 or later is required.
Before you install Exchange Server 2016, we recommend that you review this topic to ensure your network, hardware, software, clients, and other elements meet the requirements for Exchange 2016. Also, make sure you understand the coexistence scenarios that are supported for Exchange 2016 and earlier versions of Exchange.
To actually install Exchange 2016, see Deploy new installations of Exchange.
Supported coexistence scenarios for Exchange 2016
The following table lists the scenarios in which coexistence between Exchange 2016 and earlier versions of Exchange is supported.
Exchange version | Exchange organization coexistence |
---|---|
Exchange 2007 and earlier versions | Not supported |
Exchange 2010 | Supported with Update Rollup 11 for Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers. |
Exchange 2013 | Supported with Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers. |
Mixed Exchange 2010 and Exchange 2013 organization | Supported with the following minimum versions of Exchange: • Update Rollup 11 Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers. • Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers. |
Supported hybrid deployment scenarios for Exchange 2016
Exchange 2016 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 server requirements for Exchange 2016
The following table lists the requirements for the network and the directory servers in your Exchange 2016 organization.
Component | Requirement |
---|---|
Domain controllers | All domain controllers in the forest need to be running one of the following versions of Windows Server: • Windows Server 2019 Standard or Datacenter • Windows Server 2016 Standard or Datacenter • Windows Server 2012 R2 Standard or Datacenter • Windows Server 2012 Standard or Datacenter • Windows Server 2008 R2 Standard or Enterprise • Windows Server 2008 R2 Datacenter RTM or later |
Active Directory forest | The Active Directory forest functional level is Windows Server 2008 R2 or higher. |
Active Directory site | • The Active Directory site where you install the Exchange Server must contain at least one writeable domain controller that's also a global catalog server, or the installation will fail. • You can't install the Exchange server and then remove the domain controller from the Active Directory site. |
DNS namespace support | Exchange 2016 supports the following domain name system (DNS) namespaces: • Contiguous • Noncontiguous • Single label domains • Disjoint 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 2016, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2016 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. |
Directory server architecture for Exchange 2016
The use of 64-bit Active Directory domain controllers increases directory service performance for Exchange 2016.
Note
In multi-domain environments, on Windows Server 2008 domain controllers that have the Active Directory language locale set to Japanese (ja-jp), your servers may not receive some attributes that are stored on an object during inbound replication. For more information, see KB949189.
Installing Exchange 2016 on directory servers
For security and performance reasons, we recommend that you install Exchange 2016 only on member servers and not on Active Directory directory servers. To learn about the issues you can face when installing Exchange 2016 on a directory server, see Installing Exchange on a domain controller is not recommended [WarningInstallExchangeRolesOnDomainController]. After Exchange 2016 is installed, changing its role from a member server to a directory server, or vice versa, isn't supported.
Hardware requirements for Exchange 2016
For information about deploying Exchange in a virtualized environment, see Exchange Server virtualization.
Component | Requirement | Notes |
---|---|---|
Processor | Either of the following types of 64-bit processors: • Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T). • AMD processor that supports the AMD64 platform. Note: Intel Itanium IA64 processors are not supported. | For more information, see Sizing Exchange 2016 Deployments. See the Supported operating systems for Exchange 2016 section later in this topic for supported operating systems. |
Memory | Varies by Exchange server role: • Mailbox: 8 GB minimum. • Edge Transport: 4 GB minimum. | For more information, see Sizing Exchange 2016 Deployments. |
Paging file size | Set the paging file minimum and maximum value to the same size: • Less than 32 GB of RAM installed: Physical RAM plus 10MB, up to a maximum value of 32GB (32,778MB). • 32 GB of RAM or more installed: 32GB | None |
Disk space | • At least 30 GB of free space on the drive where you're installing Exchange, plus an additional 500 MB for each Unified Messaging (UM) language pack that you plan to install. • At least 200 MB of free space on the System drive. • At least 500 MB of free space on the drive that contains the message queue database. | For more information, see Sizing Exchange 2016 Deployments. |
Drive | DVD-ROM drive, local or network accessible. | None |
Screen resolution | 1024 x 768 pixels (XGA) or higher | None |
File format | NTFS: Required on partitions that contain the following types of files: • The System partition. • Exchange binaries. • Files generated by Exchange diagnostic logging. • Transport database files (for example, the mail queue database). ReFS: Supported on partitions that contain the following types of Exchange files: • Mailbox databases. • Transaction logs. • Content indexing files. | None |
Supported operating systems for Exchange 2016
Important: We don't support the installation of Exchange 2016 on a computer that's running Windows Server Core or Nano Server. The Windows Server Desktop Experience feature needs to be installed. To install Exchange 2016, you need to do one of the following to install the Desktop Experience on Windows Server prior to starting Exchange 2016 Setup:
- Windows Server 2012 and Windows Server 2012 R2: Run the following command in Windows PowerShell
- Windows Server 2016: Install Windows Server 2016 and choose the Desktop Experience installation option. If a computer is running Windows Server 2016 Core mode and you want to install Exchange 2016 on it, you'll need to reinstall the operating system and choose the Desktop Experience installation option.
Component | Requirement |
---|---|
Mailbox and Edge Transport server roles | • Windows Server 2016 Standard or Datacenter* • Windows Server 2012 R2 Standard or Datacenter • Windows Server 2012 Standard or Datacenter |
Management tools | One of the following versions of Windows: • Windows Server 2016 Standard or Datacenter* • Windows Server 2012 R2 Standard or Datacenter • Windows Server 2012 Standard or Datacenter • 64-bit edition of Windows 10 • 64-bit edition of Windows 8.1 |
* Requires Exchange Server 2016 Cumulative Update 3 or later.
Supported Windows Management Framework versions for Exchange 2016
Exchange 2016 only supports the version of Windows Management Framework that's built in to 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.
Installing other software on Exchange 2016 servers
We don't support installing Office clients or other Office server products (for example, SharePoint Server, Skype for Business Server, Office Online Server, or Project Server) on Exchange 2016 servers. Software that you want to install on an Exchange 2016 server needs to be designed to run on the same computer as Exchange Server.
Supported .NET Framework versions for Exchange 2016
We strongly recommend that you use the latest version of .NET Framework that's supported by the release of Exchange you're installing.
Important
• Releases of .NET Framework that aren't listed in the table below are not supported on any release of Exchange 2016. This includes minor and patch-level releases of .NET Framework.
• The complete prerequisite list for Exchange 2016 is available here.
• The complete prerequisite list for Exchange 2016 is available here.
Exchange version | .NET Framework 4.8 | .NET Framework 4.7.2 | .NET Framework 4.7.1 | .NET Framework 4.6.2 |
---|---|---|---|---|
Exchange 2016 CU13 | Supported | Supported | ||
Exchange 2016 CU11, CU12 | Supported | Supported | ||
Exchange 2016 CU10 | Supported | |||
Exchange 2016 CU8, CU9 | Supported | Supported | ||
Exchange 2016 CU5, CU6, CU7 | Supported |
Supported clients (with latest updates) in Exchange 2016
- Office 365 ProPlus
- Outlook 2019
- Outlook 2016
- Outlook 2013
- Outlook 2010 SP2
- Outlook 2016 for Mac
- Outlook for Mac for Office 365
Exchange third-party clients
Exchange Server offers several well-known protocols, and publishes APIs that third-party vendors often write clients for.
Microsoft makes no warranties, expressed or implied, as to the overall suitability, fitness, compatibility, or security of clients that are created by third-party developers.
If you want to use a third-party client that uses our protocols or APIs, we recommend that you thoroughly review and test all considerations (functionality, security, maintenance, management, and so on) before you deploy the client in the enterprise workspace. We also recommend that you make sure that the third-party vendor offers an appropriate Enterprise Support Agreement (ESA).
-->Exchange Server 2016 and Exchange Server 2019 are available in two server editions:
- Enterprise Edition: Can scale up to 100 mounted databases per server.
- Standard Edition: Limited to five mounted databases per server.
A mounted database is a database that's in use (an active mailbox database that's mounted for use by clients or a passive mailbox database that's mounted in recovery for log replication and replay). While you can create more databases than the described limits, you can only mount the maximum number of databases that are allowed by the edition of Exchange. Note that the recovery database doesn't count towards these limits.
The server editions are defined by a product key. When you enter a valid product key, the supported edition for the server is established. For more information, see Enter your Exchange Server product key.
Notes:
- You can use a valid product key to move from the Trial Edition (evaluation version) of Exchange to either Standard Edition or Enterprise Edition. No loss of functionality occurs after the Trial Edition expires, so you can maintain lab, demo, training, and other non-production environments beyond 120 days without having to reinstall the Trial Edition of Exchange or entering a product key.
- Magalir mattum movie online. You can use a valid product key to move from Standard Edition to Enterprise Edition.
- You can't use a valid product key to downgrade from Enterprise Edition to Standard Edition or revert to the Trial Edition. You can only do these types of downgrades by uninstalling Exchange, reinstalling Exchange, and entering the correct product key.
Exchange Server versions
For a list of Exchange Server versions and how to download and upgrade to the latest version of Exchange, see the following topics:
To view the Exchange version and edition information for all Exchange servers in your organization, run the following command in the Exchange Management Shell:
Exchange Server license types
Exchange 2013 and all later versions use a licensing model that's similar to how Exchange 2010 was licensed:
- Server licenses: A license must be assigned for each Exchange server. The Server license is sold in two server editions: Standard Edition and Enterprise Edition.
- Client Access licenses (CALs): Exchange also comes in two CAL editions, which are referred to as a Standard CAL and an Enterprise CAL. You can mix and match the Exchange server editions with the CAL types. For example, you can use Enterprise CALs with Standard Edition or Standard CALs with Enterprise Edition.
For more information about Exchange license types, see Licensing.
As you probably know, the Standard Edition of Microsoft Exchange is much more limited than the Enterprise Edition. Besides only providing for one information store, the Standard Edition limits your Exchange mail storage—to 75GB with SP2 and to 16GB without SP2. While at first glance a single information store might not seem like much of a limitation, bear in mind that there are a number of global properties for an information store, such as the mail quota, that are easier to manage when you provide multiple stores for your data.
Exchange 2016 Standard Vs Enterprise Features
The good news is that Microsoft now makes 'step up' licenses available to allow you to move from the Standard Edition to the Enterprise Edition if you're under volume licensing arrangements. I won't try to give you advice on Microsoft’s convoluted licensing schemes, though. Contact your software reseller to find out if you're eligible.
Before you do anything, make sure you have a good backup. Even though the procedure is easy, you never know what might happen.
To upgrade to the Enterprise Edition or Exchange, insert an Enterprise Edition CD into your Exchange server and execute the setup.exe program in the SETUPI386 folder. On the 'Component Selection' screen, choose the Reinstall option.
You may get errors warning you that newer files will be overwritten. This will happen if you’ve applied a service pack to your Exchange server. Be sure to reapply the service pack to your server after you upgrade to the Enterprise Edition. Obviously, this process is best done during off-hours.
After the upgrade, go to System Manager, and choose Servers, you will see 'Enterprise' indicated under the Edition heading.
Microsoft isn't known for making its licensing easy to understand; in fact, many of the company's products have numerous licensing options that are often confusing. Exchange Server 2010 licensing options don't vary from this pattern. Here are the server-side and client-side licensing options that are available for the product. I'll also provide a description of the external connector.
Exchange 2019 Standard Enterprise
Server-side licensing
If you're going to use on-premises Exchange, you need a server, as well as Exchange licenses for each server (physical or virtual) on which you install the Exchange software.
For quite some time, Microsoft has offered server licensing in two editions — Standard and Enterprise — and there used to be significant differences between the editions, but that's changed a lot with Exchange 2010; now, it's all about scale.
- Exchange 2010 Standard edition. Supports up to a total of 5 mailbox databases per server.
- Exchange 2010 Enterprise edition. Supports up to a total of 100 mailbox databases per server.
In previous versions of Exchange, you didn't have the full range of availability options in the Standard edition that were available in the Enterprise edition. With Exchange 2010, both editions fully support Database Availability Groups as long as you're running Exchange on the Enterprise edition of Windows Server.
Client-side licensing
Client licensing comes in Standard and Enterprise editions, but there's a catch: You can't buy just an Enterprise client access license (CAL); if you want an enterprise feature such as unified messaging, you must first buy a Standard CAL to unlock the basic functionality, and then you add on the Enterprise CAL to add the advanced features. Microsoft calls this 'additive licensing.' So, in essence, you buy two CALs for each user who needs enterprise-level features. It might sound unnecessary, but it's kind of nice because you can mix-and-match the licenses to suit your needs. For example, if you only have several users who need functionality provided by the Enterprise CAL (such as Unified Messaging), you just need to buy Enterprise CALs for those users. For all other users, you can stick with the Standard option and save a few bucks.
Microsoft also makes a Services add-on available that provides some additional Exchange security options. Lirik kau auraku chord.
Top of FormFeature Bottom of Form | Standard CAL | Std. + Ent. CAL (both licenses) | Std. + Ent. CAL plus Services |
Yes | Yes | Yes | |
Calendar | Yes | Yes | Yes |
Contacts | Yes | Yes | Yes |
Tasks | Yes | Yes | Yes |
Outlook Web App (cross browser) | Yes | Yes | Yes |
ActiveSync Mobile Access | Yes | Yes | Yes |
Role Based Admin. Control | Yes | Yes | Yes |
Integration of IM, SMS, and RSS | Yes | Yes | Yes |
Federated Calendar Sharing | Yes | Yes | Yes |
ActiveSync Mobile Policies | Standard | Advanced | Advanced |
Journaling | Per Database | Per User / Distribution List | Per User / Distribution List |
Voicemail with Unified Messaging | No | Yes | Yes |
Retention Policies | Default | Custom | Custom |
Integrated Archive | No | Yes w/Office 2010 Pro Plus | Yes w/Office 2010 Pro Plus |
Multi-Mailbox Search | No | Yes | Yes |
Legal Hold | No | Yes | Yes |
Information Protection & Control | No | Yes | Yes |
Top of Form Forefront Security for Exchange Bottom of Form | No | No | Yes |
Forefront Online Security for Exchange | No | No | Yes Bottom of Form |
It's important to understand that basic email functionality is not allowed with just the Enterprise CAL. If you want email, calendaring, and other typical Exchange functionality, you need to buy the Standard CAL. If you want advanced features, such as Unified Messaging, you need to buy two CALs.
Client CALs can be licensed per user or per device. If any of your users share machines (e.g., shift workers), you can save money with per-device CALs. If you have users who need to access Exchange from multiple devices, you should go with per-user CALs.
Note: A Standard or Enterprise CAL can be used with either server edition — Standard or Enterprise. You don't need to match editions.External connector
If you have external users (e.g., business partners, suppliers, customers, retirees, and alumni) who need to access your Exchange server, the external connector license grants access to the Exchange server by an unlimited number of these external users.
Summary
Exchange 2010 has a number of licensing options. This article is intended to help you get your bearings with regard to these options. For specific questions, please contact your Microsoft licensing reseller.
Keep up with Scott Lowe's posts on TechRepublic
Q: (from John)
We are looking into Exchange 2010 and would like to get a list of all the differences between Enterprise and Standard versions. Also, we need to know is some of the Enterprise features such as Integrated Archiving, Multi-mailbox search and legal hold, and advanced journaling are available with the Standard version, if you use an Enterprise CAL?
We are looking for more info on how the standard and enterprise CALs interact with BOTH standard and enterprise Exchange Server, and what features are available depending on which CAL you have.
We are having trouble determining which CAL and Server version to buy depending on what features we need for a certain customer, is there a breakdown for this somewhere?
A:
the functionality of the client is dependent on the CAL and independent of the Server.
The Exchange Licensing page is a good reference:
So, to take the specific features the customer mentioned:
- Integrated Archiving (Ent CAL)
- Multi-mailbox Search & Legal Hold (Ent CAL)
- Advanced Journaling (Ent CAL)
Those features are all defined by the CAL(s) selected and independent of the Server choice. I view the CAL as the choice of features and the Server and the choice or scalability.
Steve
Technorati Tags: Exchange 2010,Standard CAL,Enterprise CAL,Archive,Mulit-Mailbox Search,Legal Hold,Journaling
del.icio.us Tags: Exchange 2010,Standard CAL,Enterprise CAL,Archive,Mulit-Mailbox Search,Legal Hold,Journaling