Major changes with Exchange Server 2013 - Part 1

This is the documentation for the Online discussion we conducted on Major changes with Exchange Server 2013.

Recording of this session is available on

Here we discussed about.

 PART 1 of 2
Changes in Exchange Architecture
What is Exchange Admin Center? 
Changes in Information Store
Changes in Certificate Management
Changes in Messaging Policy and Compliance
Changes in Anti-malware protection
Changes in Transport Rules
Changes in Mail Flow
Changes in Recipient Management

Changes in Exchange Architecture
 Exchange 2013 Server Roles
  1. Client Access Server role
  2. Mailbox Server role.
 HT, UM and Edge Role didn’t make to 2013
  1. The Mailbox server handles all activity for a given mailbox.
  2. This Architecture changes brings changes with client connectivity.
  3. No more RPC
  4. Clients not longer connects to Server FQDN
  5. Only Outlook 2007 and higher versions are supported
 Later we talked about Exchange Admin Center? 

Major changes in Information Store
 Managed Store
  1. Newly rewritten Information Store processes, Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe.
  2. Each database runs under its own process, allowing for isolation of store issues to a single database.
  3. Tightly integrated with MSExchangeRepl.exe to provide higher availability through improved resiliency.
  4. Public Folder Database no longer exist.
  5. Exchange 2013 it supports up to 100 GB of Mailbox size, with OL2013 OST file size can be controlled.
  6. Exchange 2013 Enterprise Edition can only mount 50 databases on a mailbox server
 Major changes in Certificate Management
  1. Certificate management functionality is provided in the Exchange Administration Center.
  2. All certificate management is performed on the Client Access server.
  3. Notifications center will display warnings when a certificate stored on any Exchange 2013 Preview Client Access servers is about to expire.
  4. The Client Access server automatically trusts the self-signed certificate on the Exchange 2013 Mailbox server, provided that the Exchange 2013 Client Access server has a non-self-signed certificate from either a Windows certificate authority (CA) or a trusted third party.
 Major changes in Messaging Policy and Compliance
  1. Data loss prevention (DLP)
  2. In-place Archiving, retention, and eDiscovery
  3. In-Place Hold   
  4. In-Place eDiscovery
  5. Search across primary and archive mailboxes in Outlook Web App
  6. Archive Lync content
  7. Retention policies
  8. Transport rules
  9. Information Rights Management
  10. Protects sensitive emails from unauthorized access.
 Major changes in Transport Rules
  1. New predicates are added to Exchange 2013 preview transport files in order to
  2. Detect sensitive information from message body and attachments.
  3. Detect messages sent from specific ip ranges.
  4. Detect messages with specific extensions
  5. Detect messages that contain attachments with executable content.   
  6. New Actions are added in order to :
  7. Controls how the sender of a message that goes against a DLP policy is notified.
  8. Stops the processing of all subsequent rules on the message.
  9. Requires TLS encryption when routing this message outside your organization.
 Major changes in Anti-malware protection
  1. Builtin Antimalware protection
  2. If malware is detected, the message is deleted.
  3. You can also choose to replace infected attachments with either default or custom messages that notify the recipients of the malware detection.
  4. You can also use a third-party anti-malware protection program. In this case, you may want to disable the built-in anti-malware protection
  5. Enable-Antimalwarescanning.ps1 and Disable-Antimalwarescanning.ps1
  6. Update-MalwareFilteringServer.ps1
  7. Each server checks for new malware definitions every hour.
  8. The default anti-malware policy controls your company-wide malware filtering settings. As an administrator, you can view and edit, but not delete, the default anti-malware policy
 Major changes in Changes in Mail Flow
The Mailflow in Exchange 2013 is made up of several different services:
  1. Front End Transport service on Client Access servers
  2. Hub Transport service on Mailbox servers
  3. Mailbox Transport service on Mailbox servers.
 Front End Transport service
 This service runs on all Client Access servers and acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange 2013 organization.

Mailbox Transport service
 This service runs on all Mailbox servers and consists of two separate services
  1. Mailbox Transport Submission service
  2. Mailbox Transport Delivery service
  • Mailbox Transport Delivery service receives SMTP messages from the Hub Transport service, and connects to the mailbox database using an Exchange remote procedure call (RPC) to deliver the message.
  • Mailbox Transport Submission service connects to the mailbox database using RPC to retrieve messages, and submits the messages over SMTP to the Hub Transport service.
  • Mailbox Transport service doesn't queue any messages locally as it is a stateless service.
 Hub Transport service
  1. This service runs on all Mailbox servers and is virtually identical to the Hub Transport server role in previous versions of Exchange.
  2. Handles all SMTP mail flow for the organization, performs message categorization, and performs message content inspection.
  3. Routes messages between the Mailbox Transport service, the Hub Transport service, and the Front End Transport service.
 Messages from outside the organization
  1. Enter through a Receive connector in the Front End Transport service on a Client Access server
  2. Then routed to the Hub Transport service on a Mailbox server.
  3. The Transport service on a Mailbox server never communicates directly with a mailbox database.
  4. Transport service communicates with the Mailbox Transport service on the Mailbox server.
  5. Mailbox Transport service communicates with the mailbox database on the local Mailbox server.
Exchange 2013 Mail Routing is 100% DAG aware.
When the Mailbox server is a member of a DAG, only the Mailbox Transport service on the Mailbox server that holds the active copy of the mailbox database accepts the message for the destination recipient.

Usage of RPC in Mail Routing
  1. RPC is never used for cross-server communication.
  2. Remote procedure calls (RPCs) are only used by the Mailbox Transport service when sending messages to or receiving messages from the local mailbox database.
  3. When the Mailbox server is a member of a DAG Mailbox Transport service only uses RPCs to communicate locally with the active copies of the mailbox databases.
  4. Mailbox Transport service and the Transport service on different Mailbox servers always communicate using SMTP.
 Improvement in Message Queuing
  1. Exchange 2013 uses more precise queuing for remote destinations.
  2. Instead of using one queue for all destinations in a remote Active Directory site, Exchange 2013 queues messages for specific destinations within the Active Directory site, such as individual Send connectors.
  3. Linked connectors have been deprecated. A linked connector was a Receive connector that was linked to a Send connector. All messages received by the Receive connector were automatically forwarded to the Send connector.
 Brief overview of Mail Flow
 Transport Pipeline: 
  1. Front End Transport service on Client Access servers
  2. Hub Transport service on Mailbox servers
  3. Mailbox Transport service on Mailbox servers.  
  1. Recognizes DAG boundaries
  2. Recognizes AD Site boundaries
  3. Improved Queuing
  1. The default maximum message size for a Send connector or a Receive connector has been increased from 10MB to 25MB.
  2. You can set a Send connector in the Transport service of a Mailbox server to route outbound mail through a Front End transport server in the local Active Directory site.
 Edge Transport: 
  1. Currently, there isn’t an Exchange 2013 version of the Edge Transport server. Supports 2010 and 2007 version also can use Third Party Solution.
 Major changes in Recipient Management

Group naming policy
  1. Administrators can now use the EAC to create a group naming policy, which lets you standardize and manage the names of distribution groups created by users in your organization.
  2. You can require a specific prefix and suffix be added to the name for a distribution group when it's created
  3. You can block specific words from being used. This capability helps you minimize the use of inappropriate words in group names.
 Auditing reports
  1. The EAC includes auditing functionality so that you can run reports or export entries from the mailbox audit log and the administrator audit log.
  2. The mailbox audit log records whenever a mailbox is accessed by someone other than the person who owns the mailbox.
  3. The administrator audit log records any action, based on an Exchange Management Shell cmdlet, performed by an administrator.
 Message Tracking
  1. Administrators can also use the EAC to track delivery information for email messages sent to or received by any user in your organization.
  2. You just select a mailbox, and then search for messages sent to or received by a different user.
  3. You can narrow the search by searching for specific words in the subject line.
  4. The resulting delivery report tracks a message through the delivery process and specifies if the message was successfully delivered, pending delivery, or if it wasn't delivered.
 Please find the slides as attached.
 Thanks you all for spending your valuable time.


Microsoft Exchange Server 2013 - PART 1.pdf