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


Published on

Walk through the process for introducing Exchange 2010 servers into an Exchange 2003/2007 organisation. Learn the pre-requisites, steps required, and the impact to client access for MAPI, Outlook Anywhere, OWA, ActiveSync, and POP/IMAP clients after the upgrade has occurred.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • SituationBefore we dive into Exchange 2010, let’s talk about the vast improvements made from 2003 to 2007Slide objectiveSet the stage with background on what has changed from source Exchange 2003 organizations.Talking points
  • SituationNow, let’s see the next step – what has changed from 2007 to 2010Slide objectiveSet the stage with background on what has changed from Exchange 2003 organizationsTalking pointsWe’ve listened to our customers and have simplified, but yet, made more powerful our HA solutionFlexibility of deploymentSome other technical changes – for customers that leverage these technologies
  • Situation :People use many different platforms to communicate these days. From getting a message on the go on your cell phone to sending out a contract proposal at a desktop; users are looking for ways to keep in better touch as their mobility increases. Access though Macs, PCs, Web Browsers and Cell phones all are a critical part of the connected infrastructure that allows businesses to increase their productivity and decrease decision making time. Talking Points :Rich desktop clients are available for both PCs and Macs though Outlook and EntourageRich web browser access to OWA premium is now available for 99% of the browser market. Users can use IE for the premium experience they have come to expect, or use Safari and Firefox for very similar premium experiences. OWA Lite is still available for those with restricted bandwidth or accessibility needs.Exchange ActiveSync (EAS) is fast becoming the standard for Push e-mail to smartphones. For almost any smartphone that an organization has decided to support, there is an Exchange ActiveSync enabled client available. There are other access methodologies not mentioned here: POP/IMAP/Outlook 2003, etc.Slide Objective:The Audience should walk away understanding that Exchange is providing the one stop for their communications needs. Exchange inboxes will be accessible from a wide variety of platforms and technologies. This broad access to rich Exchange data experiences allows them to be more flexible in their organizations while still having a consistent management story on the administrative side. This means lower costs with greater support for the platforms their organizations chooses to use; lower cost, greater choice.
  • SituationBefore you can begin deploying Exchange 2010 there are several preliminary requirements that must be completed.Slide objectiveExplain Exchange Server 2010 prerequisites so that when admins deploy it there are no surprises.Talking pointsPrepare the AD forest Make sure that the existing Exchange organization meets the requirements for installing install Exchange 2010No Support for RODCUse 64 bit domain controllers if possibleThere are schema changes!Commitment to non-deprecationNo hard requirement for Windows Server® 2008 Active Directory® (AD)At least one Windows 2003 Service Pack 2 (SP2) global catalog in each site where Exchange Server 2010 domain-joined server roles will be installedThe AD must be at least in Windows Server 2003 forest functionality modeNo support for read-only domain controller (RODC)/read-only global catalog (ROGC)Additional resources“Active Directory Performance for 64-bit Versions of Windows Server 2003”http://www.microsoft.com/downloads/details.aspx?FamilyID=52e7c3bd-570a-475c-96e0-316dc821e3e7&DisplayLang=en
  • SituationStep-by-step instructions help you install Exchange easily Slide objectiveInstalling Exchange 2010 is very straightforward and available through a GUI interface or a scriptable shellAids to handle common scenarios and interoperability needsTalking pointsOut-of-the box integration with Exchange 2003 and Exchange 2007Step-by-step instructions and parameters
  • SituationThrough the iterations of Exchange, there have been many additions and removals of virtual directories needed to be published for exchange to work externally. Slide objectiveShow what is needed as far as namespaces and virtual directories in Exchange 2010Show what has changed from their current experienceTalking pointsOutlook Web App is the new name for Outlook Web Access to give common look and feel across all of the Office Web AppsNew: ECP is added giving self-service for users/unifiedmessaging is not needed any more as the service runs through Exchange Web Services
  • SituationSSL certificates are a challenge that can provide security for an organization if done correctly.Slide objectiveUse a SAN cert to reduce complexityMinimize different certificatesTalking pointsUse “Subject Alternative Name” (SAN) certificate which can cover multiple hostnamesUse Load Balance (LB) arrays for intranet and Internet access to serversBest practice: Minimize the number of certificates
  • SituationIf you would like to use the Exchange Management Console to create the certificate request, it is possible and easy. You can import and enable via shell as well.Slide objectiveHere is a sample of what a certificate request would look like. Talking pointsUse the new-, import-, and enable-exchangecertificate commands to secure the server roles with certificates
  • If you would like to host your demo on the Virtual Server, please use the myVPC demo slide, not this slide.
  • SituationChoosing how to manage DNS has been complicated in the past. We now recommend using split-brain DNS for Exchange environments to minimize certificate and user training complexitySlide objectiveUsing the same namespace internally and externally is recommendedTalking pointsUse the same name space internally and externally.This will mean that changes to the external zone need to be manually created internallyPlanning for all external records should be done prior to deploying
  • SituationCAS is now at the forefront of server roles as it manages all client connectivity. High availability and redundancy for this role is paramount.Slide objectiveDetermine the path and technology for load balancingMake sure that the Web Service virtual directory, client access array and mailboxdatabase are set accuratelyTalking pointsOWA and EWS load balancing require ClientServer affinityTell Autodiscover where to send clients: Configure internalURL and externalURL parameters and virtual directoriesTell Outlook clients where to go for intranet MAPI access
  • SituationCAS is now at the forefront of server roles as it manages all client connectivity. High availability and redundancy for this role is paramount.Slide objective5 virtual directories in particular need to have internalURL and externalURL set based on whether the AD site is internet facingTalking pointsIf the site is not Internet facing, never set the ExternalURL parameterIf the site is Internet facing, always set the ExternalURL to NLB FQDNFor /OWA set the internalURL to Server FQDNFor all other Virtual Directories, set the internalURL to NLB FQDN
  • SituationUpgrading to Exchange Server 2010 is designed to be as easy as possible. Slide objectiveGive the audience an idea of what’s involved in upgrading, beginning with how to migrate Internet-facing sites.Talking points Start with diagram of a typical exchange architecture where you have one site which is Internet facing, and the second site on the right is an internal site which is accessed through the CAS to CAS proxy mechanism. For the Exchange 2003 environments the CAS server is the front-end server, and you can see that we have a URL for OWA for the users – mail.contoso.comWhen moving to Exchange 2010: First determine which order you need to upgrade your sites in. Assuming you have Exchange servers in more than one site, you will want to start with any Internet-facing AD Sites. The general pattern of upgrading is from the outside in – so anything facing the Internet is migrated first, followed by the internal sites. The first step in the upgrade is to install Service Pack 2 onto any Exchange 2007 servers you have in that site. We have included some fixes in Sp2 to improve the interop experience with Exchange 2010. After that, you can start to deploy your Exchange 2010 servers. You start with the CAS servers, then HUB, UM and lastly the Mailbox servers. The third step is what we’ll discuss most in this presentation: moving the Internet host name for your Exchange servers to point to the new Exchange 2010 servers. In the diagram, mail.contoso.com is what provided OWA access before. Now you redirect this name so that it is pointing to the new Exchange 2010 CAS server. At the same time, you want to set up some other host name (here we have called it legacy.contoso.com) and make that point to your older CAS or frontend servers. An alternative to using a different host name for your existing OWA environment may be to use the same name with an alternative port number. Setting up the legacy Exchange host name enables Exchange 2010 to redirect users to the older servers until they have been moved to Exchange 2010. Users will in most cases never have to remember this legacy hostname. It is just something which is used under the covers to support the redirection between the old and new environments. You may need to get an SSL certificate to support this old or legacy name End users continue to use the same name they used before – in this example mail.contoso.com – for all their configuration or external access to the Exchange system. For existing Exchange 2007 customers, the UM phone number will also have to be pointed to the new Exchange 2010 UM Server. Once you have done this, your environment is setup to support both the old Exchange mailboxes as well as the new Exchange mailboxes, and you are can start moving mailboxes from the old Exchange servers to the new Exchange mailbox servers. Once you have migrated the Internet facing sites, you can move on to migrating the Internal facing sites.
  • SituationProblems can arise during an upgrade process. We have a variety of tools to make your upgrade easier.Talking pointsA number of tools are availableUse RCA at every step of an upgradeTroubleshooting Assistant is great for mailflow and database issuesLoad Generator is a great way to test your storage solution before deploymentBest Practice Analyzer is a great health check for your Exchange organizationSlide objectiveTools are available to ensure your success
  • If you would like to host your demo on the Virtual Server, please use the myVPC demo slide, not this slide.
  • SituationNow, let’s go through what the actual steps are to switch over to a CAS infrastructure on Exchange 2010Talking pointsThese are preparatory steps before actually performing a switchWalk through the steps and give examplesMake sure to test each step by using Exchange RCASlide objectiveMake sure audience is comfortable with the 8 basic steps on how to prepare to get to CAS 2010
  • SituationNow, let’s go through what the actual steps are to switch over to a CAS infrastructure on Exchange 2010Talking pointsThese are preparatory steps before actually performing a switchWalk through the steps and give examplesMake sure to test each step by using Exchange RCASlide objectiveMake sure audience is comfortable with the 8 basic steps on how to prepare to get to CAS 2010
  • SituationOnce the preparation is complete, we can now switch the service over to CAS 2010 from Exchange 2003 Front-End or Exchange 2007 CAS for an AD-SiteTalking pointsOnce step 1 is done, the service is liveStep 2 and 6 are vital for getting a properly configured autodiscover service to be reachableMake sure to test each step by using Exchange RCASlide objectiveMake sure audience is comfortable with the 6 basic steps on switching to CAS 2010
  • SituationCAS 2010, by default, minimizes end-user impacting behavior. Here is how each service uses the 4 technologies.Talking pointsOWA will try to redirect (with Single Sign-On for Forms-Based Authentication). This prevents a user from having to learn a new URL or type in a password twice.Exchange Activesync will do Autodiscover and redirect (WM6.1 and newer for Exchange 2007), Proxying (WM6 and older, all non-Microsoft OS for Exchange 2007), Direct CAS2010 access (for Exchange 2003).Clients which use new EAS2010 features need to re-syncOutlook Anywhere,Offline Address Book, and autodiscover will do direct CAS2010 supportExchange Web Services will use autodiscoverPOP/IMAP will do proxy for Exchange 2007 and Direct CAS2010 for Exchange 2003Slide objectiveNo matter the protocol, Exchange 2010 has your users in mind.
  • If you would like to host your demo on the Virtual Server, please use the myVPC demo slide, not this slide.
  • SituationAdmins need to know how to upgrade SMTP transport when deploying Exchange 2010.Slide objectiveShow the process in upgrading SMTP to use the Exchange 2010 serversTalking points We start with Exchange 2003 environment and an Exchange 2007 environment. The dash lines here mean either one or the other (2003 or 2007) is the ingress/egress point; you won’t have both.First upgrade all servers to SP2.Introduce 2010 servers.If you have Edge Transport deployed, you will re-subscribe your Exchange 2007 Edge servers with E2010 Hub Transport. At this point your Edge synchronization will now be managed via Exchange 2010 HubThen install Edge 2010.And then finally switch the endpoint for mail flow.
  • SituationUpgrading Unified Messaging systems is an important part of moving to Exchange Server 2010Slide ObjectiveTalking PointsUnified MessagingFirst add the Exchange Server 2010 UM server to an existing UM dial plan that contains Exchange Server 2007 UM serversThen configure each IP gateway or IP PBX to send all incoming calls to the Exchange Server 2010 UM servers within the UM dial planAfter all UM-enabled user’s mailboxes have been migrated to Exchange Server 2010 Mailbox server, the Exchange Server 2007 UM servers can be removed from the UM dial planUsers don’t need to change any configuration or connectivity behavior (e.g. URL they use) as part of migration Certificates for Exchange Server 2010Simplest way: wildcard for domain name (doesn’t work for WM5)SAN certificateWith IP PBX/GWAdmin ImpactPoint SIP GWs to send calls to UM2010 servers onlyUM2010 servers will redirect traffic to UM12 servers as requiredUser ImpactNone, except appearance of new featuresWith OCSAdmin ImpactOCS will now find the appropriate version of Exchange UM and redirect the call to that locationNo new dial plans are neededThis is contingent on a post RTM patch that is forthcomingUser ImpactNone, except appearance of new features
  • SituationPublic Folders continue to be a very important part of Exchange for some customers. Others wish to migrate or delete some of these folders.Slide ObjectiveTools are available to help you identify, monitor, and report against Public FoldersAccess methodology to Public Folders differTalking PointsThere is enhanced reporting for PFs. Get-PublicFolderStatistics now captures last user access – this will help determine which PFs to move, delete, or migrate to SharePoint.Outlook can access multiple versions of Public FoldersOWA will access a 2010 replica of a Public Folder
  • SituationIn the IT community, the metric used to measure availability is the percentage of time that a system is capable of serving its intended function. As it relates to messaging systems, availability is the percentage of time that the messaging service is up and running. The following formula is used to calculate availability levels:Percentage of availability = (total elapsed time – sum of downtime)/total elapsed timeAvailability is typically measured in “nines.” For example, a solution with an availability level of “three nines” is capable of supporting its intended function 99.9 percent of the time—equivalent to an annual downtime of 8.76 hours per year on a 24x7x365 (24 hours a day/seven days a week/365 days a year) basis. Talking PointsThe simple task of moving a 1 GB mailbox will take 90 minutes. If you measure this against an organizations’ SLA, you’ll find that the uptime agreement may not have been met.We wanted to allow regular maintenance and upgrade to Exchange 2010 while not increasing downtimeSlide ObjectiveMeasuring SLA for an organization is important. Regular maintenance may lead to unnecessary outages
  • Situation: Administrators commonly move mailboxes between servers and databases as part of maintenance activities or when migrating between Exchange versionsCurrently, moving mailboxes takes them offline -- end users experience an e-mail outage for the duration of the move. As mailbox sizes have grown, mailboxes take longer to move, and administrators have been forced to perform mailbox moves at night and on weekends to minimize disruptions for end usersSlide Objective:Describe how give administrators can use the new online move mailbox process to perform Exchange maintenance and migrations without sacrificing their evenings and weekends. Talking Points: In Exchange 2010, mailbox moves can be done in online mode: users remain can send, receive, and read e-mail while the contents of their mailboxes are moved to a new location Maintenance activities can now be performed during the day, rather than a nighttime or weekend maintenance window Migration to Exchange 2010 can be accomplished faster and with less end-user disruption For E12- E2010 moves to be online your E12 server will require SP2 otherwise the move will be offline during migration ?
  • SituationShown how to move to Exchange 2010Talking PointsExchange 2007 Service Pack 2 introduces new functionality and is required for coexistence with Exchange 2010Exchange 2010 CAS redirects, proxies, or provides direct access to the mailbox server depending on the client, protocol, and mailbox versionExchange 2010 UM, Hub, Edge have seamless upgrade paths as well.Online mailbox moves improves mailbox data migration by significantly reducing the user outage windowSlide ObjectiveRecap high level points in moving to Exchange 2010
  • UNC301 - Microsoft Exchange Server 2010 Upgrade and Coexistence with Exchange Server 2007 and 2003

    1. 1.
    2. 2. Exchange 2010 Upgrade and Coexistence<br />Andrew Ehrensing<br />Principal Consultant<br />Microsoft Corporation<br />UNC301<br />
    3. 3. New from Exchange Server 2003 to Exchange Server 2007<br />Shift from front-end/back-end to a scalable role-based architecture<br />64-bit server support<br />Active Directory Sites replace Routing Groups<br />AutoDiscover to automatically configure users<br />Removes Outlook 2007+ need for Public Folders<br />Availability Service: Free/Busy information read direct from mailboxes, not from Public Folders<br />Offline Address Book download from Client Access Server<br />New admin tools<br />Unified Messaging: Get voice mail in your inbox<br />New Developer API: Exchange Web Services (EWS)<br />
    4. 4. New from Exchange Server 2007 to Exchange Server 2010<br />Flexible deployment choices<br />Run Exchange Server on-premises, use Exchange Online, or a hybrid approach<br />High Availability solution for mailbox resiliency<br />Comprised of database availability group and database copies<br />Provides site resilience and disaster recovery<br />30-second switchover/failover with simplified admin experience<br />Improves the flexibility in storage choices (SATA disks, JBOD configurations, etc.) <br />Replaces SCR, LCR, SCC, and CCR from E2007<br />64-bit management tools support<br />RPC client access and Address Book services<br />Improved High Availability solution<br />Outlook MAPI connects directly to Client Access Servers for mailbox-related data and directory requests<br />ExOLEBD, WebDAV, and CDOEx are gone<br />“Entourage EWS” uses EWS<br />
    5. 5. A familiar and rich Outlook experience across clients, devices, and platforms<br />Mobile<br />Web<br />Collaborate Effectively<br />Desktop<br />
    6. 6. Exchange Server 2010 Prerequisites<br /><ul><li>Active Directory
    7. 7. Windows 2003 SP2 global catalog server is installed in each Exchange Active Directory (AD) site
    8. 8. No hard requirement for Windows Server 2008 AD
    9. 9. Windows Server 2003 forest functional level
    10. 10. Exchange
    11. 11. All Client Access Servers (CAS) and Unified Messaging (UM) servers must have SP2
    12. 12. Existing servers are Exchange 2003 SP2 or Exchange 2007 SP2
    13. 13. Server
    14. 14. Windows Server 2008 SP2 or R2 64-bit editions (Std/Ent)
    15. 15. Windows Management Framework
    16. 16. .NET Framework 3.5 SP1
    17. 17. Internet Information Services (IIS)</li></li></ul><li>Starting Setup for Exchange 2010<br />Step-by-step instructions in setup app<br />Setup.com with parameters gives unattended setup<br />Setup provides specific settings for configuring your environment<br />Configure CAS External domain name<br />Sets ExternalUrl property which aids client configuration<br />E2003 routing groupconnector: E2003 server<br />
    18. 18. Namespaces and URLs<br />Exchange 2010<br />Exchange 2007<br />Exchange 2003<br />mail.contoso.com<br />mail.contoso.com<br />mail.contoso.com<br />Outlook Web Access<br />/exchange, /exchweb, /public<br />Exchange ActiveSync<br />/microsoft-server-activesync<br />Outlook Anywhere<br />/rpc<br />POP/IMAP<br />Outlook Mobile Access<br />/oma<br />Outlook Web Access<br />/owa<br />Exchange Web Services<br />/ews<br />Offline Address Book<br />/oab<br />Unified Messaging<br />/unifiedmessaging<br />Outlook Mobile Access<br />/oma<br />Outlook Web Access<br />Outlook Web App<br />Exchange Control Panel<br />/ecp<br />Unified Messaging<br />/unifiedmessaging<br />Note: the legacy vdirs will provide a 301 redirect experience to /owa<br />Autodiscover.contoso.com<br />smtp.contoso.com<br />legacy.contoso.com<br />E2003/E2007 services<br />Autodiscover<br />/autodiscover<br />Clients and SMTP servers<br />
    19. 19. Deploying SSL Certificates<br />Use “Subject Alternative Name” (SAN) certificate which can cover multiple hostnames<br />Site resilience scenario <br />If leveraging a certificate per datacenter, ensure that the Certificate Principal Name is the same on all certificates<br />Don’t list machine hostnames in certificate hostname list<br />Use Load Balance (LB) arrays for intranet and Internet access to servers<br />Best practice: Minimize the number of certificates<br />1 certificate for all CAS servers + reverse proxy + Edge/Hub<br />Additional certificate(s) if using Office Communications Server (OCS)<br />
    20. 20. New-ExchangeCertificate<br />-GenerateRequest<br />-Path c:certificates equest.req<br />-SubjectName “c=US, o=contoso Inc, cn=mail1.contoso.com”<br />-DomainNamemail.contoso.com, autodiscover.contoso.com, legacy.contoso.com<br />-PrivateKeyExportable$true<br />Certificate Creation<br />Create a Certificate Request file<br />Send Request file to certificate authority you are buying from<br />Use Import-ExchangeCertificate to activate newly acquired certificate<br />Use Enable-ExchangeCertificateto enable the certificate for use with a particular service<br />
    21. 21. Certificate Wizard<br />demo<br />
    22. 22. Deploying E2010<br />Topology Decisions—Split DNS<br />Best Practice: Use “Split DNS” for Exchange hostnames used by clients<br />Goal: Minimize number of hostnames<br />mail.contoso.com for Exchange connectivity on intranet and Internet<br />mail.contoso.com has different IP addresses in intranet/Internet DNS<br />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<br />
    23. 23. Deploying Exchange 2010<br />Topology decisions—CAS load balancing<br />OWA and EWS load balancing require ClientServer affinity<br />Client-IP based Windows NLB or LB device using cookie-based affinity<br />Tell Autodiscover where to send clients: Configure internalURL and externalURL parameters and virtual directories<br />Example: Set-WebServicesVirtualDirectory cas2010ews* -ExternalURL https://mail.contoso.com/ews/exchange.asmx<br />Tell Outlook clients where to go for intranet MAPI access<br />Use New-ClientAccessArray and set-mailboxdatabase<br />
    24. 24. Deploying Exchange 2010<br />Topology decisions—CAS load balancing<br />CAS AutoDiscoverServiceInternalUriproperty should be set to NLB FQDN<br />Ensure the Web Services property InternalNLBBypassURL is set to the Server FQDN<br />Configure virtual directory URLs according to this table:<br />
    25. 25. Upgrading to Exchange 2010<br />Internet Facing AD Site<br />2<br />Deploy E2010 Servers<br />Upgrade Internet-facing sites FIRST<br /><ul><li>Start small
    26. 26. Gradually add more servers to support scale</li></ul>4<br />Move Infra Pointers<br /><ul><li>Internet hostname switch
    27. 27. Unified Messaging switch
    28. 28. SMTP switch</li></ul>Internal AD Site<br />Proxy<br />https://autodiscover.contoso.com<br />https://mail.contoso.com<br />5<br />Internet<br />Move Mailboxes<br />E200x Servers<br />https://autodiscover.contoso.com<br />https://mail.contoso.com<br />https://legacy.contoso.com<br />Legacy hostnames for old FE/CAS<br />3<br />1<br />Upgrade servers to SP2<br /><ul><li>SSL cert purchase
    29. 29. End users don’t see this hostname
    30. 30. Used when new CAS tell clients to talk to legacy environments</li></ul>E200x Servers<br />Upgrade Internal sites NEXT<br />Decommission old servers<br />
    31. 31. Preparation Tools<br />Finding and solving problems before users do<br />Remote Connectivity Analyzer<br />Verify Internet-facing services are set up and configured properly<br />Troubleshooting Assistant<br />Help determine the cause of performance, mail flow, and database issues<br />Load Generator<br />Simulate and test how a server responds to e-mail loads<br />Best Practice Analyzer<br />Determine overall health of Exchange system and topology<br />
    32. 32. Exchange Remote Connectivity Analyzer<br />demo<br />
    33. 33. Switching to CAS2010<br />Preparatory steps<br />Obtain and deploy a new certificate that includes the required host name values<br />mail.contoso.com<br />autodiscover.contoso.com<br />legacy.contoso.com<br />Upgrade all Exchange servers to Service Pack 2<br />Enable Integrated Windows Authentication on Exchange 2003 MSAS virtual directory (KB 937031)<br />Install and configure CAS2010 servers<br />Configure InternalURLs and ExternalURLs<br />Enable Outlook Anywhere<br />Configure the Exchange2003URL parameter to be https://legacy.contoso.com/exchange<br />
    34. 34. Switching to CAS2010<br />Preparatory steps, continued<br />Join CAS2010 to a load balanced array<br />Create CAS2010 RPC Client Access Service array<br />Ensure MAPI RPC and HTTPS ports are load balanced<br />Install HUB2010 and MBX2010 servers<br />Configure routing coexistence<br />Configure OAB Web-based distribution<br />Create Legacy record in DNS (internal/external)<br />Create Legacy publishing rules in your reverse proxy/firewall solution pointed to FE2003 / CAS2007 array<br />Use ExRCA to verify connectivity for Legacy namespace<br />
    35. 35. Switching to CAS2010<br />The switchover<br />autodiscover…<br />mail…<br />legacy…<br />The switchover involves a minor service interruption<br />Update internal DNS and have Mail and Autodiscover point to CAS2010 array<br />Update/Create Autodiscover publishing rule and point to CAS2010 array<br />Update Mail publishing rules and point to CAS2010 array<br />Remember to update paths with new Exchange 2010 specific virtual directories<br />Reconfigure CAS2007 URLs to now utilize Legacy namespace<br />Disable Outlook Anywhere on legacy Exchange<br />Test that CAS2010 is redirecting/ proxying to CAS2007 (externally and internally)<br />ISA<br />1<br />2<br />2<br />E2010 CAS+HUB+MBX<br />E200x SP2<br />Clients access E2010 through Autodiscover… and mail…<br />1<br />Redirection (legacy…), proxying, and direct access to E2003/E2007<br />2<br />
    36. 36. Client Access Upgrade<br />Clients access CAS2010 first<br />Four different things happen for E2003/ E2007 mailboxes<br />Autodiscover tells clients to talk to CAS2007<br />HTTP redirect to FE2003 or CAS2007<br />Proxyingof requests from CAS2010 to CAS2007<br />Direct CAS2010 support for the service against BE2003 and MBX2007<br />
    37. 37. Exchange CAS Redirection<br />demo<br />
    38. 38. <ul><li>Follow this flow for each physical location
    39. 39. Edge servers are optional
    40. 40. Edge 2007 SP2 can be used with HUB 2010</li></ul>Step 5: <br />Switch Internet e-mail submission to Edge 2010<br />SMTP Transport Upgrade<br />Internet SMTP Servers<br />Step 4: <br />Install Edge 2010<br />E2010 Edge<br />E2007 Edge<br />Step 3: <br />Switch Edgesync +SMTP to go to HUB2010<br />E2010 HUB<br />E2007 HUB<br />E2003 Bridgehead<br />Step 1: <br />Upgrade existing E2003 and E2007 servers to SP2 <br />Step 2: <br />Install HUB and MBX 2010<br />E2003 Back-End<br />E2010 MBX<br />E2007 MBX<br />
    41. 41. Unified Messaging Upgrade<br />Step 1: <br />Introduce UM 2010 to existing dial plan<br />Step 2: <br />Route IP GW/PBX calls to UM 2010 for dial plan<br />Step 3:<br />Remove UM 2007 after mailboxes have been moved<br />IP PBX/ gateways: One Dial Plan, Redirect<br />With Office Communications Server: Will find proper UM server<br />
    42. 42. Public Folders<br />Co-existence support between mailbox server 2010 and mailbox server 2003/2007<br />Outlook can read mailbox from one Exchange version (such as 2010) and public folder from another (such as 2003/2007)<br />OWA 2010 will allow access to public folders with replica in mailbox server 2010<br />Get-PublicFolderStatistics help take action<br />Move<br />Delete<br />Migrate to SharePoint<br />
    43. 43. Service Level Agreement<br />Service availability during migration<br />1GB mailbox could take 90 minutes or more to move<br />Pain: User is disconnected for the duration<br />Pain: Your SLA for availability is not met<br />
    44. 44. Online Move Mailbox<br />Minimal disruption<br /><ul><li>Users remain online while their mailboxes are moved between servers
    45. 45. Sending messages
    46. 46. Receiving messages
    47. 47. Accessing entire mailbox
    48. 48. Administrators can perform migration and maintenance during regular hours
    49. 49. Also can be used to migrate users from on-premises server to Exchange Online</li></ul>E-mail Client<br />Client Access Server<br />Exchange 2010 and Exchange 2007 SP2 Online<br />Exchange 2003 Offline <br />Mailbox Server 1<br />Mailbox Server 2<br />
    50. 50. Key Takeaways<br />Exchange 2007 Service Pack 2 introduces new functionality and is required for coexistence with Exchange 2010<br />Upgrading server roles is seamless and without impact to end users<br />Online mailbox moves improves mailbox data migration by significantly reducing the user outage window<br />
    51. 51. question & answer<br />
    52. 52. Required Slide<br />Speakers, <br />TechEd 2009 is not producing <br />a DVD. Please announce that <br />attendees can access session <br />recordings at TechEd Online. <br />www.microsoft.com/teched<br />Sessions On-Demand & Community<br />www.microsoft.com/learning<br />Microsoft Certification & Training Resources<br />http://microsoft.com/technet<br />Resources for IT Professionals<br />http://microsoft.com/msdn<br />Resources for Developers<br />Resources<br />
    53. 53. UNC Track Call to Action!<br />Learn More!<br />Related Content at TechEd on “Related Content” Slide<br />Attend in-person or consume post-event at TechEd Online<br />Check out learning/training resources at Microsoft TechNet<br />Exchange Server and Office Communications Server<br />Check out Exchange Server 2010 atVirtual Launch Experience (VLE) at thenewefficiency.com<br />Try It Out!<br />Download the Exchange Server 2010 Trial<br />Take a simple Web-based test drive of UC solutions through the 60-Day Virtual Experience<br />
    54. 54. Required Slide<br />Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!<br />
    55. 55. Required Slide<br />© 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.<br />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.<br />