1 / 57

Satisfy Your Technical Curiosity

Learn why, how, and when to transition to Exchange 2007 for optimal efficiency and coexistence with legacy systems. Expert advice on planning, preparation, and deployment for a seamless migration process.

tanginika
Download Presentation

Satisfy Your Technical Curiosity

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SatisfyYourTechnicalCuriosity 27, 28 & 29 March 2007 International Convention Center (ICC) Ghent, Belgium

  2. Migrating to Exchange 2007: Why, How, and When? Ilse Van Criekinge ICT Consultant – Atos Origin NV/SA http://www.atosorigin.be http://www.pro-exchange.be

  3. Content • Introduction: Migrating vs Transitioning • Whybother? • Supportedtransitionscenarios • Planning forcoexistence • How? • Period of coexistence • Prepare and Remove last Exchange 2000/2003

  4. Introduction: Migrating vs Transitioning • Migration = Move to Exchange • From a non-Exchangemessaging system to an Exchange Organization • Fromone Exchange organization to a new Exchange Organization • Transitioning = Upgrade to Exchange • Move data fromanylegacy Exchange servers in yourorganization to new Exchange 2007 servers in sameorganiztion • Decommission the legacy Exchange servers

  5. Transitioning to Exchange 2007: Why, How, and When? Ilse Van Criekinge ICT Consultant – Atos Origin NV/SA http://www.atosorigin.be http://www.pro-exchange.be

  6. Content • Introduction: Migrating vs Transitioning • Whybother? • Supportedtransitionmigrationscenarios • Planning forcoexistence • How? • Period of coexistence • Prepare and Remove last Exchange 2000/2003

  7. Whybother?

  8. Content • Introduction: Migrating vs Transitioning • Whybother? • Supportedtransitionscenarios • Planning forcoexistence • How? • Period of coexistence • Prepare and Remove last Exchange 2000/2003

  9. Supportedtransitionscenarios

  10. Content • Introduction: Migrating vs Transitioning • Whybother? • Supportedtransitionscenarios • Planning forcoexistence • How? • Period of coexistence • Prepare and Remove last Exchange 2000/2003

  11. Planning forCoexistence • Coexistencepossiblewith Exchange 2003 or Exchange 2000 • Gain knowledge on: • AdministrationDifferences • Routing Differences • Licensing

  12. AdministrationDifferences • AdministrativeGroups are gone • Exchange Administrative Group (FYDIBOHF23SPDLT) • Exchange Server 2000/2003 • Exchange System Manager • Active Directory Users and Computers • Exchange Server 2007 • Exchange Management Console • Exchange Management Shell

  13. Routing Differences • Routing Groups are gone • Exchange Routing Group (DWBGZMFD01QNBJR) • Link-state routing is notusedby Exchange 2007 • Routing Topology is definedby: • Exchange 2000/2003: routing groups • Exchange 2007: Active Directory site topology

  14. LicensingDifferences • Microsoft Exchange Server 2007 • Standard Edition • EnterpriseEdition • Microsoft Exchange Server 2007 CAL • Standard CAL • Enterprise CAL

  15. Exchange 2007 does not support

  16. Content • Introduction: Migrating vs Transitioning • Whybother? • Supportedtransitionscenarios • Planning forcoexistence • How? • Period of coexistence • Prepare and Remove last Exchange 2000/2003

  17. How? • Collectinformation • Run ExBPAversion 2.7 • Prepare Active Directory • Deploy Exchange

  18. Collectinformation • Exchange organization settings; • Active Directory settings; • Network settings; • Exchange-awareproducts.

  19. Exchange 2007 Readiness Check • Scan yourexistingorganizationusing the Microsoft Exchange Server Best PracticesAnalyzerTool (ExBPA) • ExBPAversion 2.7 and later (http://www.exbpa.com) • Includesan Exchange 2007 Readiness Check • Results in Transitiondocumentation

  20. Prepare Active Directory • Prepare Legacy Exchange Permissions • Enables the legacy RUS to functioncorrectly • Prepare Schema (Setup /PrepareSchema) • Updates schema with Exchange 2007 specificattributes • Prepare AD (Setup /PrepareAD) • Configuresglobal Exchange objects in AD • Creates Universal SecurityGroups in root domain • Setup /PrepareDomain, Setup /PrepareAllDomains

  21. Prepare the Exchange Server • Hardware • x64 architecture-based computer • Min 2Gb RAM • Software • .Net Framework 2.0 + Update (Q926776) • Windows Powershell • MMC 3.0 • Updates • http://support.microsoft.com/?kbid=919166

  22. Deploy Exchange 2007 • Deploy and configureClient Access servers • Deploy and configure Edge Transport servers • Deploy and configureHub Transport servers • Deploy and configure Mailbox servers • Deploy and configureUnifiedMessaging Servers

  23. Transition • Replicate Public Folders • Move legacymailboxes to Exchange 2007 • Rehomeconnectors • Redirectinbound mail to Exchange 2007 • Rehomeoutbound mail connectors to Exchange 2007 • Decommission Exchange Legacy Servers

  24. Content • Introduction • MigratingvsTransitioning • Whybother? • Supportedtransitionscenarios • Planning forcoexistence • How? • Period of coexistence • Prepare and Remove last Exchange 2000/2003

  25. Coexistence: Administration • Use ESM or ADUC to manage Exchange 2000/2003, use EMC or EMS to manage Exchange 2007! • Global Settings are stored in the Active Directory directory service, maintainorganization-levelpermissionsusing EMC or Exchange Management Shell

  26. Coexistence: OWA • CAS isn’t FE • FE acceptsrequests and forwardsthem to the BE, who handles the business logic and renders the UI • CAS acceptsrequests, and CAS contains the business logic and renders the UI • Scriptmaps: ExProx.dll and DavEx.dll • Davex responds to both DAV and OWA requests • Davexredirects a requestbasedon the internal name of the server!

  27. Coexistence: Free/Busy Information • Exchange 2000/2003: Free/Busy System Public Folder • Exchange 2007: CalendarConcierge • CalendarAttendant • SchedulingAssistant • Resource BookingAttendant • Availability Web Service

  28. Coexistence: Availability Web Service Exchange Server 2007 Exchange Server 2003 Exchange Server 2007 2 3 4 5 1

  29. Coexistence: OAB • Exchange 2000/Exchange 2003 • OAB stored in system folder • Clients connect to system folder for download • Exchange 2007 & Outlook 2007 • OAB updated by Mailbox Server • OAB copied to CAS by the Microsoft Exchange File Distribution Service • Outlook 2007 uses web service to download OAB • OAB web publishing integrates seamlessly with the OAB in previous versions of Exchange Server

  30. Coexistence: Public Folders • Remember: De-Emphasized • For OWA, IMAP4, and NNTP Clients, maintain a replica of the public folders on a server running Exchange 2003 • For IMAP4 and NNTP clients, provide access to the public folder through an Exchange 2000 or 2003 FE server, or allow direct connection to Exchange 2000 or 2003 BE server

  31. Coexistence: RUS • Introduced in Exchange 2000 to discover and provisionrecipientobjects • Twofunctionalparts: • An API to calculate the appropriatepropertiesonrecipientobjects • A subservice in System Attendantwhich discovers the recipientsthatneed updating and stamps themwith the calculatedproperties

  32. Coexistence: RUS /cont’d • Keychange in Exchange 2007: recipients are fullyprovisioned as they are created • In mixed environment youwillneed a RUS foreach domain that has Exchange recipients, includingdomainswithonly Exchange 2007 servers and users present! • Workaroundsforasynchronousprovisioning • Update-EmailAddressPolicy • Update-AddressList • Note: LDAP vs OPATH

  33. Coexistence: Routing • Routing Exchange 2007 • Disable Minor Link State Updates

  34. From malcolmp@MBXB To: lwarman@MBXG; From malcolmp@MBXB To: lwarman@MBXG; Routing Exchange 2007 • Site-based • Keywords • Direct Connect • DelayedFan-Out • Queue at Point of Failure • Hub Sites

  35. Be Careful with Link State Updates • Two flavors • Minor Link State Updates • Major Link State Updates • Exchange 2007 • Doesn’t use Link State routing • Can not propagate link state updates • Minor Link state updates must be suppressed to prevent message looping when a route is recalculated

  36. Possible Routes Exchange Routing Topology Mail sent from RG1 to RG4 Site USA Site Europe Site Africa Site Asia Exchange Routing Group (DWBGZMFD01QNRBJR) E2K7 E2K7 RGC 1 RGC 10 Routing Group 1 Routing Group 2 Routing Group 3 Routing Group 4 RGC 1 RGC 1 RGC 1 E2K3 E2K3 E2K3 E2K3

  37. But Server in RG 3 is down Message will be rerouted Mail is Sent Site USA Site Europe Site Africa Site Asia Exchange Routing Group (DWBGZMFD01QNRBJR) E2K7 E2K7 RGC 1 RGC 10 Routing Group 1 Routing Group 2 Routing Group 3 Routing Group 4 RGC 1 RGC 1 RGC 1 E2K3 E2K3 E2K3 E2K3

  38. Message Rerouted to RG 1 MessageRerouted to RG E2K7 Site USA Site Europe Site Africa Site Asia Exchange Routing Group (DWBGZMFD01QNRBJR) E2K7 E2K7 RGC 1 RGC 10 Routing Group 1 Routing Group 2 Routing Group 3 Routing Group 4 RGC 1 RGC 1 RGC 1 E2K3 E2K3 E2K3 E2K3

  39. Message Looping Site USA Site Europe Site Africa Site Asia Exchange Routing Group (DWBGZMFD01QNRBJR) E2K7 E2K7 RGC 1 RGC 10 Routing Group 1 Routing Group 2 Routing Group 3 Routing Group 4 RGC 1 RGC 1 RGC 1 E2K3 E2K3 E2K3 E2K3

  40. Disable Minor Link State updates • Disables the ability to mark links Up or Down • Used when you have multiple routes to/from the Exchange 2007 Routing Group • Must be done to every Exchange 200x server in the organization • Forces Exchange 2000/2003 to use least cost routing • Controlled via Registry

  41. Coexistence: ActiveSyncAccess to Exchange 2003 mailboxes • EnableIntegrated Windows Authenticationon all Exchange ActiveSyncvirtual directories on Exchange 2003 Mailbox servers

  42. Coexistence: Backups • StreamingBackupDe-emphasized… • Exchange-aware backups are supported for both production and copy storage groups and databases using Volume ShadowCopy Service (VSS) technology. Streaming backups are only supported from the active node

More Related