A. Introduction:
1. New form 2007 to 2010:
· Run exchange server yourself, or use exchange online
· High availability solution for mailboxes is database availability group (DAG)
a. Also provides site reillience3 and dr
b. 30sec failover with simplified admin experience
c. Works with cheap disk
d. Replaces SCR, LCR, SCC and CCR from 2007
· EMC (Exchange mangement console) client access server
a. Improved high availability solution: outlook MAPI connects directly to CAS
B. Transition:
1. In nutshell:
· Transition ad site by ad site
· Start with internet facing AD sites
· Upgrade all your existing servers to SP2
· Deploy 2010 servers CAS first, MBX last. Start with few and gradually add more servers as you move mailboxes
2. Steps:
· Legacy hostname for old FE/CAS
· SSL cert purchased
· End users don’t’ see this host mane
· Used when auto discover and redirection form cas2010 tell clients to talk to fe2003 /cas 2007 for MBX 2003 and MBX 2007 access
3. Move:
· Internet host manes to cas2010
· Um phone number to um 2010
· SMTP end point to hub2010
·
4. Move mailboxes
5. Decommission old servers
6. Move to next AD site
C. Prerequisites:
1. Windows server 2008 sp2 or r264 bit, standard, enterprise...
2. Client supported , outlook 2007, enterouge 2008, outlook 2010
D. Tools for migration:
1. Remote connectivity analyzer:
· https://www.testexchangeconnectivity.com
· In beta
· Features: Active sync connectivity test
· Use this tool validate any change
E. Migration/Deployment:
1. Setup:
· Step by step instructions in setup app
· Setup.exe with parameters gives unattended setup
· Try it this week – UNC14-HOL
· Configure 2010:
a. Your preferred configuration
b. External cas hostname: mail.andaker.com. exernalURL parameters
2. Certificates and SSL
· Best practice: minimize the number of certificates:
a. 1 certificate for all CAS serves + reverse proxy + edge/hub
b. Use ‘subject alternative name” (SAN) certificate which can cover multiple hostnames
c. Don’t list machines hostnames in certificated hostname list: use load balance (LB) array
d. Minimize the number of host names
3. CAS load balancing:
· Best practice: use ‘split dns” for exchange hostnames used by clients. Goal: minimize number of hostnames
a. Mail.andaker.com for exchange connectivity on intranet and internet
b. Mail.andaker.com has different IP addressing intranet/internet DNS
· Here’s the gotcha: OWA and EWS load balancing require client <-> sever affinity:
a. Client –IP based window NLB or LB device using cookie based affinity
· Tell autodiscover where to send clients : configure internal URL and externalURL parameters on virtual directories:
a. E.g. Set-owavirtual directory
4. Certificates: step by step
· New-exchange Certificate*
· You can also use certificate wizard
a. Takes you through list of questions to list all host names you need
b. The rtm version will include configuration for legacy CAS
5. Switching to 2010 CAS:
· configure reverse proxy (eg.isa) or external dns to point legacy.anddaker.com to fe2003/cas2007
· transition from 2003: ensure owa can redirect user to correct URL: configure exchange 2003 url parameter on CAS2010 owa virtual directory
· test before the plunge: legacy.andakercom works for internet access
6. the plunge:
· transition from 2007: tell CAS2010 how to send users to CAS2007:
a. configure externalURL parameter on cas2007 virtual directories (OWA, EAS, EWS, OAB..) to point to legacy.andake.com
b. tests that cas 201o is redirecting
· configure reverse proxy or dns:
a. switch mail.candakar.com to go to 2010 cas and edge/hub
b. users will start using 2010
7. demo:
· setting the virtual directory on 2010 to point exchange 2003 users to right directories by use of -external2003URL
· view from ISA server: publishing 2010 rules on ISA:
a. you can go to paths and create new path mappings for 2010 (e.g., /ews/*, /autodiscover)
b. update the DNS records pointing to 2007 to 2010
· run test exchange connectivity
· you get the logon page of 2010 but it redirects to owa 2003
8. client access transitions:
· client access cas2010
· four different things happen for 2003/2007 mailboxes
a. autodiscover tells clients to talk to cas 2007
b. http redirect to FE (front end 2003 or CAS 2007
c. praying of requires form CAs 2010 to CAS 2007: for pop and imap there is no redirection
d. direct CAS 2010 support for the service against BE 2003 and MBX 2007
9. smtp transport transition:
· upgrade existing servers to sp2
· introduce 2010 servers
· switch edge DNS + stmp to go to hub2010, you can continue to use 2007 edge just change out the subscription
10. Exchange UM:
· Introduce 2010 UM
· Add the UM to dial plan you already have
· Configure gateway
· You tell everyone to talk to 2010 first. 2010 is smart enough to redirect users on 2007 to 2007 UM
11. Exchange UM: OCS
· You need to add new dial plan\
· When you move user mailbox you also need to add user to new dial plan
12. Mailbox moves:
· 1 Gb mailbox could take 90 minutes to move:
a. Pain: user is disconnected for duration
b. Pain: your SLA for availability is not met
· Online move mailbox:
a. new feature in 2010
b. users remain online while mailboxes are moved: at end of move user is briefly disconnected as recently received messages are copied over, client autodiscover new database location
c. admins can perform migration and maintenance during regular hours
d. online: 2007, 2010 -> e2010 exchange online
e. offline: 2003-> 2010
f. commandlets available for mailboxes very powerful, it also gives reporting and granularity for the details of move
13. mailbox move demo:
· option to move local and remote (hosted service)
· you can track move requests and their status
1. New form 2007 to 2010:
· Run exchange server yourself, or use exchange online
· High availability solution for mailboxes is database availability group (DAG)
a. Also provides site reillience3 and dr
b. 30sec failover with simplified admin experience
c. Works with cheap disk
d. Replaces SCR, LCR, SCC and CCR from 2007
· EMC (Exchange mangement console) client access server
a. Improved high availability solution: outlook MAPI connects directly to CAS
B. Transition:
1. In nutshell:
· Transition ad site by ad site
· Start with internet facing AD sites
· Upgrade all your existing servers to SP2
· Deploy 2010 servers CAS first, MBX last. Start with few and gradually add more servers as you move mailboxes
2. Steps:
· Legacy hostname for old FE/CAS
· SSL cert purchased
· End users don’t’ see this host mane
· Used when auto discover and redirection form cas2010 tell clients to talk to fe2003 /cas 2007 for MBX 2003 and MBX 2007 access
3. Move:
· Internet host manes to cas2010
· Um phone number to um 2010
· SMTP end point to hub2010
·
4. Move mailboxes
5. Decommission old servers
6. Move to next AD site
C. Prerequisites:
1. Windows server 2008 sp2 or r264 bit, standard, enterprise...
2. Client supported , outlook 2007, enterouge 2008, outlook 2010
D. Tools for migration:
1. Remote connectivity analyzer:
· https://www.testexchangeconnectivity.com
· In beta
· Features: Active sync connectivity test
· Use this tool validate any change
E. Migration/Deployment:
1. Setup:
· Step by step instructions in setup app
· Setup.exe with parameters gives unattended setup
· Try it this week – UNC14-HOL
· Configure 2010:
a. Your preferred configuration
b. External cas hostname: mail.andaker.com. exernalURL parameters
2. Certificates and SSL
· Best practice: minimize the number of certificates:
a. 1 certificate for all CAS serves + reverse proxy + edge/hub
b. Use ‘subject alternative name” (SAN) certificate which can cover multiple hostnames
c. Don’t list machines hostnames in certificated hostname list: use load balance (LB) array
d. Minimize the number of host names
3. CAS load balancing:
· Best practice: use ‘split dns” for exchange hostnames used by clients. Goal: minimize number of hostnames
a. Mail.andaker.com for exchange connectivity on intranet and internet
b. Mail.andaker.com has different IP addressing intranet/internet DNS
· Here’s the gotcha: OWA and EWS load balancing require client <-> sever affinity:
a. Client –IP based window NLB or LB device using cookie based affinity
· Tell autodiscover where to send clients : configure internal URL and externalURL parameters on virtual directories:
a. E.g. Set-owavirtual directory
4. Certificates: step by step
· New-exchange Certificate*
· You can also use certificate wizard
a. Takes you through list of questions to list all host names you need
b. The rtm version will include configuration for legacy CAS
5. Switching to 2010 CAS:
· configure reverse proxy (eg.isa) or external dns to point legacy.anddaker.com to fe2003/cas2007
· transition from 2003: ensure owa can redirect user to correct URL: configure exchange 2003 url parameter on CAS2010 owa virtual directory
· test before the plunge: legacy.andakercom works for internet access
6. the plunge:
· transition from 2007: tell CAS2010 how to send users to CAS2007:
a. configure externalURL parameter on cas2007 virtual directories (OWA, EAS, EWS, OAB..) to point to legacy.andake.com
b. tests that cas 201o is redirecting
· configure reverse proxy or dns:
a. switch mail.candakar.com to go to 2010 cas and edge/hub
b. users will start using 2010
7. demo:
· setting the virtual directory on 2010 to point exchange 2003 users to right directories by use of -external2003URL
· view from ISA server: publishing 2010 rules on ISA:
a. you can go to paths and create new path mappings for 2010 (e.g., /ews/*, /autodiscover)
b. update the DNS records pointing to 2007 to 2010
· run test exchange connectivity
· you get the logon page of 2010 but it redirects to owa 2003
8. client access transitions:
· client access cas2010
· four different things happen for 2003/2007 mailboxes
a. autodiscover tells clients to talk to cas 2007
b. http redirect to FE (front end 2003 or CAS 2007
c. praying of requires form CAs 2010 to CAS 2007: for pop and imap there is no redirection
d. direct CAS 2010 support for the service against BE 2003 and MBX 2007
9. smtp transport transition:
· upgrade existing servers to sp2
· introduce 2010 servers
· switch edge DNS + stmp to go to hub2010, you can continue to use 2007 edge just change out the subscription
10. Exchange UM:
· Introduce 2010 UM
· Add the UM to dial plan you already have
· Configure gateway
· You tell everyone to talk to 2010 first. 2010 is smart enough to redirect users on 2007 to 2007 UM
11. Exchange UM: OCS
· You need to add new dial plan\
· When you move user mailbox you also need to add user to new dial plan
12. Mailbox moves:
· 1 Gb mailbox could take 90 minutes to move:
a. Pain: user is disconnected for duration
b. Pain: your SLA for availability is not met
· Online move mailbox:
a. new feature in 2010
b. users remain online while mailboxes are moved: at end of move user is briefly disconnected as recently received messages are copied over, client autodiscover new database location
c. admins can perform migration and maintenance during regular hours
d. online: 2007, 2010 -> e2010 exchange online
e. offline: 2003-> 2010
f. commandlets available for mailboxes very powerful, it also gives reporting and granularity for the details of move
13. mailbox move demo:
· option to move local and remote (hosted service)
· you can track move requests and their status
No comments:
Post a Comment