The Exchange 2010 Ecosystem

Transcription

1 The Exchange 2010 Ecosystem Joe Hoegler Practice Leader, Kraft Kennedy Microsoft Certified Master Exchange 2010 TECH9 S e s s i o n G o a l s Discuss the capabilities and limitation of native features Identify when third party solutions are appropriate p Focus on high availability, disaster recovery, backup, archiving and compliance, mobility, anti-virus/anti-spam, unified messaging Discuss considerations for integrating with SharePoint 2010, Office 2010 and Lync 2010 Exchange 2010 Architecture Enterprise Network Phone system (PBX or VOIP) Edge Transport Routing and AV/AS Hub Transport Routing and policy External SMTP servers Mobile phone Mailbox Storage of mailbox items Unified Messaging g Voice mail and voice access Web browser Client Access Client connectivity Web services Outlook (remote user) Outlook (local user) Line of business application 1

2 HIGH AVAILABILITY & DISASTER RECOVERY High Availability & Disaster Recovery Unified in Exchange 2010 via the Database Availability Group Native or third party replication supported Recovery Time Objective of 15 minutes or less is possible Recovery Point Objective of 1 MB or less is possible Database Availability Group San Jose New York Mailbox Server Mailbox Server Mailbox Server Recover quickly from disk and database failures DB1 DB2 DB3 DB4 DB1 DB2 DB3 DB4 DB1 DB2 DB3 DB4 Replicate databases to remote datacenter DB5 DB5 DB5 Evolution of Continuous Replication technology Easier than traditional clustering to deploy and manage Allows each database to have 16 replicated copies Provides full redundancy of Exchange roles on as few as two servers HA and DR capabilities combined into one platform 2

3 Key Considerations Increased storage capacity requirements Dramatically reduced storage performance requirements (~90% IOPS reduction from Exchange 2003) Load balancing appliances strongly recommended WNLB or round robin DNS not recommended Continuous Replication Block Mode Third Party Alternatives Leverage SAN replication through DAG third party replication API SAN-based replication Host-based replication Recommendations Native DAG features and replication provide a complete solution that can be managed wholly by messaging team Marginal feature enhancements or replication performance improvements via third parties generally not worth the added complexity 3

4 BACKUP Exchange Native Protection Backup-less Exchange Site/server/disk failure Archiving/compliance Recover deleted items Database Availability Group Database Availability Group Personal Archive Extended/Protected Dumpster Retention Mailbox Server 1 Mailbox Server 2 Mailbox Server day lag copy DB1 DB2 DB3 DB1 DB2 DB3 DB1 DB2 DB3 X Key Considerations Requires at least 3 database copies across more than 1 site Point-in-time recoveries require lagged database copies Leverages native corruption detection mechanisms Understand Deleted Item Retention and Single Item Recovery 4

5 Third Party Alternatives Virtual Deployments agent, SAN snapshot, image-based backup Physical Deployments agent, SAN snapshot If using SAN snapshots, *always* ensure that snapshots are replicated outside of the enclosure/site Recommendations Increase Deleted Item Retention period to match normal backup retention to help with item-level recovery Leverage Single Item Recovery if appropriate Consider risk/reward of Exchange Native Protection vs. cost of third party backup solution ARCHIVING & COMPLIANCE 5

6 Archiving & Compliance Suite Personal Archive Multi-Mailbox Search Legal Holds Litigation Hold Retention Hold Single Item Recovery Personal Archive A secondary mailbox that is configured by the administrator Appears alongside a user s primary mailbox in Outlook or Outlook Web App. PST data can be dragged and dropped to the Personal Archive Personal Archive in primary mailbox can be moved automatically using Retention Policies Archive quota can be set separately from primary mailbox Multi-Mailbox Search Delegate Access to Specialists Rich Search Criteria and Targeting Options Results Stored in Specialized Mailbox 6

7 Legal Holds User is told how to comply (no action needed for ) URL links to additional info Key Considerations Personal Archive limitations No stubbing, no offline access, separate tree Requires Outlook 2010 Professional or Professional Plus or OWA 2010 Requires Exchange 2010 Enterprise CAL Capabilities of Retention Policies Archive API exists for third party integration Third Party Alternatives Traditional archiving solutions Autonomy ZANTAZ EAS Symantec Enterprise Vault Hosted/cloud d archiving i solutions 7

8 Recommendations Determine feature requirements vs. feature desires Understand the feature gaps between native and third party archiving ing Evaluate if native archiving meets all feature requirements Pilot, pilot, pilot MOBILITY Trends in Mobility Most firms support multiple mobility platforms across a broad range of device types BlackBerry Enterprise Server still generally considered firm standard for enterprise mobility ActiveSync widely adopted across multiple device types (e.g. ios, Android, etc.) Good Mobile Messaging much less common than in the past 8

9 Native ActiveSync Easier provisioning through AutoDiscover Feature control and security enforced through ActiveSync Policies Device OS controls implementation i of policies i Remote wipe Wipes entire device, including personal data Statistics data exists but must be interpreted Allow/Block/Quarantine Key Considerations BES must be version MR5 or MR1 to address specific performance issues associated with BES and Exchange 2010 SP1 Windows Server OS hotfixes, MAPI/CDO updates, and Exchange 2010 SP1 RU3 required as well Advanced ActiveSync Policies require Enterprise CAL (application control, browser control, etc.) MobileIron BoxTone Third Party Alternatives 9

10 Recommendations Establish mobile device usage and support policy State if the firm reserves the right to wipe a personal device if lost If advanced inventory, selective data wipe, and easier statistics are required, consider a third party solution ANTI-VIRUS & ANTI-SPAM Native Message Hygiene Edge Transport Server role includes some native anti-spam features Connection/content filtering, Sender ID, sender reputation, etc. Enterprise CAL (with services) can provide antivirus and anti-spam features Forefront Protection for Exchange Server Forefront Online Protection for Exchange 10

11 Key Considerations Hosted hygiene services dramatically decrease the traffic that reaches a firm s environment Reduces WAN utilization, server processing, etc. Multiple levels of anti-spam can make quarantining challenging No central console for FPE Third party anti-virus software that integrates into transport or scans databases can introduce instability Third Party Alternatives Major anti-virus software vendors McAfee, Symantec, Trend Micro Hosted hygiene services Message Labs, Mimecast, Postini Appliance solutions Axway (formerly Tumbleweed), Barracuda, Cisco Recommendations Strongly consider hosted provider for hygiene services (Microsoft or third party) If pair hosted provider with Edge Transport Server, consider disabling ETS native anti-spam features With multiple levels of anti-virus, avoid scanning database files directly Leverage FPE if Enterprise CAL purchased 11

12 UNIFIED MESSAGING Exchange 2010 Unified Messaging Voic Preview Message Waiting Indicator Protected Voic Call Answering Rules (Enhanced Auto Attendants) Native Faxing Support Removed Voic Preview 12

13 Protected Voic Call Answering Rules Key Considerations Requires supported IP Gateway or IP PBX Proper high availability and disaster recovery for UM must be considered UM role should be located near HTS, CAS, MBX roles UM role is now supported in a virtualized environment Requires Enterprise CAL Previous lack of MWI was previously a large issue 13

14 Third Party Alternatives Avaya Modular Messaging Cisco Unity Traditional PBX Solution Recommendations Understand compliance/discovery requirements for voic storage Define feature requirements of voic solution Consider native UM during next voice refresh INTEGRATION SHAREPOINT, LYNC, OFFICE 14

15 SharePoint 2010 Use Exchange for mail-enabled libraries/lists Consider migrating public folder data to SharePoint for improved usability Lync 2010 Fully integrated with Exchange, SharePoint, Office Presence/IM capabilities available within OWA, SharePoint, Outlook, other Office applications Enables rich and easy collaboration Leverages corporate photographs in AD Leverages SharePoint skills search for ask the expert Lync / OWA Integration 15

16 Lync / Outlook Integration Lync / AD Integration Lync / Office Integration 16

17 Lync / SharePoint Integration Lync Skill Search QUESTIONS? 17