Informações do Produto

Managed availability Managed availability is a monitoring and recovery infrastructure that is integrated with Exchange’s high availability solution. Managed availability detects and recovers from problems as they occur and as they are discovered. Data loss prevention (DLP) DLP features include a robust set of transport rule–like tools for scanning messages for sensitive data, a predefined set of policies for common regulatory requirements, and tools for customizing the included items or building your own. E-discovery experience You can now perform discovery searches that include Exchange mailboxes Public folders Archived Microsoft Lync conversations Material that’s stored in Microsoft SharePoint from a single SharePoint-based interface. Mailbox Server Changes ____________________ Exchange Replication service _____ Controls failover and switchover operations and database mounts and dismounts, manages the database worker processes. Failure of the Information Store service process affects only one database at a time. Improved Exchange 2013 schema _____ By increasing the degree of physical and logical contiguity in the Exchange 2013 schema, fewer large I/Os will be required — but an increased amount of CPU will be needed to handle them. AutoReseed feature _____ The new Store also implements a new AutoReseed feature. This feature can immediately create a new passive replica of a database on a failed disk by using a spare disk on the server, automatically replacing the failed copy to maintain the correct number of copies in the database availability group. Completely re-implemented public folders _____ Public folders essentially look and act like databases. Public folder databases are stored in DAGs, just as mailboxes are, so you protect public folders against outages by adding multiple replicas of a given public folder database to a DAG. Clients always connect to the active copy of the public folder, which might have implications for scalability in some environments. Client Access Changes ____________________ Proxy connections Exchange 2013 no longer renders data for the client. The only thing it does is perform proxy connections from the client to the appropriate Mailbox server. This proxy-only design eliminates the need for the Client Access server to maintain affinity or state with clients, which in turn enables a much broader range of potential load-balancing solutions. Client access protocols Client connections can use IMAP, POP, or Exchange Web Services (EWS), but they no longer use Messaging API (MAPI) RPCs. Cross-site access Clients connect to whichever Client Access server is convenient, and the Client Access server can perform HTTP redirects as necessary to find the correct Mailbox server across Active Directory (AD) sites. Transport Changes The transport process has changed significantly because of the two-role architecture. ____________________ The new Front End Transport service has a completely new approach to mail acceptance and delivery: It has no permanent queues. When a new SMTP conversation is opened, the service accepts the connection, performs filtering based on the SMTP envelope data, and then determines the route to the “best” Mailbox server before starting the delivery process. The Mailbox server runs three new transport-related services: The Mailbox Transport Service The Mailbox Transport Delivery Service The Mailbox Transport Submission Service