Transcript Exchange

Lee Benjamin
ExchangeGuy Consulting
www.ExchangeGuy.com
About Lee Benjamin
ExchangeGuy Consulting
Architecture, Migration/Upgrades, Project Guidance
ISV Advisor, Strategy, Whitepapers, Testing, Reviews
Industry Events, Speaker, Custom Training, Expert
www.ExchangeGuy.com
[email protected]
User Groups
Chairman
Vice President
Global Secretary
Advisor
www.ExchangeServerBoston.org
www.BostonUserGroups.org
www.GITCA.org
www.VirtG.com
Agenda
• Virtualizing Exchange 2010
• Common Questions, Releases
• Architectural Foundation
• Exchange Server Roles
• Foundation Technologies
• Virtualization and Exchange
• Generalities
• Hyper-V, Other (WSVVP)
• Exchange Online In Office 365
Common Questions
 What Exchange Roles can I virtualize?
 Should I virtualize the Mailbox Role?
 Can I virtualize with VMware, or just Hyper-V?
 What about virtualization snapshots?
 Should I use Network Load Balancing?
 Can I virtualize the Unified Messaging Role?
 Can I virtualize Lync?
 Is Office 365 considered virtualization?
Exchange Server 2010 Releases
 Exchange Server 2010
 Released November 2009
 Final RTM Rollup 5 Released December 2010
 EX2010 RTM Is No Longer Supported (With or Without RU)
 Service Pack 1
 EX2010 SP1 Released August 2010
 Rollup 6 for SP1 Released October 2011
 Service Pack 2
 EX2010 SP2 Released December 2011

Hybrid Configuration Wizard, OWA Mini,
Address Book Policies (GAL Segmentation)
 Rollup 1 for SP2 Released February 2012
 http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-
and-update-rollups-builds-numbers.aspx
MEC Is Back !!
 Microsoft Exchange Conference
 Was The Conference About Exchange






1996 Austin (Exchange Deployment Conference)
1997 San Diego
1998 Boston
1999 Atlanta/Hamburg/Tokyo
2000 Dallas/Nice/Tokyo/Singapore
2001 Orlando/Nice
 Started Out Reasonable Size (Though 4000 Peak in Boston)
 Many Community Experts
 Disappeared For Ten Years.. ?
 MEC Returns
 September 24-26, 2012 In Orlando
 Focus is Exchange, On-Premises and Cloud
Exchange Server Roles
Exchange 2003
1. Front-End
Server
2. Back-End
Server
• SMTP, POP3/IMAP4
• HTTPS
• Outlook Web Access
• Exchange ActiveSync
• Hygiene (AV/AS)
• Optional
•
•
•
•
Mailbox Databases
Routing
MAPI/Outlook
Includes Front-End
Exchange 2010/2007
1. CAS – Client
Access Server
• Client Connection Point, Required
• Including Outlook/MAPI In 2010
• More Load, = More CPU + Memory
2. HUB – Hub
Transport Role
• All Message Routing, Required
• Shadow/Resiliency In 2010
3. MBX –
Mailbox Role
• 64 Bit ESE Database
• Scalability And Performance
4. UM – Unified • Voicemail, Voice Access,
Voicemail Preview
Messaging
5. EDGE- Edge
Transport Role
• Routing and Hygiene
• Lives Alone, Optional
Exchange 2010 Architecture
Phone system
(PBX or VOIP)
Edge Transport
Routing & AV/AS
Hub Transport
Routing & Policy
External
SMTP
servers
Mailbox
Storage of
mailbox items
Unified Messaging
Voice mail &
voice access
Mobile
phone
Web
browser
Client Access
Client connectivity
Web services
Outlook
Anywhere
(remote user)
Line of business
application
Outlook (local user)
Exchange 2010 Foundation
64bit Database
And Storage
Technologies (ESE)
Virtualization
Support
Availability
And Resilience-
Designed For
On-Premises
and OnlineHosted
Compliance
And Discovery
Functionality
Integration
With Mobility
And Voice
Anti-Virus,
Anti-Spam,
And Rights
Management
Exchange’s
Database
 Extensible Storage Engine (ESE)
 Well Known With 16 Years In Production
 64bit Database Introduced In Exchange 2007
 Removed Database Cache Memory Limitation (1.2GB)
 Log Files Are 1MB (was 5MB), STM Files Are No More
 For 2010, Database Reorganized For Large Mailboxes
 Tables vs. Mailboxes, SIS Casualty, Storage Groups Gone
 Database Page Repair From Replicated Copy (Lagged)
 90% IO Reduction Over Exchange 2003
 Really Fast, Latency Matters, No NAS
MAPI To The Middle (CAS) Finally
Mailbox
CAS
Middle
Tier
Mailbox
Agents
OWA
Sync
Entourage
UM
Exchange
Biz Logic
Store
WS
Outlook
/ MAPI
CAS
MAPI RPC
Exchange Components
Mailbox
Agents
OWA
Sync
MAPI,
Exchange
RFR &
Biz Logic
NSPI RPC
Exchange Core Biz Logic
DAV
Mailbox
WS
Transport
Agents
Entourage
Middle
Tier
Exchange Components
Outlook
/ MAPI
MAPI RPC
Store
Performance Implications Moving Heavy Workload
Transport
Agents
UM
Database Availability Groups
 SCC, CCR, and SCR Evolved
 No Clustering Knowledge Required
 Windows Server Clustering Underneath For Heartbeat
 From 2 To 16 Replicas, Multiple Active Nodes
 All Managed Inside Exchange
 Exchange Management Console or Shell
 Recommend 3-4 Node DAGs, Or Larger (2 with SP1)
 Allows Slower SAS Or Lower Cost SATA Disks
Must I Sill Backup? Yes.
 Storage Groups Removed 2010
 Store:SG Became 1:1 in 2007
 Stores Now Owned By The Organization
 Allows Database Mobility


Recover To Another Exchange Server
Recovery Database (was Recovery Storage Group)
 Streaming Backup Support No Longer
 Only VSS Snapshots
 From Microsoft And 3rd Parties
 Backup/Restore From/To Any DAG Member
 Why Restore When You’ve Got DAG Replication..??
Transition: Deployment Assistant
 http://technet.microsoft.com/exdeploy2010
Remote Connectivity Analyzer
 https://www.
testexchangeconnectivity.com/
 Test
 Exchange ActiveSync (EAS)
 Outlook Anywhere




(RPC/HTTP)
Autodiscover
SMTP
…More Will Come…
Office 365
 Use It Every Step Of Transition
Architectural Best Practices
 Multi-Role Servers
 When At All Possible
 Combine Roles
 CAS+HUB Obvious
 Similar Functions (Protocols)
 CAS And HUB Not Supported In the DMZ
 Not MBX or UM Either, Only Edge
 Infrastructure Remains Critical
 64bit Domain Controllers
 Load Balancers versus NLB
 Redundancy, Redundancy, Redundancy
EX2010 Virtualization Support
 EX2010 Runs On Windows Server 2008 And R2, 64bit
 Not Supported On Server 8 Beta !!
 Microsoft Hyper-V
 Also Microsoft Hyper-V Server/R2
 Third-Party Hypervisor Validated Under WSVVP
 Windows Server Virtualization Validation Program
 VMware, Other
 Any Exchange 2010 Role
 Unified Messaging (UM) Supported SP1
 Only Virtualization SW On Host, and Management SW
 Dynamic Memory Not Useful
Virtual Concerns
 9-12% Overhead For Hypervisor
 Plan For 10% Less Users
 Same CPU and Memory Requirements As Physical
 Savings May Not Be There
 Scale Out Rather Than Scale Up
 Conscious Decision From Exchange Team
 Spread The Load And Risk
 More Servers And Replicated Copies (DAGs)
 Storage
 Must Use Fixed Size Virtual Storage Disks, or SCSI
Pass-Through Physical Disks, or iSCSI SAN Disks
 No Differencing Disks, No Hypervisor Snapshots
Virtualization Scenarios
 CAS/HUB, MBX, UM
 Branch Office
 Streamlined Provisioning To Smaller Offices
 Distributed DR Sites
 Around The World
 DR Sites With Lagged Copies
 Log Files Are Replicated
 Delayed Insert Into Database (Hours, Days)
 If Major Corruption, Remove Troubled Log Before
 Transition Helper
 CAS/HUB 2007 And CAS/HUB 2010
Living With The Cloud- Hybrid
Coexistence
Sync AD
Microsoft Office 365
What’s New in Office 365
• Flexible service offering
with pay-as-you-go,
per-user licensing
• The complete Office
experience with
services integration in
Office 365
• Always the latest
version of the Office
apps, including Office
Web Apps
• Familiar Office user
experience to access
services
•
•
•
•
• Voicemail with unified
messaging
• Integrated personal
archiving
• Retention policies and
legal hold
• Exchange Control
Panel
• Free/busy coexistence
• Cross-premises
management
• My Sites to manage
and share documents
• Access documents
offline
• Improved Team &
Project Sites
• Document-level
permissions to protect
sensitive content
• Share documents
securely with Extranet
Sites
• Cross site collection
search
New user interface
Role based access
Identity federation (eliminate sign-in client)
Multi-factor authentication support
• IM & Presence across
firewalls
• GAL/Skill search in
SharePoint
• Online meeting with
desktop sharing
• Activity feeds
• Contact photos
• Click to communicate
from Office contact
cards
• Windows Live
federation
Simple Exchange Coexistence
•
•
•
•
Exchange 2010 is not required
for simple coexistence features
Exchange 2003,
2007 or 2010
Rich Exchange Coexistence
 Share free/busy data between cloud




and on-premises users
Manage cloud and on-premises
users from one place
Configure secure, high-fidelity
cross-premises mail flow
Migrate users to the cloud with
native Exchange tools
Easily move mailboxes back onpremises
Exchange 2010 SP1 “gateway”
server enables rich coexistence
with Exchange 2003/2007
Exchange 2010 SP1
server
Exchange
2003/2007
Rich Coexistence Mailbox Moves
Exchange
2010 SP1
CAS
Exchange
2003
Exchange
2007
 Uses same replication engine as
Exchange
2010 SP1
on-premises mailbox moves
 Migration support is built into
Exchange Management Console
and Remote PowerShell
 No Outlook resync or profile
change required after mailbox
move
 Yes, you can go back
Office 365 Simple vs. Rich
Coexistence
Feature
Simple
Rich*
Mail routing between on-premises and cloud (recipients on either side)


Mail routing with shared namespace (if desired; @company.com on both sides)


Unified global address list (GAL)


Free/Busy information and calendar sharing across premises

Out of Office notice understands that across-premises is internal to the organization

MailTips, messaging tracking, and mailbox search work across premises

Outlook Web App Redirection across premises (single URL for Outlook Web App both on
premises and in the cloud)

Preserve Auth header (that is, ensure internal email is not marked as spam, resolve against
GAL)

Exchange Management Console on premises is used to manage cross-premises mailbox
migrations

Mailbox moves support both onboarding and offboarding

No Outlook reconfiguration or OST resynchronization required after mailbox migration

equires Exchange 2010 SP1 HT+CAS on premises and requires supplemental configuration steps (both on
premises and in the cloud)
Common Questions
 What Exchange Roles can I virtualize?
 Should I virtualize the Mailbox Role?
 Can I virtualize with VMware, or just Hyper-V?
 What about virtualization snapshots?
 Should I use Network Load Balancing?
 Can I virtualize the Unified Messaging Role?
 Can I virtualize Lync?
 Is Office 365 considered virtualization?
Virtualization Summary
Exchange 2010: Rise Of The Hypervisors
Consolidation and Resilience Are Business Drivers
Exchange Heavy Resource Application, Virtual Or Not
When Not To Virtualize- UM Role (Perhaps Not Enough
Resources), CPU/Memory, Hypervisor Not Validated
Scenarios- Virtual Disaster Recovery, Branch Office,
Redundancy, Green Computing, Transition Helper
Lee Benjamin
ExchangeGuy Consulting
www.ExchangeGuy.com
[email protected]
ExchangeServerBoston.org, Chairman
BostonUserGroups.org, Vice President
Virtualization Group (VirtG), Advisory Board
GITCA.org (formerly Culminis), Director, Global Board