Global Groups Local Groups Universal Groups Exchange Issues with Groups Primary Group Issue Administrative Plan.
Administrative Basics Native vs. Mixed Mode Administration Applying Administrative Permissions Administrative Roles Designing The Routing Topology. Routing Group Planning Single Routing Groups Multiple Routing Groups Planning Routing Group Connectors Choosing a Connector Creating a Routing Group Connector Creating an X.
Connector Costs Message Flow Planning Providing Fault Tolerance Routing Group Master Servers: What and Where. Determining Server Requirements Server Role Considerations Server Sizing Capacity Planning Tools Public Folders.
Determining Requirements Organization Issues Public Folder Trees 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. Skip to main content.
This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Supported coexistence scenarios for Exchange The supported coexistence scenarios between Exchange and earlier versions of Exchange are described in the following table: Exchange version Exchange organization coexistence Exchange and earlier versions Not supported Exchange Supported with Exchange Cumulative Update 21 CU21 or later on all Exchange servers in the organization, including Edge Transport servers.
Exchange Supported with Exchange CU11 or later on all Exchange servers in the organization, including Edge Transport servers. Mixed Exchange and Exchange organization Supported if all Exchange and Exchange servers in the organization meet the requirements as previously described in this table. Supported hybrid deployment scenarios for Exchange Exchange supports hybrid deployments with Microsoft or Office organizations that have been upgraded to the latest version of Microsoft or Office Network and directory server requirements for Exchange The requirements for the network and the directory servers in your Exchange 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 Standard or Datacenter Windows Server Standard or Datacenter Windows Server R2 Standard or Datacenter Active Directory forest The Active Directory forest functional level is Windows Server 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.
Installing Exchange on directory servers For security and performance reasons, we don't recommend installing Exchange on Active Directory directory servers. Hardware requirements for Exchange For information about deploying Exchange in a virtualized environment, see Exchange Server virtualization.
Installing Exchange on a computer that's running Nano Server isn't supported. Important Releases of. Supported coexistence scenarios for Exchange The following table lists the scenarios in which coexistence between Exchange and earlier versions of Exchange is supported.
Exchange version Exchange organization coexistence Exchange and earlier versions Not supported Exchange Supported with Update Rollup 11 for Exchange SP3 or later on all Exchange servers in the organization, including Edge Transport servers. Exchange Supported with Exchange Cumulative Update 10 or later on all Exchange servers in the organization, including Edge Transport servers.
Mixed Exchange and Exchange organization Supported with the following minimum versions of Exchange: Update Rollup 11 Exchange SP3 or later on all Exchange servers in the organization, including Edge Transport servers. Exchange Cumulative Update 10 or later on all Exchange servers in the organization, including Edge Transport servers. Network and directory server requirements for Exchange The following table lists the requirements for the network and the directory servers in your Exchange organization.
Note In multi-domain environments, on Windows Server 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. Note For older versions, see Exchange Server supportability matrix. In this article. Supported with Exchange CU11 or later on all Exchange servers in the organization, including Edge Transport servers.
Supported if all Exchange and Exchange servers in the organization meet the requirements as previously described in this table. 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. Exchange and later support IPv6 only when IPv4 is also installed and enabled on the Exchange server.
Either of the following types of bit processors: Intel processor that supports Intel 64 architecture formerly known as Intel EM64T. At least 30 GB of free space on the drive where you're installing Exchange. DLP capabilities help you protect your sensitive data and inform users of internal compliance policies. Smart Search learns from users' communication and collaboration behavior to enhance and prioritize search results in Exchange. Outlook Web App emphasizes a streamlined user interface that also supports the use of touch, enhancing the mobile device experience with Exchange.
The built-in malware filtering capabilities of Exchange helps protect your network from malicious software transferred through email messages. All messages sent or received by your Exchange server are scanned for malware viruses and spyware. With Exchange , users can merge contacts from multiple sources to provide a single view of a person, by linking contact information pulled from multiple locations.
Together, these products offer a suite of features that make scenarios such as enterprise eDiscovery and collaboration using site mailboxes possible. Exchange helps you to find and search data not only in Exchange, but across your organization. With improved search and indexing, you can search across Exchange , Lync , SharePoint , and Windows file servers. Exchange reduces the number of certificates that an Administrator must manage, minimizes the interaction the Administrator must have with certificates, and allows management of certificates from a central location.
Exchange readiness checks make sure that your computer and your organization are ready for Exchange deployment. Public folders now take advantage of the existing high availability and storage technologies of the mailbox store. The public folder architecture uses specially designed mailboxes to store both the hierarchy and the public folder content. This new design also means that there is no longer a public folder database. Exchange introduces the concept of batch moves, which allows the ability to move multiple mailboxes in large batches.
The new move architecture is built on top of MRS Mailbox Replication service moves with enhanced management capability. These improvements have pleased our customers because they've helped to make managing an Exchange organization easier than ever. For more information about the new features in Exchange , see What's New in Exchange Now that we've talked about the new features in Exchange , it's time to start the planning. To design a successful Exchange messaging system, you must first understand the capabilities of the software and hardware.
Specifically, you need to balance the limitations of your network infrastructure with the capabilities of your messaging system, operating system, and user software.
Planning and deployment. Active Directory.
0コメント