You are on page 1of 20

The Expert's Guide for

Exchange 2003
Preparing for, Moving to, and Supporting
Exchange Server 2003

by Steve Bryant



Chapter 4 Installing Exchange Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . 65
Deployment Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Deployment Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Exchange Server 2003 Installation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
New Exchange 2003 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Upgrade from Exchange 2000 Native Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Coexistence with Mixed Mode Exchange 2000 and Exchange 5.5 . . . . . . . . . . . . . . . 69
Coexistence and Migration from Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Coexistence and Migration from Exchange 5.5: Step by Step . . . . . . . . . . . . . . . 70
Coexistence and Migration, Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Coexistence and Migration, Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Understanding ADC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
The ADC Tools Applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Deploying ADC Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Deploying the Resource Mailbox Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Deploying the Connection Agreements Wizard . . . . . . . . . . . . . . . . . . . . . . . 76
Coexistance and Migration, Phase 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
ExDeploy Command-Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Next: Multiple Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

and I felt that another wizard-like tool was unnecessary. The Exchange Server 2003 deployment toolset. but now the tools are included in the deployment toolset to let you inspect your domain. Most importantly. the installation is just a few mouse clicks away. and current Exchange systems.NET Magazine eBooks . In this chapter. ultimately. Many people don’t see the importance of a planning process and so don’t go through the planning stages I describe in this book. I wasn’t too excited about the new deployment tools Microsoft ships with Exchange Server 2003. I emphasize migrating an existing Exchange 5. users quickly learned about the required installation of SMTP. Administrators diagnosed problem installations with tools such as Dcdiag – and sometimes used ADSI Edit to inspect Active Directory (AD). installing Exchange has always been that easy – and therein lies a problem. Having covered upgrading one Exchange organization to another in Chapter 3. ExDeploy.5. I’ve come to really appreciate the deployment tools and recommend them to even the most seasoned Exchange administrators. resembles a wizard in that it walks you through all the requirements and provides links to multiple tools. in this chapter.5 and. Although I thought these requirements and tools were common knowledge. the new deployment tools introduce an important paradigm to installation: that administrators check the domain for errors before they introduce Exchange Server 2003. I’ve learned that they aren’t. You can predict problems rather than having to react to them. Microsoft Product Support Services (PSS) has used many of these tools to analyze Exchange Server installations. I discuss the new set of deployment tools for Exchange Server 2003 as well as ways to install Exchange Server 2003 programmatically. failure to consider Exchange server placement can negatively affect both performance and collaboration. and Microsoft IIS on the server. to migrate mailboxes. With Exchange Server 2000. Documentation about deployment is available online. I cover deploying Exchange Server 2003 in several scenarios – including a new (“greenfield”) installation and a migration from Exchange 5. After you meet the requirements discussed in the first three chapters. To reflect the range of deployment options.5 organization to Exchange Server 2003. Network News Transfer Protocol (NNTP). Outlook will perform poorly. For example. Deployment Tools Initially. DNS. including Dcdiag and ADSI Edit – Brought to you by Quest Software and Windows & . The new tools make preparation and installation easier. 65 Chapter 4: Installing Exchange Server 2003 You might have noticed that I’ve covered nearly everything you need to know about installing Microsoft Exchange Server 2003 except for the installation itself. Also. I discuss in some detail how to use the Active Directory Connector (ADC) to establish coexistence with Exchange 5. you’re more likely to understand and be able to solve any problems that arise. In fact. However. if you prepare for Exchange Server 2003 and know why you’re doing what you’re doing. Lack of planning can lead to problems. if you don’t place your Global Catalog (GC) servers properly.

other benefits include knowing that your AD is clean and functioning well and that the Exchange environment is provisioned correctly. I make it a habit to run ExDeploy instead of manually running the setup from the \i386 directory. but those minutescan save you hours spent troubleshooting. Even as a seasoned consultant.g. When you insert the Exchange Server 2003 media (e. The Exchange deployment tools provide a walkthrough that lets you mark off phases as you complete them. The tools also let you check your current environment before and immediately after the installation. CD-ROM. and more.66 The Expert’s Guide for Exchange 2003 to preemptively troubleshoot problems with AD. Tools in the set • check the Exchange 5. Doing so lets me double-check myself on specific steps and provides quick access to diagnostic tools. Deployment Tasks Deploying Exchange Server 2003 includes the following six phases: • Phase 1: Planning the deployment and checking the infrastructure • Phase 2: Checking and cleaning the Exchange 5.NET Magazine eBooks . From the list on this screen.. Later in the chapter. Systematically using ExDeploy’s preparation tools can add 20 minutes to the deployment phase.5 directory (if it exists) • Phase 3: Replicating the Exchange 5. DVD) autorun launches a setup file that displays a CD-ROM menu. I discuss ExDeploy’s options.5 Directory Configuration and Directory Objects • provide a Exchange 5.5 directory data • Phase 4: Provisioning the AD for Exchange • Phase 5: Installing the Exchange Server directory components • Phase 6: Moving mailboxes and removing legacy Exchange 5.5 Directory User Count • check Exchange and GC server versions • check ADC replication • run the NTDSNoMatch utility • check Organization and Site Names • run the Active Directory User Replication Scan • check policies • run the Organization Readiness Check • run the Public and Private Folder DS/IS checks • check the Exchange Server 2003 Configuration and Recipient Objects • run an Org Report Brought to you by Quest Software and Windows & . No joke! Of course.5 servers The overall purpose of the deployment toolset is to give you the tools and wizards you need to walk you through the installation – so you don’t have to call Microsoft Product Support Services (PSS). the ForestPrep process. select and click Exchange Deployment Tools to launch ExDeploy.

ExDeploy is actually exdeploy. these tools aren’t for you.1 shows. Figure 4. After you select the Exchange Deployment Tools option from the CD-ROM autorun screen. you’ll see the Exchange Server Deployment Tools screen. and it runs from within your browser. I’ll devote most of the discussion for each scenario to deploying the first Exchange 2003 server. which Figure 4. Initially. However.1 Exchange Server Deployment Tools Brought to you by Quest Software and Windows & . Because I lack space to cover an entire deployment. Exchange Server 2003 Installation Scenarios As I mentioned previously.NET Magazine eBooks .hta. Exdeploy. Chapter 4 Installing Exchange Server 2003 67 n Note For those of you who enjoy knowing the details. I want to emphasize two key points: • You can’t upgrade Exchange 5. You might want to explore third-party migration tools.exe is the command-line tool ExDeploy uses to perform the checks and create the logs. however. • Exchange Server Deployment Tools aren’t designed for inter-organization migration. I’ll discuss new installations of Exchange Server 2003 as well as migrations from Exchange 5. If you have two Exchange organizations. I’ll spend more time on the migration scenario because it’s more com- plicated and requires additional tools and procedures.5.5 Servers directly to Exchange Server 2003.

New Exchange 2003 Installation The simplest Exchange Server 2003 installation is a new one. Upgrade from Exchange 2000 Native Mode The next easiest installation is an upgrade from Exchange 2000 Native Mode. non-clustered server. you’ll see a new installation page that contains eight steps. After you make your selection. the appropriate screen will appear and list specific deployment tasks. you’ll be prompted to choose whether you plan to migrate from and coexist with Exchange 5. In fact. I recommend that you make sure the first server is a permanent.68 The Expert’s Guide for Exchange 2003 j Tip You can download the Exchange 2003 Deployment Tools from http://www. You should use the latest version of the installation tools. you’ll deploy ForestPrep and DomainPrep. you might choose to install a new Exchange Server 2003 server in your environment alongside your Exchange 2000 server or Brought to you by Quest Software and Windows & . then.aspx?FamilyID=271e51fd-fe7d-42ad-b621-45 f974ed34c0&DisplayLang=en. Before you can upgrade an Exchange 2000 server to Exchange Server 2003. The steps are designed to walk you through verifying that the target server has the appropriate services installed. select New Exchange 2003 installation. and system public folder server are assumed for the first server and don’t work correctly in a clustered environment. such as the Recipient Update Service (RUS). when prompted. saving the most complicated scenario for last.NET Magazine eBooks . Some roles. They offer instructions for deploying the Netdiag and Dcdiag tools to check network and domain health. or perform a new installation. then install the server. Routing Group Master. If you select Deploy the first Exchange 2003 server. Next. After you select Deploy the first Exchange 2003 server. I’ll discuss the scenarios in reverse the installation process is the same as the process for a new installation – except that you must address several components shipped with Exchange 2000 that Exchange Server 2003 no longer supports. you must remove the following components: • Instant Messaging Server • Chat • Key Management Service (KMS) • Lotus cc:Mail connector • Microsoft Mail (MS Mail) connector • Microsoft Mobile Information Server Event Sink • Any third-party email connector that’s not compatible with Exchange Server 2003 If your situation requires the use of one or more of these If you’re installing Exchange Server 2003 into your production network. upgrade from Exchange 2000.

then verify the connection agreements (CAs). Therefore. the Exchange 2000 version of ADC isn’t compatible with Exchange 2003. the difference between this scenario and the previous one is that this scenario uses the ADC.5 servers.5 servers. in this scenario.5 Brought to you by Quest Software and Windows & . you didn’t need to synchronize information in an Exchange 5. And. although you’ll already have configured ADC. Because the Exchange 2000 Native Mode installation contained no Exchange 5. Chapter 4 Installing Exchange Server 2003 69 servers. In a mixed environment. however. Keep in mind. your main task is to upgrade the ADC servers.5 scenario. however. In a Mixed Mode Exchange 2000 and Exchange 5. you must upgrade your front-end servers before you upgrade the mailbox servers.NET Magazine eBooks .5 directory with information in AD. Coexistence with Mixed Mode Exchange 2000 and Exchange 5.2 Coexistence with Mixed Mode Exchange 2000 and Exchange 5.5 and AD. that Exchange 2000 can’t act as a front-end to Exchange Server 2003. as Figure 4.2 indicates. you have Exchange 2000 and Exchange 5. which control synchronization between Exchange 5.5 Technically. Figure 4.

When you select Upgrade Active Directory Connector Servers. and running ADC Setup to upgrade the ADC servers.) All existing CAs will remain in place because they and their settings are still required.2 shows. deploying the first Exchange 2003 or Exchange 2000 server in an Exchange 5. you should run the ADC tools (which I’ll cover in detail later in the chapter). Coexistence and Migration from Exchange 5.” not an upgrade.NET Magazine eBooks . The deployment tools walk you through this scenario in detail. (If you think back to early Exchange 2000 documentation. prepping the domain.5 has its own directory.5 I’ve saved the “best” scenario for last – and devote the remainder of the chapter to it. Because Exchange 5. which Figure 4. After you’ve upgraded the ADCs. subsequent installations of Exchange 2003 or Exchange 2000 are fairly simple. the number and types of objects. The ADC tools will analyze the Exchange 5.) Coexistence and Migration from Exchange 5.5 migrations underscore the importance of AD to Exchange 2003 and Exchange 2000. The ADC and its settings differentiate this scenario from the previous one.5. the user count. The deployment tools divide the migration scenario into three phases.5 coexistence. you’ll recall that Microsoft always termed the move to Exchange 2000 a migration. You must Brought to you by Quest Software and Windows & . (You’ll need to run ADC Setup for each of your ADC servers. The ADC service performs this directory migration. you also run a group of tools known collectively as DSScopeScan. Phase 1 Much as you would in the Exchange 2000 coexistence scenario. you can upgrade existing Exchange 2000 servers to Exchange Server 2003 and install new Exchange 2003 servers into your environment.5: Step by Step The term migration is correct because directory information isn’t upgraded from Exchange 5.5 organization is the largest step in moving toward these later versions of Exchange.5 currently installed on the servers. to make its contents available in Exchange 2000. but you should know that the ADC servers must run the Exchange Server 2003 version of ADC before you deploy Exchange Server 2003 on any servers. The information is copied and the data is migrated. However. you must migrate the configuration and mailbox directory information to AD. you run Dcdiag and Netdiag. and the version of Exchange 5. you’ll see a new task list that contains six steps designed to walk you through extending the schema. Note that Microsoft terms this process a “migration. After this step is complete.5 server in your organization and determine its configuration. Exchange 5. After you’ve upgraded the ADCs.5 organization and can automatically create additional CAs as needed. Because of the necessary integration with AD. to verify that the CAs are configured correctly and that nothing else is required for Exchange 5. Coexistence and Migration.70 The Expert’s Guide for Exchange 2003 j Tip I’ll discuss the ADC service and CAs in much more detail shortly. DSScopeScan uses Lightweight Directory Access Protocol (LDAP) and credentials that you specify to connect to an Exchange 5.

In this case. and you launch OrgPrepcheck to check the results. Brought to you by Quest Software and Windows & .3 shows. Chapter 4 Installing Exchange Server 2003 71 have Exchange 5. During the procedure. those objects must be replicated to the Exchange 5. and groups. the Exchange Directory Service (DS) contains objects: mailbox objects. Before I discuss Phase 3 of the migration process. I’ll describe the ADC service and its function in some detail.5 coexistence scenario. Coexistence and Migration. Moreover. and configuration settings for the entire organization. Initially. ADC is a service that runs on a Windows 2003 or Windows 2000 server to perform directory synchronization. Understanding ADC [3] As I mentioned previously.5 Service Pack 3 (SP3) installed on at least one server in your organization before you deploy Exchange Server 2003.NET Magazine eBooks . custom recipients. the objects must first be replicated to the AD. as Figure 4. I’ll then resume the migration discussion with Phase 3.5 DS. You can find those results in the ExDeploy. distribution lists (DLs). I’ll discuss the version that comes on the Exchange 2003 CD-ROM or DVD in the \ADC\I386 folder.log file under the “+ Preparing Active Directory for Exchange Server 2003 (OrgPrepCheck)” section. The ForestPrep procedure will take about 20 minutes depending on the number of items in the domain and the performance of your server(s). Phase 2 In phase two of the migration to an Exchange 5. you can easily see where Exchange stores its settings within the Configuration Naming Context of the AD.5 users to see and use Exchange 2003 mailboxes. For Exchange 2003 to take advantage of those objects and settings. The account or group that you list will have Exchange Full Admin permissions to the organization. you’re prompted to enter the name of the account or group to use for subsequent installs. for Exchange 5. n Note You can install the ADC service only after you’ve executed ForestPrep and DomainPrep because the configuration settings for ADC are maintained within the Microsoft Exchange object that ForestPrep creates. you deploy ForestPrep and DomainPrep to provision AD. From among the several versions of ADC. I think you’ll soon see why a thorough understanding of ADC is essential. contacts. ADSI Edit is a handy tool for verifying AD changes. only this account or group will have permission to install Exchange Server 2003.

as Figure 4.3 Exchange settings in ADSI Edit During ADC installation.NET Magazine eBooks . so plan accordingly.4 shows.72 The Expert’s Guide for Exchange 2003 Figure 4. it’s best to install both. you’re prompted to install the Active Directory Connector Service and the Active Directory Connector Management components. For the initial installation. Brought to you by Quest Software and Windows & . Installing the ADC requires a reboot.

5 shows. Brought to you by Quest Software and Windows & . so you can administer the connection locally. which Figure 4.NET Magazine eBooks . Chapter 4 Installing Exchange Server 2003 73 Figure 4.4 Microsoft Active Directory Connector Setup j Tip You don’t have to install the management tools on the ADC server. You might prefer to install the management tools on your administrative terminal. The ADC Tools Applet Those of you who’ve used the Exchange 2000 Microsoft Management Console (MMC) Active Directory Connector Services snap-in will find a new addition with Exchange Server 2003: the ADC Tools applet.

Both functions are included in this tool.6 shows. Brought to you by Quest Software and Windows & . In Step 2. identifies domain accounts associated with more than one mailbox.74 The Expert’s Guide for Exchange 2003 Figure 4. ADC Tools connects to the target server and begins collecting information about the Exchange 5. and automatically create CAs based on the discovered information (through the Connection Agreement Wizard).5 organization.5 environment. Deploying ADC Tools In ADC Tools Step 1. which Figure 4. find resource mailboxes (through the Resource Mailbox Wizard). you set the server and the path for the log files. you no longer need to download NTDSNoMatch or run queries against the Exchange organization.5 ADC Tools applet ADC Tools will help you collect information about the Exchange 5.NET Magazine eBooks . This information is used in Step 3 as the Resource Mailbox Wizard. n Note With the inclusion of ADC Tools in the Active Directory Connector Services snap-in.

6 Resource Mailbox Wizard displaying two Exchange mailbox associations Deploying the Resource Mailbox Wizard Discovering these domain accounts is important: ADC Tools will find each Windows NT 4. the domain account is the primary object and the Exchange settings are attributes of that object. Daniel Malloy is the primary NT 4. Remember that the field for NT Account allowed a single reference only. j Tip Each AD domain account can have only one primary associated mailbox. In other words.0 account was an attribute you could change at will. In Exchange 5.7 shows. Although the resource mailbox will then be primarily associated with another domain account. each AD domain account is limited to one primary mailbox account. Using ADC Tools.5 mailboxes. Although you can add another account to the ACL of a mailbox later. one AD domain account must equal one Exchange mailbox.0 account on two Exchange 5. Brought to you by Quest Software and Windows & . With AD.0 account that’s associated with more than one mailbox and let you match the appropriate account with one of the mailboxes.6 shows. With Exchange 5. I selected the Malloy. In the example that Figure 4. AD makes that impossible because of the nature of the objects and the number of values possible within the attributes.5 multiple mailboxes could be associated with a single domain account. Daniel (dmalloy) account as the primary account for his mailbox and identified the other mailbox as a resource mailbox.NET Magazine eBooks .5. as Figure 4. Chapter 4 Installing Exchange Server 2003 75 Figure 4. the primary object was a mailbox and the associated NT 4. Daniel Malloy will retain permissions to it.

5 migration projects: the Connection Agreements Wizard. you’ll use the most longed-for tool for Exchange 5.7 Exchange settings in an AD account Each Exchange 5. after you or your staff members make the changes in the DS. those details involve CA configurations. this association process could take a few minutes or many hours.5 mailbox must be associated with a unique domain account before you deploy the ADC – or the wrong domain account might be associated with the mailbox. With Exchange migration projects. As with most technical processes. Depending on the number of resources in your organization. which contain the settings that the ADC service uses to keep the directories synchronized.76 The Expert’s Guide for Exchange 2003 Figure 4. you should run the Mailbox Resource Wizard as early in the migration process as possible – and export and view the results so you can delegate the changes. an automated tool for creating CAs. The risk of an incorrect association is quite real. The ADC uses three types of CAs: Brought to you by Quest Software and Windows & . You can run the wizard again at a later time. Therefore. especially with resource mailboxes such as mailboxes in conference rooms – which is why ADC Tools includes the Resource Mailbox Wizard.NET Magazine eBooks . Deploying the Connection Agreements Wizard In ADC Tools Step 4. the devil is in the details.

0 directories. When you associate an NT 4. and DLs for that site. your Exchange 5. the installation program asks for connection settings. you can’t create this CA manually. Without the correct recipient CAs in place. Moreover. The first time you install Exchange Server 2003 into your Exchange 5.0 account with an Exchange 5. Although ADC Tools will launch regardless.5.0 domain is upgraded or the accounts migrated to a clean AD using SIDHistory. if you attempted to install Exchange Server 2003 and don’t see the configuration CA. Because the SID is unique and is an attribute for both systems. Chapter 4 Installing Exchange Server 2003 77 • configuration CAs • recipient CAs • public folder CAs Configuration CA. you lack a single address book – even in a single- organization scenario. The “magic” behind its ability to do so lies in the fields the ADC uses during the search.0 account (sometimes incorrectly referred to as the SID) is the only field that’s truly matched between Exchange 5. By default.5 objects appear in AD and adds Exchange 2003 mailboxes to the Exchange 5.5 organization into the AD configuration container. this value is then the perfect field for the ADC to use to match objects between AD and the Exchange DS. then leverages the ADC to create the configuration CA and begin replicating the configuration settings of the Exchange 5. if you want to synchronize DLs and mailboxes on different schedules or into different containers. Therefore. you’ll need to manually create separate CAs for the different settings. you might notice how accurately it matches accounts to mailboxes. the SID value will probably remain intact. the SID is copied into the mailbox object as an attribute. You can move the configuration CA to other ADC servers and change the Windows connectivity settings. If you choose to upgrade an existing Exchange 5. contacts. n Note If you pay close attention to the ADC during the setup phases. It controls synchronizing mailbox objects to the AD. you won’t get past the authentication screen unless it can communicate with and authenticate to all sites in your organization. During this installation.5 Global Address List (GAL). but otherwise the configuration CA is read-only. The number of recipient CAs you need depends on the degree of granularity your synchronization requires.5 organization hasn’t been upgraded. • synchronization to and from each site will occur on the same schedule using the same settings. Assuming that an NT 4. The recipient CA is the primary emphasis for this section.5 and NT 4. a CA is created automatically. the associated NT 4. Brought to you by Quest Software and Windows & .5 organization.5 mailbox. The recipient CA lets Exchange 5. ADC Tools attempts to create a single recipient CA for each site that synchronizes all of the recipients.5 organization.5 organization. For example. In Exchange 5. you’ll be asked whether you want to create a new Exchange organization or upgrade an existing Exchange 5. This default behavior means that • you must make sure that each site has a network connection and proper credentials before ADC Tools can complete all its steps. Recipient CA.NET Magazine eBooks .

Brought to you by Quest Software and Windows & .5 public folders.5 public folders. You can have just one primary CA. You have three choices for each agreement: • Two-Way – The preferred and most common method of synchronization is a two-way agreement. ExDeploy now includes the Microsoft Exchange Public Folder Migration Tool (pfMigrate. It can handle deletions and find matches within the target systems without creating duplicates.5 organization name instead of a specific site to replicate every Exchange 5. Secondary CAs can only append or modify existing objects. it isn’t ideal for two-way synchronization because any AD changes made to objects in other Exchange 5.5 environment. To make replication changes easier during migration.5 object to AD with a single CA. a hub-and-spoke configuration is typical to centralize the updates. replication can occur between Exchange 5. Its mapping rules are flexible. For example. In addition to choosing the source and target servers and containers. Public folder CA. you can choose to synchronize with AD only those attributes that exist in the DS. Although this might seem to be an effective way to minimize the complexity of your ADC configuration. you can select the Exchange 5.5 sites won’t replicate.78 The Expert’s Guide for Exchange 2003 j Tip An interesting aspect of the recipient CA is that you can select root objects for the source. The public folder CA’s purpose is to create public folder proxies in AD for Exchange 5. you’ll need to select a direction for your agreements.5 GAL. The ADC is a powerful tool. • Exchange to Windows – If you’re planning a quick move or want to avoid making changes to the existing Exchange 5. but administrators in complex environments often choose to deploy multiple ADC servers.wsf) to help automate the process of adding Exchange Server 2003 to the replication list of the Exchange 5. After you’ve added the public folder proxy addresses. The number of CAs you can run on an ADC server has no published limit. you might notice that the first CA you create becomes the primary CA for that Exchange organization.NET Magazine eBooks . n Note When you use the MMC Active Directory Connector Management snap-in. and only that CA that can create accounts in the target environment. you might choose not to replicate any changes to AD. on the From Exchange tab from within the CA details.5 and Exchange Server 2003 servers – including the system folders. • Windows to Exchange – If you want to establish a single Exchange 5. As with any directory replication. and you can configure the CAs it contains to be quite specific and granular.

5 environment. you can install the first Exchange 2003 server into your organization.400 connectors. then upgrade the servers to Exchange Server 2003. Coexistence and Migration.5 site or sites. To move mailboxes from the Exchange 5. but you’ll need to manually modify the Outlook profiles or run the Profile Migration script to reset the Outlook profiles to the new target server. you need to add one Exchange 2003 server to the existing Exchange 5. Moving mailboxes has been greatly improved with the Exchange Server 2003 MMC Active Directory Users and Computers snap-in. Chapter 4 Installing Exchange Server 2003 79 j Tip Without a direct upgrade path from Exchange 5. During the Exchange Server 2003 setup.5 servers to Exchange Server 2003 machines in other sites (admin groups). then select the target Exchange 2003 server and the appropriate storage group. One solution is to first upgrade the hub-site servers to Exchange 2000. Therefore.NET Magazine eBooks . which Figure 4. select Move Mailbox. you’re prompted to select whether you’ll create a new organization or upgrade an existing Exchange 5.8 shows. You’re then asked to choose how to handle errors that occur during the process. You can choose to have the mailbox move aborted in the event of any error. You’ll see this prompt only once – and failure to make the right choice results in considerable cleanup work. Phase 3 Phase 3 of the Coexistence with Exchange 5. The Mailbox Move Wizard can now migrate multiple accounts at once. With the release of Exchange Server 2003 SP1. Brought to you by Quest Software and Windows & . Select one or more user objects in the snap-in and right-click to bring up the Exchange Tasks.5 to Exchange Server 2003.5 scenario involves installing Exchange 2003 Server. From this selection.5 servers to the Exchange Server 2003 servers. The first is to execute Setupprep to examine and verify that the directories are synchronized. you can now move mailboxes from Exchange 5. which retains their mail settings. and this phase contains five steps. Such environments often have a hub site that handles the complex mail routing topology by using a mix of site connectors. X. You can choose to migrate the accounts after hours or watch the migration live and monitor the progress with the new onscreen reporting information. or you can choose to log a cer- tain number of errors after which the attempt is considered failed. do your home- work before you make this choice. and specific SMTP settings.5 organization. After you evaluate the results. you have to decide what to do about a complex Exchange 5.

822450.” at http://support. then verify and use the ADC to replicate the changes. you stop the Exchange 5.80 The Expert’s Guide for Exchange 2003 Figure 4.5. you need to make sure the system folders are replicated.aspx?scid=kb.8 Exchange Task Wizard progress report n Note The Mailbox Move Wizard now moves multiple mailboxes (up to four) at once and displays the status and progress of each move live.5 server from the site. “How to Remove the Last Exchange Server 5. you can begin to think about retiring the old servers. Microsoft maintains current information about this procedure in the Knowl- edge Base Article 822450. Immediately below you see what the Help screen displays when you use exdeploy. ExDeploy Command-Line Options As I mentioned previously.5 services and use the Exchange 5.5 administrative tools from the Exchange Server 2003 console to remove the Exchange 5. Finally. After you’ve moved the information you need from Exchange 5.exe /? to find the syntax for the tools: Brought to you by Quest Software and Windows & . ExDeploy is the brains behind the deployment tools. EN-US. In Magazine eBooks .com/default.5 Computer from an Exchange Server 2003 Administrative Group.

. ExDeploy tools that help you gain information include the following: • DSConfigSum runs Exchange 5. • ConfigDSInteg runs Exchange Server 2003 Configuration Object Check. • GCVerCheck runs Global Catalog Server Version Check. As you know from this chapter.5 Directory User Count. • ADCConfigCheck runs ADC Configuration Replication Check. • PolCheck runs Policy Check.. • OrgNameCheck runs Organization and Site Names Check. • ADCObjectCheck runs ADC Object Replication Check. • ADUserScan runs Active Directory User Replication Scan. • DSObjectSum runs Exchange 5..5 Directory Configuration Summary. • NTDSNoMatch runs NTDSNoMatch. • VerCheck runs Server Version Check. • PubFoldCheck runs Public Folder DS/IS Check.5 server>[:port] /gc:<Global Catalog server>|? Use <Global Catalog server> as target server /p:<Log File Path> Redirects progress output to <Log File Path> /h. • RecipientDSInteg runs Exchange Server 2003 Recipient Object Check. setting goals for the migration..5 Directory Object Summary. and determining the administrative structure of the target system often involves non-technical decisions that require input from non-technical teams. However. • OrgCheck runs Organization Readiness Check.NET Magazine eBooks . Determining AD design. /? Display this Help text /c (Comprehensive) Runs all tools /skip:<Tool1> [/skip:<Tool2>] . you can take off your gloves and get to work. Brought to you by Quest Software and Windows & . ] Skips specified tools or tool groups /t:<Tool1> [/t:<Tool2>] . • PrivFoldCheck runs Private Folder DS/IS Check. ] Runs all specified tools or tool groups /site Runs PrivFoldCheck on all servers in the same site Also. Planning for your Exchange Server 2003 deployment can seem more daunting than the actual installation. after the planning stages are complete. • OrgReport runs Existing Org Report. • UserCount runs Exchange 5. Chapter 4 Installing Exchange Server 2003 81 /s:<Exchange 5. Exchange Server 2003 deployment tools will help you walk through the installation process from start to finish. • ADCUserCheck runs ADC User Replication Check.

the Interorg ADC agreement.NET Magazine eBooks .82 The Expert’s Guide for Exchange 2003 Next: Multiple Directories In the next chapter. I’ll cover the need for multiple directories and the methods you can use to keep them in sync. as well as migrations from other directories (e. and.. Notes). Brought to you by Quest Software and Windows & . I’ll discuss the Microsoft Identify Integration Server in depth. finally.g.