1. Understand the general company size, number of offices and office locations, and the industry that the business operates in.Understand the general company size, number of offices and office locations, and the industry that the business operates in. Determine if the customer already has an HA solution in place. If they do, bring content focused on how we are better then the other vendor. Also determine the version of Exchange that they are using.Determine if the customer already has an HA solution in place. If they do, bring content focused on how we are better then the other vendor. Also determine the version of Exchange that they are using. Determine if the customer is interested site resiliency and or if they currently have a site resiliency solution / plan in place.Determine if the customer is interested site resiliency and or if they currently have a site resiliency solution / plan in place. Prepare for the ADS What to bring with you to a presentation, and what to find out beforehand

2. NameTitleMicrosoft Exchange High Availability Solution Architecture Design Session

3. Solution Overview Technology Overview Point out technologies for relevant capabilities Discuss technologies Architecture Discussion Discuss Architecture Decision Points POC Planning Develop scope and specifications for POC VPC-based demo Web –based demo View the capabilities in action Show various possibilities Vision scope input from solution briefing Solution Briefing Summary

4. Architecture Design Session Vision scope input from solution briefing Solution Briefing Summary

5. Service downtime disrupts business operations and reduce productivity Achieving high availability for all types of communication is expensive Protection against Site-level Disasters Challenges Presenter: Complete this section prior to the presentation. Confirm and verify that you’re still tracking with the customer’s challenges, drivers and the capabilities from the SB. Meeting stringent SLAs Accelerate productivity Ensure business continuity Reduce IT cost Business Drivers Summary of Pains and Drivers Technical Requirements Easy to Deploy and Manage Deliver a high-value hosted continuity service Provide IT control with failover, redundancy, and scalability across your organization

6. Architecture Design Session Solution Overview Vision scope input from solution briefing Solution Briefing Summary VPC-based demo Web –based demo View the capabilities in action Show various possibilities

7. Authentication Administration Storage Compliance Authentication Administration Storage Compliance Audio Conferencing E-mail and Calendaring E-mail and Calendaring Web Conferencing Web Conferencing Telephony Video Conferencing Video Conferencing Voice Mail Instant Messaging (IM) Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Telephony and Voice Mail Telephony and Voice Mail Instant Messaging E-mail and Calendaring Unified Conferencing: Audio, Video, Web On-Premises or in the Cloud Communications Today

8. Streamline Communications Amplify Protection and Control Provide a Unified and Extensible Platform Across DevicesPC, Mobile, Web Increase Efficiency and Flexibility Maximize IT Resources with S+S Authentication Administration Storage Compliance Authentication Administration Storage Compliance Unified Identity, Presence, and Inbox On-Premises or in the Cloud Microsoft Unified Communications Increased productivity through communications convergence

9. ScenariosScenarios ProductsProducts On Premise Hosted by Microsoft DeliveryDelivery IM and Presence Unified Messaging E-Mail and Calendaring VoIP Mobility Hosted by Microsoft or by Partners Hosted by Partners Microsoft UC Products and Services Conferencing

10. UC Journey Through Infrastructure Optimization identify where you are identify where you want to be Basic e-mail, file shares, mostly phone based communication Standard platform for secure e-mail and IM Ad hoc teaming around functions & projects based on IT standards Increasing unification of communication channels Fully managed collaboration platform and pervasive access Seamless collaboration across the firewall Federation of communication information and policy IT is a strategic asset IT is a business enabler IT is an Efficient cost center IT is a cost center

11. Identifying Target Maturity Level IM & Presence Voice Conferencing Messaging Work with your customer to agree on where they are and where they want to be. This portion of the presentation will fail if it is not interactive. Use the highlight boxes to show each stage (where they are, where they want to be) Legacy TDM PBX, traditional phones Limited voice mail and call routing Highly available hybrid telephony infrastructure Online & offline access to voice mail Managed call routing Encrypted voice infrastructure with unified inbox accessible from PCs, phones, & web browsers Managed storage Presence-based call routing Integrated voice platform for IM/presence; conferencing with LOB applications Auto-remediation, proactive monitoring of call quality Federated identity and presence-based call routing Rich mailbox & calendaring Secure, remote, online & offline access Basic AV/AS/AP protection and disaster recovery Solution supports encryption Business continuity with AS/AP and multi-layer AV protection Support advanced policy- driven message controls Provisioning for user inboxes Basic email with no remote access and with limited security Minimal or decentralized IT support User inboxes are fully managed by IT Seamless business continuity with multiple AV/AS protection Advanced policy control to mobile devices & applications Integration with LOB applications Federation of calendar Public IM/online presence, ad-hoc use for daily business Secure access from inside & outside the firewall Supports peer-to-peer voice & video communications Presence enabled email client Secure IM/online presence accessible from a variety of devices and integrated into enterprise productivity & collaboration platform Persistence group chat Supports federation and integration with LOB applications Sporadic use of audio & web conferencing Limited video conferencing capabilities Integrated & secure conferencing platform Supports high-quality audio & video Remotely accessible collaboration features Secure web conferencing accessible from remote locations and devices IT-managed video conferencing with limited remote access Contextual unified conferencing solution tightly integrated with collaboration infrastructure and LOB applications

12. High Availability

13. Unified Communication High Availability Overview Exchange High Availability technologies 1. Primarily designed to protect Exchange mailbox data (Mailbox server role) 2. Add redundancy to provide HA for service roles (UM, CAS, HT, Edge) 3. Remember that: 1. High Availability is automatic failovers 2. Site Resilience is manual failovers!

14. Exchange Server 2010 High Availability Goals Reduce complexity Reduce cost Native solution - no single point of failure Improve recovery times Support larger mailboxes Support large scale deployments

15. Exchange Server Improvements Improved mailbox uptime More storage flexibility Better end-to-end availability Online mailbox movesOnline mailbox moves Improved transport resiliencyImproved transport resiliency Further Input/Output (I/O) reductionsFurther Input/Output (I/O) reductions RAID-less/JBOD supportRAID-less/JBOD support Improved failover granularityImproved failover granularity Simplified administrationSimplified administration Incremental deploymentIncremental deployment Unification of CCR + SCRUnification of CCR + SCR Easy stretching across sitesEasy stretching across sites Up to 16 replicated copiesUp to 16 replicated copies Easier and cheaper to deploy Easier and cheaper to manage Better Service Level Agreements (SLAs) Reduced storage costs Larger mailboxes Key Benefits Easier and cheaper to manage Better SLAs

16. Lync Server 2010 High Availability and Resiliency Goals Reduce complexity Reduce cost Native solution - no single point of failure Resilient Voice Service Support large scale deployments High Availability Resiliency architecture Branch office resiliency Data Center resiliency

17. Architecture Design Session Solution Overview Technology Overview Point out technologies for relevant capabilities Discuss technologies Vision scope input from solution briefing Solution Briefing Summary VPC-based demo Web –based demo View the capabilities in action Show various possibilities

18. Enterprise Network External SMTP servers Edge Transport Routing and AV/AS Phone system (PBX or VOIP) Client Access Client connectivity Web services Hub Transport Routing and policy Web browser Outlook (remote user) Mobile phone Outlook (local user) Line of business application Mailbox Storage of mailbox items Unified Messaging Voice mail and voice access Exchange Server 2010 Deployment Model Role based Deployment

19. Exchange High Availability Technologies Continuous Replication technology Leverages on-site data replication (CCR) and off-site data replication (SCR) and combines into a single framework called a “Database Availability Group.” Removes the need of managing Failover Clustering separately Reduces the need for multiple servers to achieve high redundancy in small deployments – Two Servers can provide full redundancy Simplified recovery from a variety of failures (disk-level, server-level, and datacentre-level) Can be deployed with cheaper storage types Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 Mailbox Server 4 Mailbox Server 16

20. Exchange High Availability Technologies Mailbox Resiliency Evolution of Continuous Replication technology Provides full redundancy of Exchange roles on as few as two servers Reduce backup frequency through up to 16 replicas of each database Single solution for High Availability, Disaster Recovery, and Backup Simplified administration reduces complexity Built-in features for mailbox recovery Improved availability Can be deployed on a range of storage options DB1 DB3 DB2 DB4 DB5 Recover quickly from disk and database failures DB1 DB2 DB4 DB5 DB3 DB1 DB2 DB4 DB5 DB3 Replicate databases to remote datacenter San JoseNew York

21. Exchange High Availability Technologies Mailbox Resiliency Overview AD site: Dallas Clients connect via CAS servers DB2 DB3 DB1 DB4 DB5 DB1 DB2 DB3 DB4 DB5 DB1 DB2 DB3 DB4 DB5 DB1 DB3 DB5 DB1 AD site: San Jose Failover managed within Exchange Easy to stretch across sites Database - centric failover

22. Exchange High Availability Technologies Mailbox Resiliency Components Database Availability Group (DAG) Mailbox Servers Mailbox Database Copies Active Manager RPC Client Access Service Active Manager Client DB2 DB1 DB2 DB3 DB1 DB2 DB3 DB1 Active Manager RPC Client Access Service DB3 AM Client Database Availability Group

23. Exchange High Availability Technologies DAG (Database Availability Group) & Mailbox Servers Mailbox Servers Host the active and passive copies of multiple mailbox databases Support up to 100 databases per server Database Availability Group DB2 DB1 DB2 DB3 DB1 DB2 DB3 DB1 DB3 Database Availability Group A group of up to 16 mailbox servers that host a set of replicated databases Wraps a Windows® Failover Cluster Defines the boundary of replication and failover/ switchover (*over)

24. Exchange High Availability Technologies Mailbox Database Copies Database names are unique across an forest Up to 16 copies of each database Each database has one Active copy in a DAG Each server hosts only one copy of a database Replication using Log Shipping System tracks health of each copy

25. Exchange High Availability Technologies Continuous Replication Database behind on logs (e.g Server Reboot) Database available for log replication Continuous Replication – File Mode Continuous Replication – Block Mode ESE Log Buffer Replication Log Buffer X

26. Exchange High Availability Technologies Active Manager Selects the “best” copy to activate when the active mailbox database fails 30-second database failover Process which runs on every server in DAG Provides definitive information on where a database is active and mounted Active Directory ® is primary source for configuration information Active Manager is primary source for changeable state information such as active and mounted Active Manager Client runs on CAS and HUB Servers

27. Exchange High Availability Technologies Achieving double resiliency Single Site 4 Nodes in a DAG 3 Database Copies Database Availability Group (DAG) DB2 DB3 DB5 DB4 DB7 DB8 DB1 DB2 DB3 DB4 Mailbox Server 1 DB5DB6 DB7 DB8DB1DB2 Mailbox Server 2 Mailbox Server 3 CAS NLB Farm DB3DB4 DB5 DB6 DB7 DB8 Mailbox Server 4 DB1 DB6 Upgrade server 1 Server 2 fails Server 1 upgrade is done 2 active copies die

28. Exchange High Availability Technologies Resiliency across datacenters - Built-in site resiliency Same deployment and management tools as High Availability in a single datacenter No stretched subnet networking requirements Improved process to prevent “Split Brain” Database Availability Group Simplified standby datacenter validation Faster datacenter switchover process Fewer resources required for datacenter resiliency No Client re-configuration required to access databases in standby datacenter Support for 2 node datacenter resilient topologies Two node DAGs can use Datacenter Activation Coordination (DAC) mode DAC mode available to single site configurations

29. Easy to add high availability to existing deployment High availability configuration is post-setup Database Availability Group Datacenter 1 Datacenter 2 DB2 DB3 DB1 DB2 DB3 DB1 DB2 DB3 DB1 Mailbox servers in a DAG can host other Exchange 2010 roles Exchange High Availability Technologies Incremental Deployment - Reduces cost & complexity

30. Exchange High Availability Technologies RPC Client Access Server MAPI clients e.g. Microsoft Office Outlook connecting from inside the Organization Firewall no longer connects to Mailbox Server MAPI clients connects to Client Access Server for mailbox and directory access Client Access Server Array to be deployed to provide high availability and redundancy Provides a better client experience when failover occurs Allows a higher number of concurrent connections and a higher number of mailboxes per server MBX Exchange CAS Array Outlook Clients GC

31. High Availability During Failures Keeping users connected Mailbox Database or Server failure….. Client disconnected for <30 seconds Mailbox Database or Server failure….. Client disconnected for <30 seconds Client DB2 DB3 Load Balanced Client Access Servers Client Access Server failure….. Client reconnects through another Client Access Server Client Access Server failure….. Client reconnects through another Client Access Server DB1 DB2 DB3 Mailbox Servers Database Availability Group DB1

32. High Availability During Moves Keeping users connected Email Client Mailbox Server 1Mailbox Server 2 Client Access Server Users remain online while their mailboxes are moved between servers Sending messages Receiving messages Accessing entire mailbox Administrators can perform migration and maintenance during regular hours

33. Exchange High Availability Technologies Transport Resiliency Provides resilience and simplifies recovery from a transport server failure Provide redundancy for messages for the entire time they're in transit Message in Transport Database gets deleted only after it verifies that all of the next hops for that message have completed delivery Easy maintenance of Hub Transport or Edge Transport server Eliminates the need for storage hardware redundancy for transport servers Message flow with shadow redundancy

34. High Availability - Email in transit Automatic protection against loss of queued email due to hardware failure Simplifies Hub and Edge Transport Server upgrades and maintenance Servers keep “shadow copies” of items until they are delivered to the next hop

35. Exchange High Availability Technologies Backup Using Exchange 2010 Fast Recovery Data Retention Fast recovery Data redundancy Fast recovery Data redundancy Guaranteed item retention Past point-in-time database recovery Secondary mailbox for older data Reason for Backup Recovery Feature Exchange 2010 Feature Benefit Exchange 2010 Feature Benefit

36. Exchange High Availability Technologies Exchange Hosted Services Continuity Offsite, Microsoft-maintained business continuance 30-day rolling archive of online email stored offsite Full Web and Outlook access Message archive is encrypted and only accessible to authorized users Automated failover when your site goes down Multiple vendors used for message hygiene

37. Exchange High Availability Simplified Administration - Reduces cost & complexity High Availability administration all within Exchange 2010 Exchange Management Console for common tasks Exchange Management Shell (PowerShell) Mailbox Databases managed at Organizational Level Same automated database failover process used for a range for failures—disk, server, network Simplified activation of Exchange 2010 services in a standby datacenter Additional Tools provided to simplify management Active mailbox database redistribution DAG Maintenance Mode Single Copy Alert Failover Metrics Reporting (Improved) DAG property page supports static IP address specification

38. Exchange High Availability Simplified Administration – Managing Availability 1 1 2 2 3 3 Select a database View locations and status of replicated copies Take action (add copies, change master, etc.)

39. Architecture Design Session Solution Overview Technology Overview Point out technologies for relevant capabilities Discuss technologies Architecture Discussion Discuss Architecture Decision Points Vision scope input from solution briefing Solution Briefing Summary VPC-based demo Web –based demo View the capabilities in action Show various possibilities

40. Notes To Presenter The slides that follow are based on three primary deployment scenarios centered around company sizes and complexities. You should chose the appropriate slides for your customer. The small site customer has only a few servers all located in one physical location The medium site customer has more servers than a small site customer; these servers may also be located in more than one physical location The large site customer has more servers than a medium site customer and those servers are located in more than one physical location. Often the large site customer will have locations that are of data center quality, and located in different geographical regions of the same, or of different countries.

41. High Availability Scenarios Small Deployment IT assets are located at a single site. Customers has requirement of higher uptime with lower cost. Additionally the customer has the following concerns: Protection against Server/Disk failure Protection against Database failure Connection failure – Consider where messages go if you are offline Data loss – Consider the impact of lost messages, Archiving and regulatory impact of retention Site loss – Plan for site failure, what do you need to recover?

42. High Availability Scenarios Medium Deployment IT assets are located at a number of different sites. The customers has high uptime requirements. Additionally the customer has the following concerns: Protection against Server/Disk failure Protection against Database failure Connection failure – Evaluate redundant links, and routing impacts Data loss – Consider site replication, Archiving and offsite backup requirements Site loss – Consider a hosted standby, or site replication

43. High Availability Scenarios Large Deployment IT assets are located at a number of different sites often times in data centre-grade facilities. The customer has high uptime requirements. Additionally the customer has the following concerns: Server failure – Implement DAG with extended nodes in other sites Connection failure – Have redundant links to the internet and between sites Data loss – Consider site replication, Archiving and offsite backup requirements Site loss – Create site failover plans

44. Architecture Decision Points Current High Availability technologies Current Infrastructure Future High Availability needs and goals Future Infrastructure Basic deployment planning Deployment

45. Architecture Decision Points Current Infrastructure What are the currently implemented high availability technologies? What is the current network and office topology? What are the company drivers and requirements for high availability? What are the current site resiliency goals?

46. Architecture Decision Points Future Infrastructure What are the future plans for the network and office topology? What are the expansion expectations for the next six months, a year, two years, and five years? What level of high availability is needed? Does everyone need the same level of service? How will you address business continuance/site loss? Do you want to do it all in-house or outsource some of or all of it?

47. Architecture Decision Points Deployment How can you prepare now to meet your future high availability needs? Will you upgrade existing systems or implement all new systems? Exchange rely on Active Directory so it needs to be made highly available as well Exchange Hosted Services provides a quick, easily implemented HA solution for site loss and business continuance DAG spanned to multiple nodes and multiple hub and CAS servers for Microsoft Exchange

48. Architecture Design Session Solution Overview Technology Overview Point out technologies for relevant capabilities Discuss technologies Architecture Discussion Discuss Architecture Decision Points POC Planning Develop scope and specifications for POC Vision scope input from solution briefing Solution Briefing Summary VPC-based demo Web –based demo View the capabilities in action Show various possibilities

49. POC Planning Sponsor Name Project Timing Goals and Objectives ScopeMilestones Risks & Dependencies

50. Next Steps Proof of Concept Assemble resources from the business side and from the IT group Understand business processes that are being addressed Gain knowledge about technology infrastructure Verify the technology roadmap Review the POC scope and assumptions Proof of Concept Architecture Design Session Solution Briefing Solution Development

51. © 2007 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

52. Appendix Slides…

53. Exchange High Availability Technologies Creating Redundant Environment Multiple Unified Messaging Servers can be deployed in a dial plan to achieve the resiliency and high availability IP Gateways can be set up to route calls in a round-robin manner to balance the load between multiple UM servers in a dial plan and detect UM server failure Multiple Edge Transport Servers can be deployed to provide redundancy and failover capabilities Multiple HUB Transport Servers can be deployed to provide redundancy and load distribution Multiple Client Access Servers can be deployed in Client Access Array to provide redundancy and prevents single Points of failures Create Database Availability Group (DAG) with multiple copies of database Create Database Availability Group (DAG) that span multiple Mailbox servers

54. Lync Server High Availability Technologies Creating Redundant Environment Instant Messaging Enterprise Edition: Multiple Front-End Server, Array of Edge Servers Web Conferencing Enterprise Edition: Multiple Front-End Servers, Array of Edge Servers Voice Multiple Mediation Servers and Gateways Multiple voice routes Web Based IM/PA Load balance multiple Exchange 2010 CAS Servers Monitoring Server Clustered SQL database Archiving Server Clustered SQL database Persistent Group Chat Multiple Group Chat Servers in a pool

55. Best Copy Selection – Exchange 2010 SP1 Sorts copies by activation preference when auto database mount dial is set to Lossless Otherwise, sorts copies based on copy queue length, with activation preference used a secondary sorting key if necessary Selects from sorted listed based on which set of criteria met by each copy Attempt Copy Last Logs (ACLL) runs and attempts to copy missing log files from previous active copy

56. Four copies of DB1 DB1 currently active on Server1 Auto database mount dial set to Lossless DB 1 Server1 Server2 Server3 Server4 DB 1 X Best Copy Selection – Exchange 2010 SP1

57. Sort list of available copies based by Activation Preference: Server2\DB1Server3\DB1Server4\DB1 Lowest preference value – tried first Best Copy Selection – Exchange 2010 SP1

58. Datacenter Activation Coordination Mode RTM: DAC Mode is only for DAGs with three or more members that are extended to two Active Directory sites Don’t enable for two-member DAGs where each member is in different AD site or DAGs where all members are in the same AD site DAC Mode also enables use of Site Resilience tasks Stop-DatabaseAvailabilityGroupRestore-DatabaseAvailabilityGroupStart-DatabaseAvailabilityGroup SP1: DAC Mode can be enabled for all DAGs

59. Improvements in Service Pack 1 Replication and Copy Management enhancements in SP1

60. Improvements in Service Pack 1 Continuous replication changes Enhanced to reduce data loss Eliminates log drive as single point of failure Automatically switches between modes: File mode (original, log file shipping) Block mode (enhanced log block shipping) Switching process: Initial mode is file mode Block mode triggered when target needs Exx.log file (e.g., copy queue length = 0) All healthy passives processed in parallel File mode triggered when block mode falls too far behind (e.g., copy queue length > 0)

61. Improvements in Service Pack 1 SP1 introduces RedistributeActiveDatabases.ps1 script (keep database copies balanced across DAG members) Moves databases to the most preferred copy If cross-site, tries to balance between sites Targetless admin switchover altered for stronger activation preference affinity First pass of best copy selection sorted by activation preference; not copy queue length This basically trades off even distribution of copies for a longer activation time. So you might pick a copy with more logs to play, but it will provide you with better distribution of databases

62. Improvements in Service Pack 1 *over Performance Improvements In RTM, a *over immediately terminated replay on copy that was becoming active, and mount operation did necessary log recovery In SP1, a *over drives database to clean shutdown by playing all logs on passive copy, and no recovery required on new active

63. Improvements in Service Pack 1 DAG Maintenance Scripts StartDAGServerMaintenance.ps1 It runs Suspend-MailboxDatabaseCopy for each database copy hosted on the DAG member It pauses the node in the cluster, which prevents it from being and becoming the PAM It sets the DatabaseCopyAutoActivationPolicy parameter on the DAG member to Blocked It moves all active databases currently hosted on the DAG member to other DAG members If the DAG member currently owns the default cluster group, it moves the default cluster group (and therefore the PAM role) to another DAG member

64. Improvements in Service Pack 1 DAG Maintenance Scripts StopDAGServerMaintenance.ps1 It run Resume-MailboxDatabaseCopy for each database copy hosted on the DAG member It resumes the node in the cluster, which it enables full cluster functionality for the DAG member It sets the DatabaseCopyAutoActivationPolicy parameter on the DAG member to Unrestricted

65. Improvements in Service Pack 1 CollectOverMetrics.ps1 and CollectReplicationMetrics.ps1 rewritten

66. Improvements in Service Pack 1 Exchange Management Console enhancements in SP1 Manage DAG IP addresses Manage witness server/directory and alternate witness server/directory

67. Site Resilience Namespace, Network and Certificate Planning

68. Each datacenter is considered active and needs their own namespaces Each datacenter needs the following namespaces OWA/OA/EWS/EAS namespace POP/IMAP namespace RPC Client Access namespace SMTP namespace In addition, one of the datacenters will maintain the Autodiscover namespace Planning for site resilience Namespaces

69. Best Practice: Use Split DNS for Exchange hostnames used by clients Goal: minimize number of hostnames mail.contoso.com for Exchange connectivity on intranet and Internet mail.contoso.com has different IP addresses in intranet/Internet DNS Important – before moving down this path, be sure to map out all host names (outside of Exchange) that you want to create in the internal zone Planning for site resilience Namespaces

70. Datacenter 1 CAS HT MBX Datacenter 2 HT CAS AD MBX Internal DNS Mail.contoso.com Pop.contoso.com Imap.contoso.com Autodiscover.contoso.co m Smtp.contoso.com Outlook.contoso.com Internal DNS Mail.contoso.com Pop.contoso.com Imap.contoso.com Autodiscover.contoso.co m Smtp.contoso.com Outlook.contoso.com Internal DNS Mail.region.contoso.com Pop.region.contoso.com Imap.region.contoso.com Smtp.region.contoso.com Outlook.region.contoso.co m Internal DNS Mail.region.contoso.com Pop.region.contoso.com Imap.region.contoso.com Smtp.region.contoso.com Outlook.region.contoso.co m Exchange Config ExternalURL = mail.region.contoso.com CAS Array = outlook.region.contoso.co m OA endpoint = mail.region.contoso.com Exchange Config ExternalURL = mail.region.contoso.com CAS Array = outlook.region.contoso.co m OA endpoint = mail.region.contoso.com Exchange Config ExternalURL = mail.contoso.com CAS Array = outlook.contoso.com OA endpoint = mail.contoso.com Exchange Config ExternalURL = mail.contoso.com CAS Array = outlook.contoso.com OA endpoint = mail.contoso.com External DNS Mail.region.contoso.com Pop.region.contoso.com Imap.region.contoso.com Smtp.region.contoso.com External DNS Mail.region.contoso.com Pop.region.contoso.com Imap.region.contoso.com Smtp.region.contoso.com External DNS Mail.contoso.com Pop.contoso.com Imap.contoso.com Autodiscover.contoso.co m Smtp.contoso.com External DNS Mail.contoso.com Pop.contoso.com Imap.contoso.com Autodiscover.contoso.co m Smtp.contoso.com Planning for site resilience Namespaces

71. Design High Availability for Dependencies Active Directory Network services (DNS, TCP/IP, etc.) Telephony services (Unified Messaging) Backup services Network services Infrastructure (power, cooling, etc.) Planning for site resilience Network

72. Latency Must have less than 250 ms round trip Network cross-talk must be blocked Router ACLs should be used to block traffic between MAPI and replication networks If DHCP is used for the replication network, DHCP can be used to deploy static routes Lower TTL for all Exchange records to 5 minutes OWA/EAS/EWS/OA, IMAP/POP, SMTP, RPCCAS Both internal and external DNS zone Planning for site resilience Network

73. Certificate TypeProsCons Wildcard CertsOne cert for both sides Flexible if names change Wildcard certs can be expensive, or impossible to obtain WM 5 clients don’t work with wildcard certs Setting of Cert Principal Name to *.company.com is global to all CAS in forest Intelligent FirewallTraffic is forwarded to the ‘correct’ CAS Requires ISA or other firewall which can forward based on properties Additional hardware required AD replication delays affect publishing rules Load BalancerLoad Balancer can listen for both external names and forward to the ‘correct’ CAS Requires multiple certificates Requires multiple IP’s Requires load balancer Same Config in Both Sites Just an A record change required after site failover No way to run DR site as Active during normal operation Manipulate Cert Principal Name Minimal configuration changes required after failover Works with all clients Setting of Cert Principal Name to mail.company.com is global to all CAS in forest Planning for site resilience Certificates

74. Best practice: minimize the number of certificates 1 certificate for all CAS servers + reverse proxy + Edge/Hub Use Subject Alternative Name (SAN) certificate which can cover multiple hostnames If leveraging a certificate per datacenter, ensure the Certificate Principal Name is the same on all certificates Outlook Anywhere won’t connect if the Principal Name on the certificate does not match the value configured in msstd: (default matches OA RPC End Point) Set-OutlookProvider EXPR -CertPrincipalName msstd:mail.contoso.com