Migrating to Exchange 2010 and ad 2080 r2


Published on

Michael B. Smith

Published in: Technology
  • Be the first to comment

Migrating to Exchange 2010 and ad 2080 r2

  1. 1. Migrating to Exchange Server 2010 and Active Directory 2008 R2<br />A Case Study - In The Real World<br />
  2. 2. Michael B. Smith – remember the B!<br />Six year Exchange MVP<br />Consultant in Exchange, Active Directory, and Operational Best Practices<br />http://TheEssentialExchange.com/<br />Author, speaker, consultant<br />Exchange admin since 1996<br />Who Am I?<br />
  3. 3. Steps to prepare<br />Installing prerequisites<br />Installing Exchange<br />Configuring Exchange<br />Migrating objects<br />Removing Legacy Exchange Servers<br />Bumping Functional Levels<br />Q & A<br />Agenda<br />
  4. 4. Exchange Deployment Assistant<br />http://technet.microsoft.com/exdeploy2010<br />Good for basic info, doesn’t give you the “whole enchilada”<br />Build a lab!<br />Exchange Server 2010 Planning and Deployment guide on Technet<br />This presentation!<br />Getting Started<br />
  5. 5. Migration<br />Move to new (higher) version<br />New hardware<br />Same forest<br />Supports co-existence scenarios<br />Transition<br />Different hardware<br />Different forest<br />Export/Import only – no co-existence<br />No such thing as “upgrade”<br />Core Definitions<br />
  6. 6. Single-server environment<br />Process scales well<br />Must do these things regardless of size<br />Exchange 2003 native mode<br />Windows 2000 mixed-mode<br />Old boxes: Server 2003 SP2<br />New boxes: Server 2008 R2<br />Environment Used for Upgrade<br />
  7. 7. Exchange Organization: Clark<br />Exchange Admin Group: HQ<br />NetBIOS Domain: CLARK<br />AD Domain: clarksupport-hq.com<br />SSL certificate: mail.clarksupport.com<br />Old server: CLARK2K3<br />New server: CLARK2008<br />Logical Environment<br />
  8. 8. Complete coverage:<br />http://tinyurl.com/exchangeDC<br />Do NOT demote or promote DC after Exchange installation<br />Change of state is unsupported<br />ASP.Net breaks<br />Not recommended to install Exchange on DC, but fully supported (see SBS and EBS)<br />Exchange on Domain Controllers<br />
  9. 9. Exchange Native Mode (remember this?)<br />Exchange Prereqs #1<br />
  10. 10. If your Exchange organization is not already in native mode, see KB 272314, “XADM: Preparing a Mixed Mode Organization for Conversion to Native Mode”<br />Changing to native mode is easy, but prep work may take awhile – especially if Exchange 5.5 cleanup wasn’t done completely/properly.<br />Exchange Prereqs #2<br />
  11. 11. No Exchange 2000 servers installed<br />No Active Directory Connector - ADC<br />No Site Replication Service - SRS<br />Exchange 2003 Service Pack 2<br />Exchange Prereqs #3<br />
  12. 12. KB 937031 - “Event ID 1036 is logged on an Exchange 2007 server that is running the CAS role when mobile devices connect to the Exchange 2007 server to access mailboxes on an Exchange 2003 back-end server” <br />Required to properly enable CAS-2-FE proxy (or CAS-2-BE if no FE exists)<br />Applies to both 2007 and 2010<br />Exchange Prereqs #4<br />
  13. 13. Schema master FSMO running Windows Server 2003 sp1 or higher<br />At least one GC in site running Windows Server 2003 sp1 or higher<br />Windows Server 2003 DFL<br />Windows Server 2003 FFL<br />AD Prereqs #1<br />
  14. 14. AD Domains and Trusts Console<br />Right-click on domain name node and select “Raise domain functional level”<br />Right-click on “Active Directory Domains & Trusts” node and select “Raise forest functional level”<br />AD Prereqs #2<br />
  15. 15. Exchange 2003 and Exchange 2010 support DFL and FFL up to Windows Server 2008 R2<br />You must remove all Windows 2000 DCs and NT4 BDCs prior to raising DFL/FFL to Windows Server 2003<br />Can’t raise DFL/FFL above Server 2003 if Server 2003 DCs are in your AD<br />AD Prereqs #3<br />
  16. 16. Primary need for 2003 DFL/FFL:<br />Universal Groups<br />Impact of raising DFL/FFL<br />Beyond our scope<br />For most SMORG: little/no impact<br />See http://tinyurl.com/functionalAD<br />Final thought for AD:<br />Is the Exchange Server to be a DC?<br />Promote it NOW<br />AD Prereqs #4<br />
  17. 17. Exchange 2010 must be installed on x64<br />Server 2008 SP2 or Server 2008 R2<br />I recommend Server 2008 R2<br />Fewer pieces of software to install<br />Noticeably faster with CAS<br />If you choose Server 2080 SP2<br />Begin by installing PowerShell 2.0<br />KB 968929 - Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)<br />Exchange Install Prep #1<br />
  18. 18. To speed things up, copy Exchange DVD to local storage <br />We’ll assume D:Exchange2010<br />NO SPACES IN PATH NAMES (MSIExec gets weird with spaces sometimes)<br />Download most recent rollup and place in D:Exchange2010Updates<br />Today: KB 981401 (Update Rollup 3)<br />http://support.microsoft.com/kb/981401<br />Exchange Install Prep #2<br />
  19. 19. Quite frankly, I don’t care that servermanagercmd is deprecated in Server 2008 R2. It still works. And scripts using it work just fine in both 2008 SP2 and 2008 R2:<br />D:<br />Cd Exchange2010Scripts<br />Servermanagercmd –ip Exchange-All.xml -restart<br />Installing Roles and Features #1<br />
  20. 20. You can use (lots more complicated):<br />Deployment Image Servicing & Management (DISM)<br />Add-WindowsFeature<br />Next, download and install FilterPackx64.exe<br />2007 Office System Converter: Microsoft Filter Pack<br />Configure the ‘Net.TCP Port Sharing Service’<br />Somewhat dependent on your build process<br />Installing Roles & Features #2<br />
  21. 21. Logs in C:ExchangeSetupLogs<br />Most important log: ExchangeSetup.log<br />To update schema, you need Schema Admin and Enterprise Admin<br />To update forest perms, you need Enterprise Admin<br />To update domain perms, you need Domain Admin<br />To install a new Exchange server, you need Local Admin (server) & Organizational Admin<br />Installation – Key Concepts #1<br />
  22. 22. Using Setup GUI requires a user with:<br />Schema Admin<br />Enterprise Admin<br />Domain Admin<br />Local Admin<br />That user becomes first (only) Organizational Admin<br />User running “setup /PrepareAD” from cmd line becomes first Org. Admin<br />Installation – Key Concepts #2<br />
  23. 23. Prepare Forest Level Permissions to support Exchange 2003 and Exchange 2010 co-existence<br />Prepare/Update Schema<br />Prepare Forest Level Permissions to support Exchange 2010<br />Prepare Domain(s) to support Exchange 2010<br />Install Exchange roles<br />Installation Overview<br />
  24. 24. Requires Enterprise Admin & Domain Admin<br />Installation #1<br />
  25. 25. Requires Enterprise Admin & Schema Admin<br />Installation #2<br />
  26. 26. Again for Enterprise & Domain Admins<br />Installation #3<br />
  27. 27. If you have multiple domains in your Active Directory forest, an Enterprise Admin should now execute:<br /> Setup.com /PrepareAllDomains<br />An Exchange object cannot exist in a domain which has not been prepped for Exchange<br />Installation #4<br />
  28. 28. Now we can install Exchange itself<br />No longer any advantage to using setup.com<br />If you choose to:<br />setup.com /r:c<br />setup.com /r:h,m<br />(if using PowerShell, quote the /r parameter)<br />We will continue by using GUI, required perms: Local Admin, Domain Admin, & Organizational Admin<br />Installation #5 (Finally!!)<br />
  29. 29. Installation #6<br />
  30. 30. Click “Choose Exchange language option”<br />Use DVD languages (11 languages)<br />Download full language pack (30-odd languages)<br />You will return to prior window, click “Install Microsoft Exchange”<br />Accept the license agreement<br />Choose whether to send error reports to MSFT<br />Choose installation type (next slide)<br />Installation #7<br />
  31. 31. Installation #8<br />
  32. 32. Installation #9<br />
  33. 33. Next, choose the Exchange 2003 legacy server<br />Interop Routing Group Connector<br />Can be a FE or BE Exchange 2003 server<br />RGC to first HT in 2010 environment<br />If single BE, choose that<br />Next, choose whether to join CEIP<br />Installation #10<br />
  34. 34. Installation #11<br />
  35. 35. Installation #12 – Completion!<br />
  36. 36. No<br />We’ve just gotten started<br />Let’s blaze through basic configuration<br />(Easier than you might think)<br />(Well, maybe not)<br />Start Exchange Management Console<br />Slow<br />Even worse on first use<br />Are we done?<br />
  37. 37. Determine certificate requirements<br />Generate and install SSL certificate<br />Map certificate to IIS Services<br />Enable Outlook Anywhere<br />Move OAB generation to Exchange 2010<br />Create Internet send connector<br />Configure Default receive connector to accept Internet email<br />Move User Public Folders to Exchange 2010<br />Move System Public Folders to Exchange 2010<br />Configure the OWA Virtual Directory<br />Configure an IIS Redirection for Exchange 2010<br />Configure FBA on Exchange 2003<br />Update DNS<br />Req’d Configuration Overview<br />
  38. 38. Determine whether you will use wildcard (*.example.com) or SAN cert<br />Wildcard requires extra config<br />Wildcard introduces possibility of MitM<br />We won’t cover wildcard here<br />Can you use a single name cert?<br />Yes, BUT:<br />Requires extra config<br />Generates Outlook warnings<br />We won’t cover using a single name cert here<br />Basic Configuration #1<br />
  39. 39. Basic Configuration #2<br />
  40. 40. As discussed, we won’t use a wildcard certificate, just click Next<br />Determine the various “namespaces” used for Exchange services:<br />Incoming Email OWA<br />ECP EWS<br />AutoDiscover OA<br />POP IMAP<br />Legacy servers UM<br />We aren’t using UM, POP, or IMAP. So…<br />Basic Configuration #3<br />
  41. 41. Basic Configuration #4-a<br />
  42. 42. Basic Configuration #4-b<br />
  43. 43. Total list of names on UCC/SAN cert:<br />clarksupport.com<br />mail.clarksupport.com<br />autodiscover.clarksupport.com<br />legacy.clarksupport.com<br />Generally, you want the most used name to be the common name (shown on next slide)<br />Basic Configuration #4-c<br />
  44. 44. Basic configuration #5<br />
  45. 45. Basic Configuration #6<br />
  46. 46. Confirm your choices<br />Verify that the information on the “Organization and Location” dialog matches PRECISELY your domain registrar info<br />Send CSR to your provider of choice:<br />CertificatesForExchange.com<br />GoDaddy.com<br />VeriSign.com<br />Entrust.com<br />DigiCert.com<br />Many others<br />When you get it back, let’s install it!<br />Put the certificate into a file ending in .CER<br />Basic Configuration #7<br />
  47. 47. Basic Configuration #8<br />
  48. 48. Basic Configuration #9<br />
  49. 49. Basic Configuration #10-a<br />
  50. 50. Could also have done this in PowerShell:<br />Get-ExchangeCertificate |?{$_.FriendlyName -eq "All-purpose Exchange Certificate"} |Set-ExchangeCertificate –Services IIS<br />Which is easier?<br />Just depends on what you are used to and how often you need to execute this process.<br />Basic Configuration #10-b<br />
  51. 51. Basic Configuration #11<br />
  52. 52. Basic Configuration #12-a<br />
  53. 53. Or in PowerShell (if you accept the default authentication options):<br /> Enable-OutlookAnywhere –Server Clark2008<br />Definitely easier! <br />Basic Configuration #12-b<br />
  54. 54. Basic Configuration #13-a<br />
  55. 55. In PowerShell (if you have only one OAB, like 99.9% of Exchange installations):<br /> Get-OfflineAddressBook | Move-OfflineAddressBook –Server Clark2008<br />The PowerShell starts to make sense?<br />Basic Configuration #13-b<br />
  56. 56. Have to create a send connector<br />By default, Exchange 2010 doesn’t allow you to send Internet e-mail!<br />Basic Configuration #14<br />
  57. 57. Basic Configuration #15-a<br />
  58. 58. Basic Configuration # 15-b<br />
  59. 59. Basic Configuration #15-c<br />
  60. 60. Basic Configuration #15-d<br />
  61. 61. Basic Configuration # 15-e<br />
  62. 62. Or the PowerShell version:<br />New-SendConnector-Name 'Internet E-mail' <br /> -Usage 'Custom' <br /> -AddressSpaces 'SMTP:*;1' <br /> -IsScopedConnector $false <br /> -DNSRoutingEnabled $true <br /> -UseExternalDNSServersEnabled $false <br /> -SourceTransportServers 'CLARK2008'<br />Basic Configuration #15-f<br />
  63. 63. By default, Exchange 2010 cannot receive Internet email. You must enable “Anonymous users” on the Default receive connector<br />Basic Configuration #16-a<br />
  64. 64. Or the PowerShell:<br />Set-ReceiveConnector` -PermissionGroupsAnonymousUsers, ExchangeUsers, `ExchangeServers, ExchangeLegacyServers ` -Identity 'CLARK2008Default CLARK2008'<br />Basic Configuration #16-b<br />
  65. 65. Move the Public Folders<br />If all your users are on Outlook 2007+<br />And you don’t have any other PF data<br />Skip this step<br />Non-system PF data first:<br />cd $exscripts<br />.AddReplicaToPFRecursive.ps1 –TopPublicFolder `<br /> -ServerToAdd $env:computername<br />Basic Configuration - #17-a<br />
  66. 66. System PF data:<br />cd $exscripts<br />.AddReplicaToPFRecursive.ps1 `<br /> –TopPublicFolderNon_IPM_Subtree`<br /> -ServerToAdd $env:computername<br />No non-PowerShell solution shown here<br />Can be done from “Public Folder Management Console” in Exchange 2010 or ESM in Exchange 2003<br />Take 10 times longer. Or more.<br />Basic Configuration - #17-b<br />
  67. 67. Must be done from PowerShell<br />Set the redirection URL that will be used to route Exchange 2003 users during coexistence<br />Must’ve loaded the new SSL certificate to the Exchange 2003 server<br />Set-OWAVirtualDirectory Clark2008OWA* `<br /> -Exchange2003URL “https://legacy.clarksupport.com”<br />Basic Configuration - #18<br />
  68. 68. Optional<br />Add redirect from root of the Default Website to the OWA directory<br />You can disable SSL on the root<br />C:InetpubwwwrootDefault.html<br /> <html><br /> <head><br /> <meta http-equiv="refresh“ content="0;url=https://mail.clarksupport.com/owa"><br /> </head><br /> </html><br />Basic Configuration - #19<br />
  69. 69. On the Exchange 2003 server:<br />You MUST enable forms based authentication (FBA) for single sign-on to work<br />Important to do for a good user experience during co-existence<br />Basic Configuration - #20<br />
  70. 70. Change DNS<br />Rubber meets the road!<br />Exchange 2003 – becomes legacy.example.com<br />Exchange 2010 – becomes mail.example.com<br />Don’t forget to update MX (either now or later)<br />If all setup is proper as described, routing between servers is automagical<br />Everything should “just work”<br />Basic Configuration - #21<br />
  71. 71. Be default, mailbox databases in Exchange 2010 have a 2 GB limit on their mailboxes. If you have larger mailboxes, change the mailbox database config FIRST<br />You may want to consider enabling circular logging while you are doing mailbox moves (requires MSExchangeIS restart to take effect or to shut off)<br />The “Move Mailbox” process has been renamed to “Move Request”<br />Exchange 2003 -> 2010 moves are offline <br />Exchange 2010 -> 2010 moves are online<br />Moving Mailboxes<br />
  72. 72. Recipient Update Service is GONE<br />Recipient Policies are now split in two:<br />Retention Policies<br />Managed Folder Policies in Exchange 2007<br />Email Address Policies (EAP’s)<br />If you have custom EAP’s, AL’s, GAL’s, OAB’s – you will need to rework into OPATH syntax (LDAP filters are GONE)<br />Follow instructions at:<br />http://msexchangeteam.com/archive/2007/01/11/432158.aspx<br />Address List Management<br />
  73. 73. Quick overview:<br />Move ALL mailboxes off 2003<br />Remove ALL PF replicas from 2003<br />Route all SMTP to Exchange 2010<br />Update all GAL’s, AL’s, EAP’s, and OAB’s for OPATH<br />Remove domain RUS<br />Point enterprise RUS to 2010<br />Remove 2003 PF database (may require whacking)<br />Remove 2003 SMTP Connector (if present)<br />Remove Exchange 2003 (will require installation media to complete removal)<br />Retiring Exchange 2003<br />
  74. 74. Back to AD Domains & Trusts<br />Both Domain Functional Level<br />And Forest Function Level<br />Raising Functional Levels<br />
  75. 75. Q & A<br />