Exchange 2013 in the real world:from deployment to managementMichael Van Horenbeeck (@mvanhorenbeeck)

AgendaWhat you want things to look likeI…am…Frankenstein?How Exchange plays with the other kidsGotchas…? Anyone…?What just happened to my server?Q & A

AssumptionYou know what Exchange 2013 is and have heard about the new architecture paradigm…

FactIf you’re looking for more info, Channel 9 is the place to go!

Planning & Design

What you want things to look like…

Namespace Design - PAmail VIP

mail VIP

• For a site resilient datacenter pair, a single namespace / protocol is deployed across both datacenters– autodiscover.contoso.com– HTTP: mail.contoso.com– IMAP: imap.contoso.com– SMTP: smtp.contoso.com

• Load balancers are configured without session affinity, one VIP / datacenter

• Round-robin, geo-DNS, or other solutions are used to distribute traffic equally across both datacenters

Topology - PA

DAG

mail VIP

mail VIP

Witness Server

• Separate Active Directory Sites per physical site

• Deploy unbound DAG model spanning each DAG across two datacenters

• Active copies across all servers in the DAG

• Deploy 4 copies, 2 copies in each datacenter

• One copy will be a lagged copy (7 days) with automatic play down enabled

• Single network for replication and client traffic

• third datacenter for Witness server, if possible

Server Design - PA• Multi-role servers deployed on

commodity hardware• JBOD storage utilizing large

capacity 7.2K SAS disks• Multiple databases / volume• AutoReseed with hot spare

DAG

mail VIP

Selina(somewhere in

NA)DNS Resolution

DAG

na VIP na VIP

Batman(somewhere in Europe)

DNS Resolution

DAG

eur VIP

eur VIP

Preferred Architecturena.contoso.comeur.contoso.com

SummaryNew building block architecture provides flexibility in load balancing, namespace planning and high availabilityTake advantage of large, low-cost mailboxes by utilizing large capacity 7.2K RPM disksSimpler is better!

Deploying Exchange 2013

Preparing for Exchange 2013Active Directory Minimum RequirementsAt least one Windows Server 2003 SP2 or higher* Global Catalog in each AD site with Exchange installed*Use of Windows Server 2012 R2 requires a supported Exchange versionAt least one writable Domain Controller in each AD site with Exchange Servers installedAD Forest Functional Level must be Windows Server 2003 or higher

http://a

ka.ms/exchangesupportm

atrix

For the latest i

nformation se

e:

OS RequirementsWindows Server 2008 R2 SP1 Standard or Enterprise editionsStandard edition ok for CAS-only & non-DAG MBXEnterprise edition necessary for DAG joined MBX

Windows Server 2012 or 2012 R2 Standard or Datacenter editions2012 R2 is only supported with 2013 Service Pack 1 or later

OS Requirements.NET framework 4.54.5.1 strongly recommended

Windows Management Framework 3.0Unified Communications Managed API 4.0Other expected OS roles/features (IIS etc…)

Preparing for Exchange Server 2013

Recent Windows Server 2012 R2 Support Updates

2013 SP1 or later 2013 CU3 or earlier2010 SP3 RU5

or later2007 SP3 RU13

or later

Install on 2012 R2

2012 R2 DCs and a 2012 or lower DFL/FFL

2012 R2 DCs and a 2012 R2 DFL/FFL

Installing exchange 2013

Preparing for Exchange Server 2013

An OAB modification before installing the first Exchange 2013 servers:Exchange 2013 creates a new default OAB for the org.

Avoid clients downloading the new default OAB by specifying the existing OAB on all legacy DBs prior to installing Exchange 2013

[PS] C:\>Get-OfflineAddressBook | FT Name,IsDefault,ExchangeVersion -AutoSize

Name----Default Offline Address BookDefault Offline Address Book (Ex2013) True 0.20 (15.0.0.0)

False 0.1 (8.0.535.0)--------- ---------------

IsDefault Exchange Version

After Installation (SP1/CU4)The third-party or custom-developed transport agents cannot be installed correctlyYou cannot enable third-party products that rely on transport agentsThe Microsoft Exchange Transport service (MSExchangeTransport.exe) cannot start automaticallyYou receive an error message: The TransportAgentFactory type must be the Microsoft .NET class type of the transport agent factory

Problem occurs because global assembly cache (GAC) policy configuration files contain invalid XML codeHotfix and Fixit at http://aka.ms/KB2938053Download script from http://aka.ms/kb2938053DL

Slide courtesy of Scott Schnoll

Interoperability

MBX2013

CAS2013

Load Balancer

HTTP Proxy

IIS

DB

Protocol Head

HTTP

MBX2007

CAS2007

Load Balancer

IIS

DB

Middle Tier Layer

OWA Legacy Redirect Request

MBX2007

DB

Cross-Site OWA Proxy Request

CAS2007

IIS

Middle Tier Layer

Outlook Anywhere Proxy RequestActiveSync Proxy Request

Site

B

ou

nd

ary

CAS2013 Client Protocol Connectivity FlowExchange 2007 Coexistence

Slide courtesy of Microsoft

Ex2007 Coex: URL ConfigurationConfigure a legacy namespace for the ExternalURL values of the Exchange 2007 Virtual Directories (OWA, EWS, UM, OAB, EAS)Blank out the EAS Virtual Directory External URL if Exchange 2013 is deployed in the same site

* It doesn’t need to be legacy.yourdomain.com ;-)

http://a

ka.ms/exdeploy

One tool to

rule th

em all!

MBX2013

CAS2013

Load Balancer

HTTP Proxy

IIS

DB

Protocol Head

HTTP

Legacy Proxy Request

MBX2010

DB

Cross-Site Legacy Proxy Request

CAS2010

IIS

Middle Tier Layer

Load Balancer

Cross-Site OWA Redirect Request

Site

B

ou

nd

ary

MBX2010

CAS2010

Load Balancer

DB

Middle Tier Layer

IIS

CAS2013 Client Protocol Connectivity FlowExchange 2010 Coexistence

Slide courtesy of Microsoft

MBX

CAS

Load Balancer

HTTP Proxy

IIS

DB

Protocol Head

Local Proxy Request

HTTP

HTTP

Site

B

ou

nd

ary

MBX

CAS

Load Balancer

HTTP Proxy

IIS

DB

Protocol Head

HTTP

OWA Cross-Site Redirect Request

HTTP

MBX

DB

Protocol Head

HTTP

Cross-Site Proxy Request

HTTP

Site

B

ou

nd

ary

CAS

HTTP Proxy

IIS

CAS2013 Client Protocol Connectivity FlowEnd State

Slide courtesy of Microsoft

Managed Availability

What is ‘Managed Availability’?

“Exchange’s built-in monitoring and remediation center”

Probe Monitor Responder

Managed Availability ProbesProbes based on HealthSet Models:Client ProtocolsStorageMail FlowMigration“Fabric”

Retrieving Server HealthGet-HealthReport <server>Summarize the health of a server based on a worst-of evaluation of a HealthSet.

Get-ServerHealth <server> <-HealthSet>Get the per monitor state of a server.

DEMO

Managed Availability in a real-time production environment…

Q & A

Michael Van Horenbeeckmichael@vanhorenbeeck.beTwitter: @mvanhorenbeeckBlog: www.vanhybrid.com

ResourcesVarious slide decks from the Microsoft Exchange Conference:- http://

channel9.msdn.com/events/mec/2014

And take home the Lumia 1320

Present your feedback form when you exit the last session & go for the drink

Give Me Feedback

Follow Technet Belgium@technetbelux

Subscribe to the TechNet newsletteraka.ms/benews

Be the first to know

Belgiums’ biggest IT PRO Conference