UNC301 - Microsoft Exchange Server 2010 Upgrade and Coexistence with Exchange Server 2007 and 2003

Exchange 2010 Upgrade and Coexistence
Andrew Ehrensing
Principal Consultant
Microsoft Corporation
UNC301

New from Exchange Server 2003 to Exchange Server 2007
Shift from front-end/back-end to a scalable role-based architecture
64-bit server support
Active Directory Sites replace Routing Groups
AutoDiscover to automatically configure users
Removes Outlook 2007+ need for Public Folders
Availability Service: Free/Busy information read direct from mailboxes, not from Public Folders
Offline Address Book download from Client Access Server
New admin tools
Unified Messaging: Get voice mail in your inbox
New Developer API: Exchange Web Services (EWS)

New from Exchange Server 2007 to Exchange Server 2010
Flexible deployment choices
Run Exchange Server on-premises, use Exchange Online, or a hybrid approach
High Availability solution for mailbox resiliency
Comprised of database availability group and database copies
Provides site resilience and disaster recovery
30-second switchover/failover with simplified admin experience
Improves the flexibility in storage choices (SATA disks, JBOD configurations, etc.)
Replaces SCR, LCR, SCC, and CCR from E2007
64-bit management tools support
RPC client access and Address Book services
Improved High Availability solution
Outlook MAPI connects directly to Client Access Servers for mailbox-related data and directory requests
ExOLEBD, WebDAV, and CDOEx are gone
“Entourage EWS” uses EWS

A familiar and rich Outlook experience across clients, devices, and platforms
Mobile
Web
Collaborate Effectively
Desktop

Exchange Server 2010 Prerequisites
Active Directory
Windows 2003 SP2 global catalog server is installed in each Exchange Active Directory (AD) site
No hard requirement for Windows Server 2008 AD
Windows Server 2003 forest functional level
Exchange
All Client Access Servers (CAS) and Unified Messaging (UM) servers must have SP2
Existing servers are Exchange 2003 SP2 or Exchange 2007 SP2
Server
Windows Server 2008 SP2 or R2 64-bit editions (Std/Ent)
Windows Management Framework
.NET Framework 3.5 SP1
Internet Information Services (IIS)

Starting Setup for Exchange 2010
Step-by-step instructions in setup app
Setup.com with parameters gives unattended setup
Setup provides specific settings for configuring your environment
Configure CAS External domain name
Sets ExternalUrl property which aids client configuration
E2003 routing groupconnector: E2003 server

Namespaces and URLs
Exchange 2010
Exchange 2007
Exchange 2003
mail.contoso.com
mail.contoso.com
mail.contoso.com
Outlook Web Access
/exchange, /exchweb, /public
Exchange ActiveSync
/microsoft-server-activesync
Outlook Anywhere
/rpc
POP/IMAP
Outlook Mobile Access
/oma
Outlook Web Access
/owa
Exchange Web Services
/ews
Offline Address Book
/oab
Unified Messaging
/unifiedmessaging
Outlook Mobile Access
/oma
Outlook Web Access
Outlook Web App
Exchange Control Panel
/ecp
Unified Messaging
/unifiedmessaging
Note: the legacy vdirs will provide a 301 redirect experience to /owa
Autodiscover.contoso.com
smtp.contoso.com
legacy.contoso.com
E2003/E2007 services
Autodiscover
/autodiscover
Clients and SMTP servers

Deploying SSL Certificates
Use “Subject Alternative Name” (SAN) certificate which can cover multiple hostnames
Site resilience scenario
If leveraging a certificate per datacenter, ensure that the Certificate Principal Name is the same on all certificates
Don’t list machine hostnames in certificate hostname list
Use Load Balance (LB) arrays for intranet and Internet access to servers
Best practice: Minimize the number of certificates
1 certificate for all CAS servers + reverse proxy + Edge/Hub
Additional certificate(s) if using Office Communications Server (OCS)

New-ExchangeCertificate
-GenerateRequest
-Path c:certificates equest.req
-SubjectName “c=US, o=contoso Inc, cn=mail1.contoso.com”
-DomainNamemail.contoso.com, autodiscover.contoso.com, legacy.contoso.com
-PrivateKeyExportable$true
Certificate Creation
Create a Certificate Request file
Send Request file to certificate authority you are buying from
Use Import-ExchangeCertificate to activate newly acquired certificate
Use Enable-ExchangeCertificateto enable the certificate for use with a particular service

Certificate Wizard
demo

Deploying E2010
Topology Decisions—Split DNS
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 the hostnames (outside of Exchange) that you will want to create in the internal zone

Deploying Exchange 2010
Topology decisions—CAS load balancing
OWA and EWS load balancing require ClientServer affinity
Client-IP based Windows NLB or LB device using cookie-based affinity
Tell Autodiscover where to send clients: Configure internalURL and externalURL parameters and virtual directories
Example: Set-WebServicesVirtualDirectory cas2010ews* -ExternalURL https://mail.contoso.com/ews/exchange.asmx
Tell Outlook clients where to go for intranet MAPI access
Use New-ClientAccessArray and set-mailboxdatabase

Deploying Exchange 2010
Topology decisions—CAS load balancing
CAS AutoDiscoverServiceInternalUriproperty should be set to NLB FQDN
Ensure the Web Services property InternalNLBBypassURL is set to the Server FQDN
Configure virtual directory URLs according to this table:

Upgrading to Exchange 2010
Internet Facing AD Site
2
Deploy E2010 Servers
Upgrade Internet-facing sites FIRST
Start small
Gradually add more servers to support scale
4
Move Infra Pointers
Internet hostname switch
Unified Messaging switch
SMTP switch
Internal AD Site
Proxy
https://autodiscover.contoso.com
https://mail.contoso.com
5
Internet
Move Mailboxes
E200x Servers
https://autodiscover.contoso.com
https://mail.contoso.com
https://legacy.contoso.com
Legacy hostnames for old FE/CAS
3
1
Upgrade servers to SP2
SSL cert purchase
End users don’t see this hostname
Used when new CAS tell clients to talk to legacy environments
E200x Servers
Upgrade Internal sites NEXT
Decommission old servers

Preparation Tools
Finding and solving problems before users do
Remote Connectivity Analyzer
Verify Internet-facing services are set up and configured properly
Troubleshooting Assistant
Help determine the cause of performance, mail flow, and database issues
Load Generator
Simulate and test how a server responds to e-mail loads
Best Practice Analyzer
Determine overall health of Exchange system and topology

Exchange Remote Connectivity Analyzer
demo

Switching to CAS2010
Preparatory steps
Obtain and deploy a new certificate that includes the required host name values
mail.contoso.com
autodiscover.contoso.com
legacy.contoso.com
Upgrade all Exchange servers to Service Pack 2
Enable Integrated Windows Authentication on Exchange 2003 MSAS virtual directory (KB 937031)
Install and configure CAS2010 servers
Configure InternalURLs and ExternalURLs
Enable Outlook Anywhere
Configure the Exchange2003URL parameter to be https://legacy.contoso.com/exchange

Preparatory steps, continued
Join CAS2010 to a load balanced array
Create CAS2010 RPC Client Access Service array
Ensure MAPI RPC and HTTPS ports are load balanced
Install HUB2010 and MBX2010 servers
Configure routing coexistence
Configure OAB Web-based distribution
Create Legacy record in DNS (internal/external)
Create Legacy publishing rules in your reverse proxy/firewall solution pointed to FE2003 / CAS2007 array
Use ExRCA to verify connectivity for Legacy namespace

The switchover
autodiscover…
mail…
legacy…
The switchover involves a minor service interruption
Update internal DNS and have Mail and Autodiscover point to CAS2010 array
Update/Create Autodiscover publishing rule and point to CAS2010 array
Update Mail publishing rules and point to CAS2010 array
Remember to update paths with new Exchange 2010 specific virtual directories
Reconfigure CAS2007 URLs to now utilize Legacy namespace
Disable Outlook Anywhere on legacy Exchange
Test that CAS2010 is redirecting/ proxying to CAS2007 (externally and internally)
ISA
1
2
2
E2010 CAS+HUB+MBX
E200x SP2
Clients access E2010 through Autodiscover… and mail…
1
Redirection (legacy…), proxying, and direct access to E2003/E2007
2

Client Access Upgrade
Clients access CAS2010 first
Four different things happen for E2003/ E2007 mailboxes
Autodiscover tells clients to talk to CAS2007
HTTP redirect to FE2003 or CAS2007
Proxyingof requests from CAS2010 to CAS2007
Direct CAS2010 support for the service against BE2003 and MBX2007

Exchange CAS Redirection
demo

Follow this flow for each physical location
Edge servers are optional
Edge 2007 SP2 can be used with HUB 2010
Step 5:
Switch Internet e-mail submission to Edge 2010
SMTP Transport Upgrade
Internet SMTP Servers
Step 4:
Install Edge 2010
E2010 Edge
E2007 Edge
Step 3:
Switch Edgesync +SMTP to go to HUB2010
E2010 HUB
E2007 HUB
E2003 Bridgehead
Step 1:
Upgrade existing E2003 and E2007 servers to SP2
Step 2:
Install HUB and MBX 2010
E2003 Back-End
E2010 MBX
E2007 MBX

Unified Messaging Upgrade
Step 1:
Introduce UM 2010 to existing dial plan
Step 2:
Route IP GW/PBX calls to UM 2010 for dial plan
Step 3:
Remove UM 2007 after mailboxes have been moved
IP PBX/ gateways: One Dial Plan, Redirect
With Office Communications Server: Will find proper UM server

Public Folders
Co-existence support between mailbox server 2010 and mailbox server 2003/2007
Outlook can read mailbox from one Exchange version (such as 2010) and public folder from another (such as 2003/2007)
OWA 2010 will allow access to public folders with replica in mailbox server 2010
Get-PublicFolderStatistics help take action
Move
Delete
Migrate to SharePoint

Service Level Agreement
Service availability during migration
1GB mailbox could take 90 minutes or more to move
Pain: User is disconnected for the duration
Pain: Your SLA for availability is not met

Online Move Mailbox
Minimal disruption
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
Also can be used to migrate users from on-premises server to Exchange Online
E-mail Client
Client Access Server
Exchange 2010 and Exchange 2007 SP2 Online
Exchange 2003 Offline
Mailbox Server 1
Mailbox Server 2

Key Takeaways
Exchange 2007 Service Pack 2 introduces new functionality and is required for coexistence with Exchange 2010
Upgrading server roles is seamless and without impact to end users
Online mailbox moves improves mailbox data migration by significantly reducing the user outage window

question & answer

Required Slide
Speakers,
TechEd 2009 is not producing
a DVD. Please announce that
attendees can access session
recordings at TechEd Online.
www.microsoft.com/teched
Sessions On-Demand & Community
www.microsoft.com/learning
Microsoft Certification & Training Resources
http://microsoft.com/technet
Resources for IT Professionals
http://microsoft.com/msdn
Resources for Developers
Resources

UNC Track Call to Action!
Learn More!
Related Content at TechEd on “Related Content” Slide
Attend in-person or consume post-event at TechEd Online
Check out learning/training resources at Microsoft TechNet
Exchange Server and Office Communications Server
Check out Exchange Server 2010 atVirtual Launch Experience (VLE) at thenewefficiency.com
Try It Out!
Download the Exchange Server 2010 Trial
Take a simple Web-based test drive of UC solutions through the 60-Day Virtual Experience

Required Slide
Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!

Required Slide
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

UNC301 - Microsoft Exchange Server 2010 Upgrade and Coexistence with Exchange Server 2007 and 2003

by Louis Göhl on Nov 12, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 92

Statistics

UNC301 - Microsoft Exchange Server 2010 Upgrade and Coexistence with Exchange Server 2007 and 2003 — Presentation Transcript

http://www.slideshare.net	91
http://translate.googleusercontent.com	1