Exchange 2010 High Level Deployment Plan
- Assess Current Infrastructure
- Upgrade Requirements
- Built Exchange 2010 Servers
- AD Preparation
- Installation
- Front End Configuration
- Back End Configuration
- Testing
- Migration
- Post migration
- Uninstall Exchange 2003
Assess Current Infrastructure
- Very first step of Exchange migration is Assessment of current Exchange AD environment.
- You run ExBPA, EXPA, ADMAP and anaylyse the report & fix any issue reported.
- Below are some of the questions you may ask yur customer.
- How many exchange servers are currently running?
- Are they all 2003 SP2 ? 64bit OS or 32 bit OS?
- Exchange server STD or ENT version? Clustered or stand alone?
- How many Databases? How many users? Avarage Mailbox sizes?
- Any journalling / archiving features?
- What kind of back up? daily or weekly ?Incremental or full ?
- What is current DR plan ?
- What are current HA features in Exchange?
- What are exchage security and monitoring softwares in use?
- Are they using EDGE, ISA or TMG servers
- Do they have BES servers ? What version ?
- How many BB users?
- Are they using Active Sync, Outlook anywhere, OWA etc…
- With Exchange 2010 and 2007 heavily rely on DC servers, so it is also essential to get more idea about AD env.
- How many DCs? How many GCs? Version of OS ? 64 Bit or 32 bit?
- How many Sites?
- Is there any windows 2000 DC still in network?
For out test lets assume that we have below infrastruture.
- — 2 Windows 2003 R2 GC
- — 2 Windows 2008 R2 GC
- — 4 Exchange 2003 servers Clustered.
- 2 Front End Exchange 2003 servers
- — 1 BES 5.0.1 server
- — 2 ISA server (DMZ)
- — All servers are in one site and same subnet
- — Clients are running Outlook 2007 and 2010
Upgrade Requirements
- Next step is to talk with client and setup expections for exhange 2010 and ask client that what kind of HA and DR features they are looking for with Exchange 2010 infrastrcuture?
- Are they looking for Standalong Exchange 2010 servers?
- 2 Server DAG same site?
- 3 servers DAG streched in diffrerent site?
- 4 Server DAG with Automatic Datacenter failover ?
- Do they want to combine Hub/CAS/Mailbox roles or separate it?
- If they have ISA servers for web publishing , do they want ot migrate to TMG servers?
- What kind of SLA we are looking for in DR situation?
- Do they want to provide more mailbox space with Ex2010?
- Do they want to go for complience and archiving features ?
- Run EXPDA and Exchange 2010 mailbox caculator and size your exchange servers..
For our scope, below is the requirment, we would like to go forward with..
- — 3 Exchange 2010 servers with single DAG
- — Hub/CAS/MBX role combined
- — 2 Exchange 2010 servers at main site
- — 1 Exchange 2010 server at remote site
- — Single DAG Active Passive
- — FSW on DC/BES
Built Exchange 2010 servers
This is the phase where you order your servers if you are planning to deploy physical servers
Or Provision VM based on Exchange roles sizing calculation.
With our scope, we will follow below path…—
- Create 2 New VMs in site1 and 1 in site2
- — Create disk arrays
- — Install Windows 2008 R2 SP1
- — Install other Windows Update
- — Make a part of MigrationX.com domain
- — Install Exchange 2010 filter pack
- — Install IIS role and dot net framework 3.5 feature from server manager
- — Teaming of Network adapter (optional)
- — Assign static IPs
AD Preparation for Ex 2010
- — Run ExBPA on Exchange 2003 server and analyze results
- — Resolve issue reported in ExBPA
- — Run below commands on one of the VM which has Ex2010SP1 setup files extracted.
- — Setup /pl
- — Setup /ps
- — Setup /p
- — Setup /pd
5. Installation Exchange 2010
- — Extract Ex2010Sp1 setup and click setup.exe
- — Click on Automatically install all windows role and features necessary for ex2010 setup
- — Write mail.migrationx.com as external name space
- — Install Hub/Mailbox/CAS role
- — Install Forefront protection for Exchange
- — Install CA role into one of DC
6. Front end Config : Pre Migration
- Now we will start configuring those exchange 2010 servers, based on our reqirments.
- Create CSR for SAN cert
- — Get SAN cert from Internal CA
- — Import SAN cert thru IIS
- Create CAS array
- — Configure F5 HLB
- — — DNS changes for legacy owa url
- — Configure OWA redirection for Ex2003 users
- — Open ports from Ex2010 servers to firewall
- — Replace internal owa with mail.migrationx.com
- — Configure autodiscover uri parameter to point to HLB on CAS
- — Configure ISA server web publishing rules
- — ISA rules switch over
Back end Config of Ex 2010
- — Delete default Exchange 2010 DBs
- — Create and configure new DB into Ex2010
- — Create DAG /FSW
- — Create DAG network and Static routes
- — Add member server and DB copy into DAG
- — Create Public folder database
- — Create test mailboxes into Ex2003 and 2010
- — Configure retention policies and tags
- — Install Backup and testing
- — Create Receive connector for SMTP relay
Testing of Ex 2010 Environment
- — Connectivity test with CAS array
- — MAPI tests with Outlook 2003/2007/2010
- — OWA OA EAS BB test
- — DAG Replication test
- — Changes on BES server and testing
- — Backup restore testing
- — Test SMTP relay applications
- — Test mailbox moves
- — Test inbound out bound mail flow and connectivity
- — Test BB device email connectivity, address lookup and calendar sync after migration
- — Test internal external mail flow
Migration : Move mailboxes
- — Pilot migration
- — Tier 1 Mailbox move
- — Resolve mailbox migration related issues
- — Tier 2 mailbox move
- — Special mailbox move
- — Room mailbox move and convert into Resource mailbox
- — Final mailbox move
Post Migration
- — Create Send connectors on Ex2010
- — Configure TLS and change cost
- — Email cutover
- — Delete Internet connector on Ex2003
- — Update Default email address policy
- — Move replica of public folders to Ex2010
- — Delete Ex2003 Public folders
Uninstall Exchange 2003
- — Temporary shutdown services on Ex 2003 servers
- Temporary Shut down Ex 2003 severs
- — Resolve any issue related to Exchange 2003
- — Remove Recipient Update services from Ex2003
- — Remove Interop routing group
- — Dismount and delete Ex 2003 DBs
- — Uninstall Exchange 2003
- — Shut down Windows 2003 servers
