MICROSOFT EXCHANGE 2013

Huy Pham[Title][FPT Corporation]

N I DUNGỘ Introduction Exchange 2013 Architecture Focus on CAS Focus on MBX Routing Mail (Mail Flow) Managing Exchange 2013

2

3

INTRODUCTION

INTRODUCTION

LICENSING EDITION

License Edition: Exchange Server 2013, Standard Edition Exchange Server 2013, Enterprise Edition.

Client Acess License (CALs): Standard CAL: offers standard e-mail functionality from any platform. The license is for typical Exchange and Outlook usage Enterprise CAL: offers functionality such as integrated archiving, compliance features, and information-protection capabilities.

The CAL is an add-on to the Standard CAL, so both licenses need to be purchased!

Don’t support for Outlook 2003 RPC/TCP access for Outlook clients Transport service integrated Unified Messaging service Managed folders Anti-malware

What’s Removed

5

What’s New and Removed

A new look and feel of client interfaces Exchange Admin Center (Web-based) Exchange Management Shell Exchange 2013 architecture:

Mailbox server role Client Access server role Managed store Managed availability Outlook Anywhere Anti-malware protection (EOP) “Modern” public folders Data loss prevention

What’s New

6

EXCHANGE 2013 ARCHITECTURE

EXCHANGE 2013 ARCHITECTURE

ACTIVE DIRECTORY PARTITION

Schema partition: Contain all objects and properties that are available

in Active Directory There is only one schema partition in the entire

Active Directory forest Exchange Server 2013 adds a lot of new objects and

attributes to Active Directory that make it possible to

gain functionality Configuration partition:

Contain all nonschema information is stored Information stored in the configuration partition is

Exchange Server information (accepted domain

information, Rule and policy information) Domain partition:

Contain all domain-specific information is stored User objects, contacts, and security and distribution

groups are stored in the domain partition

EXCHANGE 2013 ARCHITECTURE

InternetAD

Web browser

Outlook (remote user)

Mobile phone

Line of business application

Outlook (local user)

ExternalSMTP

servers

Enterprise Network

Phone system (PBX or VOIP)

Laye

r 4LB

CAS

CAS

CAS

CAS

CAS

CAS Array

MBX

MBX

MBX

MBX

MBX

DAGExchange building blocks

Client Access Server comprises of client protocols and SMTP

Mailbox Server hosts all components to process, render and store data

Edge TransportRouting and AV/AS

LOAD BALANCING

With Exchange 2010: Configuration on a KEMP Load Balancer was quite

simply and easily accomplished. You can use the Exchange templates provided by KEMP,

or perform the configuration manually, The requirement: one for RPC/MAPI, one for HTTPS

(443), optionally redirection for HTTP (80) requests to HTTPS (443).

With Exchange 2013: Layer 4 Virtual Service for traffic coming in for

HTTPS (443) and Round Robin Just only Layer 7 load balancing have ability perform

health checking for individual Exchange 2013 web

services and to take advantage of intelligent features

KEMP Load Balacing

Stateless

10

FOCUS ON CAS

CAS 2013

The CAS in itself does not perform any processing with respect to mail data

If a CAS goes, all connected clients need to re-authenticate against another Client Access serverReceive request from Internet to the CAS is using the regular port 443, but that the proxied request to the Mailbox server is using port 444

Multiple CAS just only handle workloads, not relative with Load-Balancing solutions

The Client Access server comprises three different components: Client access protocols (HTTP, IMAP4, POP3) SMTP UM call router

CLIENT ACCESS SERVER 2013

The Death of RPC/TCP

The HTTPS connection is then terminated on the

Mailbox server— on IIS on the Mailbox server, and

the AppPool on the back end decapsulates the RPC

traffic from the HTTPS stream

Since the Outlook clients now connect to the

correct Mailbox server, it is no longer necessary to

use the RPC Client Access server array

Exchange 2010: The FQDN of the CAS array was also the server name that was visible in the Outlook profile.

Exchange 2013: The FQDN being used in the Outlook profile has been replaced with the mailbox GUID

CLIENT ACCESS SERVER 2013

Autodiscover

Autodiscover works by an XML request sent from the Outlook client to the Client Access server.

The Client Access server then accepts the request and proxies it to the Mailbox server. The Mailbox server gathers all the required information and returns this as an XML package to the Outlook client.

The request is sent once an hour to determine if there are any changes in the Exchange configuration

When a Client Access server is installed, a service connection point is also created in Active Directory

A service connection point has a GUID (Global Unique Identifier)

CLIENT ACCESS SERVER 2013

Load Balacing

With a layer-4 load balancer, the load balancing takes place on the network layer. An incoming connection is accepted and distributed across multiple Exchange 2013 Client Access servers

The Client Access server in turn accepts the connection, and after authentication, the connection is forwarded to the appropriate Mailbox server.

If one service on the Exchange 2013 Client Access server fails, the load balancer only detects that the Client Access server in general has failed and will initiate a fail-over to another Client Access server

CLIENT ACCESS SERVER 2013

Routing Mail

With a layer-4 load balancer, the load balancing takes place on the network layer. An incoming connection is accepted and distributed across multiple Exchange 2013 Client Access servers

The Client Access server in turn accepts the connection, and after authentication, the connection is forwarded to the appropriate Mailbox server.

If one service on the Exchange 2013 Client Access server fails, the load balancer only detects that the Client Access server in general has failed and will initiate a fail-over to another Client Access server

16

FOCUS ON MBX

MAILBOX SERVER 2013

One Exchange 2013 Enterprise Mailbox server can host up to 100 mailbox databases

When you install a Mailbox server, a new mailbox database is automatically created on the boot- and system disk (C:\)

The recommended maximum database size for a normal Exchange 2013 Mailbox server is 2TB (Up to 16TB) when you have multiple copies of the mailbox database

E01 (transactional processing of information) E00.chk (a checkpoint file that keeps track of the

transactions still in the log files) E01res00001.jrs - E01res0000A.jrs (are temporary log

files reserved by Exchange Server in case of disk-full problems)

E01tmp.log

MAILBOX DATABASE

MAILBOX SERVER 2013

For every mailbox database that is mounted on an Exchange 2013 Mailbox server, a new Information Store worker process is spawned and responsible for this particular database

If you have an Exchange 2013 Mailbox server with 25 mailbox databases mounted, and one of those databases crashes, including the Information Store, the other 24 mailbox databases are not affected

Microsoft Exchange Information Store

MAILBOX SERVER 2013

Called “the public folder mailbox” The public folders are now stored in mailbox databases The public folders consisted of two parts: Hierarchy

and Content. Exchange Server 2013

The hierarchy: is now stored in a new type of mailbox “the public folder mailbox”

The Content: contain all public folders

PUBLIC FOLDER 2013

20

Routing Mail

EXCHANGE 2013

MAIL FLOW

Front End Transport service (On CAS) Transport Service (On Mailbox Server) Mailbox Transport Service (On Mailbox Server):

Mailbox Transport Submission Service Mailbox Transport Delivery Service

THE TRANSPORT PIPLELINE

22

MANAGING

EXCHANGE 2013

MANAGING EXCHANGE 2013

Exchange Management Shell (EMS) Exchange Toolbox

Details Templates Editor Remote Connectivity Analyzer Queue Viewer

Management Tasks Managing SSL Certificates: http://

support.microsoft.com/kb/929395 Managing Contacts and Mail-Enabled Users Patch Management

XIN CÁM ƠN