• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
E-Guide: Definitive Guide to Exchange Server 2010 Migration—Chapter 3

E-Guide: Definitive Guide to Exchange Server 2010 Migration—Chapter 3



The process of moving from Exchange Server 2003 or Exchange 2007 to Exchange 2010 as a transition, not a migration, as many refer to it. While this may seem like simple semantics, there is a reason ...

The process of moving from Exchange Server 2003 or Exchange 2007 to Exchange 2010 as a transition, not a migration, as many refer to it. While this may seem like simple semantics, there is a reason behind it. A transition includes a period of time in which both the legacy Exchange servers and new versions of Exchange function in a coexistence scenario.



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds


Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial LicenseCC Attribution-NonCommercial License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    E-Guide: Definitive Guide to Exchange Server 2010 Migration—Chapter 3 E-Guide: Definitive Guide to Exchange Server 2010 Migration—Chapter 3 Document Transcript

    • CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010 Exchange 2003 HOME to Exchange 2010: PREREQUISITESFOR THE MOVE TO MAKING THE TRANSITION EXCHANGE 2010 REACHING OUT TO THE DEPLOYMENT ASSISTANT The transition from Exchange Server 2003 to Exchange 2010 is not simple. Skip a step along the way and the whole STEPS IN THE process becomes even more complicated. TRANSITION BY J. PETER BRUZZESE SHUTDOW: THE FINAL STAGES MICROSOFT REFERS TO the process of So how does the transition from moving from Exchange Server 2003 Exchange 2003 (or Exchange 2007) or Exchange 2007 to Exchange to that perfect state of Exchange 2010 as a transition, not a migration, 2010 happen? What’s involved? as many refer to it. While this may This chapter explains the complicat- seem like simple semantics, there is ed transition from Exchange 2003 a reason behind it. A transition to Exchange 2010, with a few points includes a period of time in which included for Exchange 2007 admin- both the legacy Exchange servers istrators. and new versions of Exchange func- tion in a coexistence scenario. The length of time the coexistence peri- PREREQUISITES FOR THE od lasts varies from company to MOVE TO EXCHANGE 2010 company and depends on the length The first step in moving to Exchange of time it takes to remove the last 2010 is to verify that your environ- legacy Exchange Server. ment meets the various prerequi- DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 2
    • CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010 sites. For example, make sure your member server of the domain on an existing directory service infrastruc- X64-based system running either ture is up to par by checking that Windows Server 2008 Standard or youve met the following criteria: Enterprise SP2 edition or Windows Server 2008 R2 Standard or Enter- Schema master: Confirm that it’s prise edition. Before installing Ex- HOME running Windows Server 2003 SP1 change 2010, both Exchange 2003 Standard, Enterprise or a later edition. and Exchange 2007 must be on SP2. PREREQUISITES The next prerequisite is to prepareFOR THE MOVE TO Global catalog server: In every the Active Directory schema for an EXCHANGE 2010 Active Directory site where you plan Exchange 2010 installation, which to install Exchange 2010, you need at you can do in a variety of ways. In least one global catalog server run- smaller Exchange installments where REACHING OUT TO THE ning Windows Server 2003 SP1 Stan- administrators are in complete con- DEPLOYMENT dard, Enterprise or a later edition. trol of upgrade decisions, you simply ASSISTANT start the installation using the graph- Active Directory forest: The AD ic setup; behind-the-scenes com- forest functional level must be run- mands and switches will run at that STEPS IN THE TRANSITION ning Windows 2003 forest func- point. However, if you are in an envi- tional mode. ronment that requires the process to be broken down into smaller pieces, SHUTDOW: Domain controller: AD domain take it one step at a time by running THE FINAL controllers must be running Win- the following switches: STAGES dows 2003 SP1 Standard, Enterprise or a later edition. Setup/PrepareLegacyExchange Permissions: This command, which Once you’ve verified this, check you can enter as /pl, is absolutely your environment for its readiness necessary for the transition from for Exchange 2010. In a smaller Exchange 2003 to Exchange 2010. environment, you can check this It ensures that permissions are pre- manually. In a larger Exchange Serv- pared between the two versions. er environment, it’s easier to down- load and use the free Exchange Pre- Setup/PrepareSchema: This com- Deployment Analyzer , which runs mand, entered as /ps, will extend an overall topology readiness scan. the schema. With Exchange 2010, in-place upgrades of an existing server are not Setup/PrepareAD: Entered as /p, possible. Therefore, you’ll need to the command runs the other two install Exchange 2010 on its own 64- commands if you haven’t started bit server. That server has to run as a them yet. This multi-tasked switch DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 3
    • CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010 will create Exchange security groups Exchange Server 2003 Exchange and prepare the local domain for System Manager. Note: The route Exchange. will be named DWBGZMFD01Q- NBJR. Setup/PrepareDomain or /Prepare Exchange also creates routing AllDomains: These switches (/pd group connectors between the HOME or /pad, respectively) create a new Exchange 2003 bridgehead routing global group called Exchange Install group and the Exchange 2010 serv- PREREQUISITES Domain Servers for the domain. er. You’ll also need to create anFOR THE MOVE TO They also add that group to the Ex- Exchange Administrative Group on EXCHANGE 2010 change System Objects container Exchange 2003; the group will be and the Exchange Servers group for named FYDIBOHF23SPDLT. the root domain. REACHING OUT TO THE DEPLOYMENT As a final prerequisite, you’ll need REACHING OUT TO THE ASSISTANT to do some patchwork changes to DEPLOYMENT ASSISTANT the Exchange 2003 environment to Before you begin the physical transi- allow it to communicate and perform tion to Exchange 2010, you should STEPS IN THE TRANSITION message transport with Exchange seek the help of Microsoft’s Ex- 2010. For example, Exchange 2010 change Server Deployment Assistant. creates an Exchange routing group Don’t let the tool’s initial screen, SHUTDOW: that is only visible using Microsoft shown in Figure 1, distract you. This is THE FINAL STAGES FIGURE 1. The Exchange Server Deployment Assistant DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 4
    • CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010 the newest iteration of the assistant, pany’s entire environment can han- which takes into account companies dle the upgrade to Exchange 2010, that want to coexist with a cloud- you still need to do more prep work. based hosted Exchange solution such If your organization has multiple as Microsoft Business Productivity sites, you’ll need to install the Online Suite (BPOS) or Office 365. Exchange 2010 server onto an HOME Our focus, however, is strictly on the Internet-facing site. on-premises option. I recommend administrators do a PREREQUISITES Once you select the "On-Premises typical installation of all three keyFOR THE MOVE TO Only" option, youll need to choose server roles—client access server, EXCHANGE 2010 from a range of options, including hub transport server and mailbox deploying from Exchange 2003 to server. However, some design archi- Exchange 2007, Exchange 2003 to tectures require that you deploy REACHING OUT TO THE 2010, Exchange 2007 to 2010 and a servers in stages. In these situa- DEPLOYMENT completely new install of Exchange tions, I recommend using the fol- ASSISTANT 2010 (Figure 2). The tool asks yes/no lowing order: questions to narrow down your needs during the transition. 1. Client access server (CAS) STEPS IN THE TRANSITION 2. Hub transport server 3. Unified Messaging server, STEPS IN THE TRANSITION which is optional SHUTDOW: Once you’re certain that your com- 4. Mailbox server THE FINAL STAGES FIGURE 2. Exchange 2010 deployment scenario choices DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 5
    • CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010 5. Edge transport server, which is Prep Outlook Address Book and optional. directories. Depending on how users access the email environment To secure external access with a in off-site situations, you may want CAS, you need digital certificates. It’s to enable Outlook Anywhere, con- recommended that you obtain a sub- figure the Outlook Address Book HOME ject alternative name certificate from (OAB) and Web Services virtual a reputable certificate authority (CA). directories or configure Exchange PREREQUISITES Since you will be running a coexis- ActiveSync settings. You’ll also needFOR THE MOVE TO tence environment, you will need at to change the OAB generation serv- EXCHANGE 2010 least three different namespaces— er to Exchange 2010. one for the current namespace, one Once you are ready to move the for the legacy namespace and one for OAB to Exchange 2010, go to Proper- REACHING OUT TO THE autodiscover. If your company con- ties and choose Web-based distribu- DEPLOYMENT nects to its mail through mail.compa- tion from the Distribution tab. This is ASSISTANT nyname .com, which is one fully quali- the modern method for Exchange fied domain name (FQDN), you 2007 and Exchange 2010 servers, so should also register autodiscover.com- you don’t need public folders or pub- STEPS IN THE TRANSITION pany name.com and legacy.company- lic folder distribution. From the name.com. Finally, you’ll need to install Actions pane, choose Move and then the certificate on the legacy Exchange the Exchange 2010 server that will SHUTDOW: 2003 servers. host the OAB. THE FINAL If you’re trying to expedite the STAGES transition or plan to move all Transition inbound/outbound Exchange mailboxes over in one fell mail flow. Now you’ll need to swoop, you don’t need to be con- reroute outbound Internet mail flow cerned with legacy host names. from Exchange 2003 to Exchange You’ll need only a subject alternative 2010. With the implementation of name certificate for the current the edge transport server role, Send/ namespace and autodiscover. Receive connectors will work out of During the transition to Exchange the box because the edge transport is 2010, one user’s mailbox may automatically configured to send and reside on Exchange 2003 while receive email. However, if you forego another resides on Exchange 2010. installing the edge transport server With the legacy namespace, all role, you’ll need to make some config- users—no matter which server ver- uration changes to the hub transport sion their mailboxes reside on— server. In addition, you’ll need to need to type only one thing to change Send connectors and Receive access Outlook Web App or connectors on the hub transport serv- ActiveSync services. er. Receive connectors are created by DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 6
    • CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010 default; they’re not configured to mailbox moves can occur simulta- allow anonymous inbound mail flow. neously. To move them, open the Exchange users can send mail inter- Exchange Management Console nally but cannot receive external mail (EMC) and use the New Local Move unless Receive connectors are proper- Request. Once you’ve moved all ly configured. mailboxes, go back and convert HOME To configure Receive connectors, them to resource mailboxes for go to the Server Configuration node rooms or equipment, as needed. PREREQUISITES and locate Receive connector set-FOR THE MOVE TO tings under the hub transport server EXCHANGE 2010 side. Then go to the Permissions SHUTDOWN: THE FINAL STAGES Groups tab and select Anonymous When you’re certain that you’ve Users to allow Internet-based email moved all mailboxes over to REACHING OUT TO THE to enter the organization. Exchange 2010—and you must be DEPLOYMENT certain because you cannot leave ASSISTANT Clean up public folders. If your anything behind in a storage organization is using public folders, group—you can move the Recipient you’ll need to set up a public folder Update Service (RUS) to Exchange STEPS IN THE TRANSITION database in Exchange 2010 and 2010. This step is a bit of an anom- create replicas of the data. Then aly since Exchange 2010 doesn’t remove legacy Exchange servers actually use the RUS. You cannot SHUTDOW: from the list of replicated folders so uninstall Exchange Server 2003 THE FINAL that all content resides on Exchange from an environment if it’s the only STAGES 2010. Set aside plenty of time for server running the RUS. First you’ll this step; replicating public folders— need to use Exchange System Man- especially if your public folder tree ager to enable the RUS on another has sprawled out of control—is a server. Moreover, you can’t uninstall time-consuming process. You might Exchange Server 2003 from an envi- even want to set aside a day for this ronment server if it’s the only server and perform a few tests afterward in a mixed-mode architecture that’s to be sure all data moved. running Site Replication Service (SRS). You’ll have to enable SRS on Move Exchange 2003 mailboxes. another Exchange Server first. When you move a mailbox from After you create the Recipient Exchange 2003 to Exchange 2010, Update Service , you may need to you must take the mailbox offline. enable Site Replication Service on a So, plan to move mailboxes after second Exchange server. Be sure to regular business hours. This is dif- clear away all bridgehead informa- ferent when you upgrade from tion and routing group data before Exchange 2007 to Exchange 2010— you try to uninstall RUS. DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 7
    • CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010 Once you’re completely confident that all mailboxes have been moved to Exchange 2010, you’ve replicated all public folder databases and and youve taken care of other odds and ends such as the RUS, the last step is HOME to click Add or Remove Programs on Exchange Server 2003 and uninstall it. PREREQUISITES Cathleen GagneFOR THE MOVE TO EXCHANGE 2010 Editorial Director here are fewer steps involved T in removing Exchange 2007 simply because you dont have to cgagne@techtarget.com REACHING OUT worry about items like the Recipi- TO THE ent Update Service (RUS) and Site DEPLOYMENT Matt Gervais ASSISTANT Replication Service (SRS). You Site Editor simply have to remove Exchange mgervais@techtarget.com 2007 from the Add or Remove Programs (in Windows Server STEPS IN THE 2003) or from Programs and Fea- TRANSITION tures (in Windows Server 2008). Michelle Boisvert Senior Managing Editor mboisvert@techtarget.com SHUTDOW: THE FINAL At this point, verify that your STAGES Exchange configuration is correct. Several tools are available to help Linda Koury Director of Online Design test external connectivity to the lkoury@techtarget.com new Exchange environment, includ- ing the Exchange Best Practices Analyzer (ExBPA) and the Exchange Marc Laplante Remote Connectivity Analyzer Publisher (ExRCA). I mlaplante@techtarget.com J. Peter Bruzzese, Triple-MCSE, MCT, MCITP: Enterprise Messaging, is an Exchange MVP, an Exchange Instructor for Train Signal and the TechTarget co-founder of ClipTraining.com. He is a technical 275 Grove Street author for Que Publishing, has produced hun- Newton, MA 02466 dreds of articles and videos about Exchange www.techtarget.com Server, and speaks at a variety of conferences. He is a frequent contributor for TechTarget’s SearchExchange.com and InfoWorld. Follow him ©2011 TECHTARGET. ALL RIGHTS RESERVED. on Twitter. DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 8
    • RESOURCES FROM OUR SPONSOR• Exchange 2010: Performance Enhancement• Hosting vs. In-House Implementation of Exchange 2010: It’s Decision Time• Presentation Transcript: Exchange 2010 Roadmap Series - Transition and MigrationAbout Dell, Inc. and Intel:Dell and Intel have worked together for years to bring you end-to-end solutions that improvebusiness productivity, increase performance and reduce your total cost of ownership (TCO)across the enterprise.