8/8/2011

1

The Exchange 2010 Ecosystem

Joe HoeglerPractice 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 appropriatepp 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 ArchitectureEnterprise NetworkEnterprise Network

ExternalSMTP

servers

Edge TransportRouting and AV/AS

Phone system (PBX or VOIP)

Hub TransportRouting and policy

Mailbox Unified Messaging

Client AccessClient connectivity

Web servicesWeb browser

Outlook (remote user)

Mobile phone

Outlook (local user)

Line of business application

MailboxStorage of mailbox

items

g gVoice mail and voice access

8/8/2011

2

HIGH AVAILABILITY & DISASTER RECOVERY

High Availability & Disaster Recovery

• Unified in Exchange 2010 via the Database Availability Group

• Native or third party replication supportedf• Recovery Time Objective of 15 minutes or less

is possible• Recovery Point Objective of 1 MB or less is

possible

Database Availability Group

Mailbox Server

DB1

DB3

DB2Recover quickly from disk and

d b f il

Mailbox Server

DB1DB2DB3

Mailbox Server

DB1DB2DB3

Replicate databases to remote datacenter

San Jose New York

• 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

DB4

DB5

database failures DB4

DB5

DB4

DB5

8/8/2011

3

Key Considerations

• Increased storage capacity requirements– Dramatically reduced storage performance

requirements (~90% IOPS reduction from Exchange 2003)g )

• 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 feat re enhancements or replication • Marginal feature enhancements or replication performance improvements via third parties generally not worth the added complexity

8/8/2011

4

BACKUP

Exchange Native Protection

“Backup-less” ExchangeDatabase Availability GroupPersonal ArchiveExtended/Protected Dumpster Retention

Site/server/disk failureArchiving/complianceRecover deleted items

7-14 day lag copy

XX

Database Availability Group

Mailbox Mailbox Server 1Server 1

Mailbox Mailbox Server 2Server 2

Mailbox Mailbox Server 3Server 3

DB1

DB2

DB3

DB1

DB2

DB3

DB1

DB2

DB3

Key Considerations

• Requires at least 3 database copies across more than 1 site

• Point-in-time recoveries require lagged database copiesdatabase copies

• Leverages native corruption detection mechanisms

• Understand Deleted Item Retention and Single Item Recovery

8/8/2011

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– Leverage Single Item Recovery if appropriate

• Consider risk/reward of Exchange Native Protection vs. cost of third party backup solution

ARCHIVING & COMPLIANCE

8/8/2011

6

Archiving & Compliance Suite

• Personal Archive• Multi-Mailbox Search• Legal Holds

– Litigation Hold– Retention Hold

• Single Item Recovery

Personal ArchiveA 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

E-mail in primary mailbox can be moved automatically using Retention Policies

Archive quota can be set separately from primary mailbox

Personal Personal ArchiveArchive

Multi-Mailbox SearchDelegate Access to SpecialistsDelegate Access to Specialists

Rich Search Criteria and Targeting OptionsRich Search Criteria and Targeting Options

Results Stored in Specialized MailboxResults Stored in Specialized Mailbox

8/8/2011

7

Legal Holds

User is told how to comply (no action needed for e-mail)

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 2010Plus or OWA 2010– Requires Exchange 2010 Enterprise CAL– Capabilities of Retention Policies

• Archive API exists for third party integration

Third Party Alternatives

• Traditional e-mail archiving solutions– Autonomy ZANTAZ EAS– Symantec Enterprise Vault

H d/ l d hi i l i• Hosted/cloud archiving solutions

8/8/2011

8

Recommendations

• Determine feature requirements vs. feature desires

• Understand the feature gaps between native and third part archi ingand third party archiving

• 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 pmobility

• ActiveSync widely adopted across multiple device types (e.g. iOS, Android, etc.)

• Good Mobile Messaging much less common than in the past

8/8/2011

9

Native ActiveSync

• Easier provisioning through AutoDiscover• Feature control and security enforced through

ActiveSync PoliciesD i OS l i l i f li i– Device OS controls implementation of policies

• Remote wipe– Wipes entire device, including personal data

• Statistics data exists but must be interpreted• Allow/Block/Quarantine

Key Considerations

• BES must be version 5.0.2 MR5 or 5.0.3 MR1 to address specific performance issues associated with BES and Exchange 2010 SP1– Windows Server OS hotfixes MAPI/CDO updates – 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.)

Third Party Alternatives

• MobileIron• BoxTone

8/8/2011

10

Recommendations

• Establish mobile device usage and support policy– State if the firm reserves the right to wipe a

personal device if lostpersonal 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 etcreputation, etc.

• Enterprise CAL (with services) can provide anti-virus and anti-spam features– Forefront Protection for Exchange Server– Forefront Online Protection for Exchange

8/8/2011

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 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 servicesM M– 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 featuresconsider disabling ETS native anti spam features

• With multiple levels of anti-virus, avoid scanning database files directly

• Leverage FPE if Enterprise CAL purchased

8/8/2011

12

UNIFIED MESSAGING

Exchange 2010 Unified Messaging

• Voicemail Preview• Message Waiting Indicator• Protected Voicemail• Call Answering Rules (Enhanced Auto

Attendants)• Native Faxing Support Removed

Voicemail Preview

8/8/2011

13

Protected Voicemail

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

8/8/2011

14

Third Party Alternatives

• Avaya Modular Messaging• Cisco Unity• Traditional PBX Solution

Recommendations

• Understand compliance/discovery requirements for voicemail storage

• Define feature requirements of voicemail sol tionsolution

• Consider native UM during next voice refresh

INTEGRATIONSHAREPOINT, LYNC, OFFICE

8/8/2011

15

SharePoint 2010

• Use Exchange for mail-enabled libraries/lists• Consider migrating public folder data to

SharePoint for improved usability

L y n c 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

8/8/2011

16

Lync / Outlook Integration

Lync / AD Integration

Lync / Office Integration

8/8/2011

17

Lync / SharePoint Integration

Lync Skill Search

QUESTIONS?