Microsoft Press 70 284 training kit exchange server 2003 phần 4 pps

5-42 Chapter 5 Migrating from Microsoft Exchange Server and Other Mail Systems limiting migrated content, and for selecting the target location for the migrated accounts. ■ You should perform a test migration using the Migration Wizard prior to perform- ing a live migration. Case Scenario Exercise Litware, Inc. is a fast-growing software development company. It has acquired several smaller companies over the last year but has been struggling to merge the various mes- saging platforms of the different companies. Litware, Inc. is running Exchange Server 5.5, but management wants to upgrade to Exchange Server 2003. The Litware, Inc. organization consists of two Exchange Server 5.5 servers, one at each of their two loca- tions. The litwareinc.com domain is running Windows 2000 Server SP2 on all its servers. Exchange Server 5.5 is not connected to Active Directory. The primary Exchange Server system, Server05, has approximately 500 mailboxes and is located at the corporate office. The second server, Server06, has approximately 250 mailboxes and is located at their branch office. Server07 has recently been deployed with Windows 2000 Server SP4 and has been designated as the server to consolidate all mailboxes to. There is a pressing need to migrate one of the acquired companies, Contoso, Ltd., to the litwareinc.com domain as quickly as possible. Contoso, Ltd. runs Exchange 2000 Server SP3 on Windows 2000 Server SP4 computers in the contoso.com domain. Man- agement wants to eliminate the contoso.com domain altogether. ■ Requirement 1 The first requirement is to upgrade Litware, Inc. to Exchange Server 2003. You need to connect Exchange Server 5.5 to Active Directory, install Exchange Server 2003 into the existing Exchange Server 5.5 organization, and move all of the mailboxes to the new Exchange Server 2003 server. Management also wants all Windows 2000 Server systems upgraded to Windows Server 2003. ■ Requirement 2 The second requirement is to migrate Contoso to the litwareinc.com domain and Exchange Server organization. You must migrate both the user accounts and the mailboxes and then eliminate the contoso.com domain. Requirement 1 The first requirement involves upgrading the Litware, Inc. Exchange Server 5.5 organi- zation to Exchange Server 2003. 1. Installing the Exchange Server 2003 version of the ADC requires a minimum of Windows 2000 Server SP3, but all servers except the new Server07 are running SP2. Before installing the ADC, should you update the service pack level to SP4 or Chapter 5 Migrating from Microsoft Exchange Server and Other Mail Systems 5-43 simply upgrade to Windows Server 2003, since management wants to upgrade anyway? What influences your decision? 2. Describe the process for upgrading Exchange Server 5.5 to Exchange Server 2003 at the corporate office. Requirement 2 The second requirement is to migrate Contoso’s user accounts and mailboxes to the lit- wareinc.com domain and the Litware, Inc. Exchange Server organization and then eliminate the contoso.com domain. 1. What tool do you use to retain the SIDs while migrating Contoso’s user accounts to Litware, Inc., and what do you need to do to migrate the existing user passwords? 2. After successfully migrating Contoso’s existing user accounts to the litwareinc.com domain, what do you need to do prior to running Dcpromo, removing the contoso.com domain, and joining Contoso’s servers to the litwareinc.com domain? Troubleshooting Lab In this lab, you will attempt to use the Migration Wizard to migrate mailboxes from Server01 to Server02 in the Litware, Inc. organization. The procedure will fail because the wizard can only migrate between organizations, not within an organization. You will then use the Active Directory Users And Computers console to move the mailboxes. Before proceeding with this lab, you must have the system requirements as outlined at the beginning of this chapter. 5-44 Chapter 5 Migrating from Microsoft Exchange Server and Other Mail Systems Exercise 1: Attempt to Migrate Mailboxes with the Migration Wizard 1. On Server02, start the Migration Wizard. From the Start menu, point to All Programs, Microsoft Exchange, and Deployment, and then click Migration Wizard. 2. Click Next to bypass the Welcome page. 3. Select to Migrate From Microsoft Exchange and click Next. 4. Click Next on the following page, which advises you about migrating from another Exchange Server organization. 5. On the Migration Destination page, note that the information for Server02 is auto- matically filled in. Click Next. 6. On the Source Exchange Server page, type Server01:1389 and enter the Administrator account information. Click Next. 7. Note the error, “Unable to perform the migration. Please enter a source Exchange server outside of the target Exchange organization.” Quit the Migration Wizard. Exercise 2: Migrate Mailboxes with Active Directory Users And Computers 1. Open the Active Directory Users And Computers console on Server01. 2. Click the Users container to see a list of user accounts. 3. Highlight to select Amy Alberts, Chris Meyer, and Eli Bowen. Right-click Eli Bowen and click Exchange Tasks. 4. Select Move Mailbox from the list of Exchange Tasks, and click Next. 5. Move the mailboxes to Server02. Chapter Summary ■ Exchange Server 5.5 cannot be upgraded in-place; you must first upgrade to Exchange 2000 Server and then to Exchange Server 2003, or install Exchange Server 2003 on a different server and move the Exchange Server 5.5 resources to the new server. ■ Exchange 2000 Server can be upgraded directly to Exchange Server 2003 if the Windows 2000 Server level is SP3 or later. ■ If you upgrade Exchange 2000 Server to Exchange Server 2003, you must run ForestPrep and DomainPrep again with Exchange Server 2003. The same permis- sions requirements apply as when installing Exchange Server 2003 in a new organization. Chapter 5 Migrating from Microsoft Exchange Server and Other Mail Systems 5-45 ■ The Migration Wizard can only migrate an Exchange Server organization to another organization. It cannot be used to migrate accounts and mailboxes within an organization. ■ X.400 connectors can connect other Exchange Server organizations, other Exchange Server routing groups in the same organization, or non–Exchange Server X.400-compliant messaging systems. ■ The Migration Wizard can migrate previous versions of Exchange Server in other organizations to an Exchange Server 2003 organization, and it can also migrate popular third-party messaging systems, such as Lotus Notes and Novell GroupWise. ■ Exchange Server 2003 can be configured to synchronize directories with Lotus Notes and Novell GroupWise with connectors that can be installed from the Exchange Server 2003 installation CD. Exam Highlights Before taking the exam, review the key points and terms that are presented in this chapter. Return to the lessons for additional practice. Key Points ■ Site Connectors are used to connect routing groups when there is reliable band- width. X.400 connectors are used to connect routing groups when bandwidth is unreliable. ■ The Migration Wizard cannot migrate existing account information. You must use the Active Directory Migration Tool to retain existing settings. ■ To configure an X.400 connector, you must first create an X.400 transport stack. ■ Synchronizing with Lotus Notes and Novell GroupWise is a two-part process. Configuring the Connector for Lotus Notes or the Connector for Novell GroupWise synchronizes account and message data, but you must also configure a Calendar Connector in order to synchronize calendar data. Key Terms security identifier (SID) A SID is an attribute of a user account that uniquely iden- tifies it in a Windows domain. A SID is unique and is used only once, so if you delete and recreate an account with all the same data, the operating system sees them as two different accounts. Because SIDs are unique, if you migrate a user account using the Migration Wizard and a new account is created in the target domain, you will have to recreate all the security settings manually. 5-46 Chapter 5 Migrating from Microsoft Exchange Server and Other Mail Systems X.400 A standards-based messaging system that is most commonly used outside of the United States. Exchange Server 2003 is X.400-compliant and can communicate with any X.400-compliant messaging system. access control list (ACL) ACLs define the security settings that are attached to an object in Active Directory. Every object has an ACL, which is used to determine what objects have permissions to the object and what level of permissions they have. The Migration Wizard is not able to migrate ACL settings. source domain and target domain When you use either the Active Directory Migration Tool or the Migration Wizard, you define a source domain that contains the accounts and mailboxes you are migrating and a target domain that is the des- tination for the migration. Questions and Answers 5-47 Questions and Answers Page 5-24 Lesson 1 Review 1. You are the Exchange Server administrator for Litware, Inc. You have installed an Exchange Server 2003 server in the existing Exchange Server 5.5 organization, and you are trying to migrate the mailboxes over to the new server. You run the Migration Wizard on the Exchange Server 2003 server and select to migrate from Exchange Server 5.5, but you find that you are unable to do so. Why would this happen? The Migration Wizard is able to move mailboxes only between servers in different organizations. It cannot be used to move mailboxes between servers within the same organization. To accomplish this, you would use the Active Directory Users And Computers console and select Move Mailbox from the Exchange Tasks menu of the user accounts with the mailboxes you want moved. 2. You need to migrate a server from Exchange Server 5.5 to Exchange Server 2003, but you know that you cannot perform an in-place upgrade in this situation. Since Exchange Server 5.5 with SP4 is running on Windows 2000 Server with SP4, you decide to do an interim in-place upgrade from Exchange Server 5.5 to Exchange 2000 Server, and then you will upgrade Exchange 2000 Server directly to Exchange Server 2003. You install Exchange 2000 Server successfully and verify that users are able to log on and access mail, and then you immediately insert the Exchange Server 2003 installation CD and run Setup. However, Setup fails. What is the most likely cause? Upgrading from Exchange 2000 Server requires SP3. In this instance, you successfully upgraded Exchange Server 5.5, so there are no permissions problems, and the version of Windows supports Exchange Server 2003. Once you install the latest service pack for Exchange 2000 Server, you will be able to perform the in-place upgrade. 3. You install a new Exchange Server 2003 server into your existing Exchange Server 5.5 organization. You successfully migrate all the mailboxes to the new server, and users are able to access their mail from the new server without any problems. One afternoon, you shut down the Exchange Server 5.5 server, planning to use the machine later for something else. The next day, you receive many complaints that e-mail is working within the company, but mail is not being sent to or received from the Internet. What is the problem? In addition to moving mailboxes, you must also transfer any connectors that are in use. In this instance, the Internet Mail Service is still on the Exchange Server 5.5 server. First, you need to start the server back up, and then you need to configure an SMTP virtual server on the new Exchange Server 2003 server and schedule the time to switch the MX record in DNS to the new server when the downtime will have the least impact. 5-48 Chapter 5 Migrating from Microsoft Exchange Server and Other Mail Systems Page 5-37 Lesson 2 Review 1. You are trying to configure an X.400 connection between your Exchange Server 2003 organization and a remote X.400 messaging system running on a UNIX plat- form. After working with the administrator of the remote system to configure the connector, you test and find that your side of the connection receives messages fine, but on the remote end, the messages come out garbled. What do you need to do to fix the problem on your end? By default, Allow Exchange Contents is enabled, which sends messages in Exchange’s internal format. This works when the destination system is an Exchange Server system, but when it is a non-Exchange Server system, you have to clear the option in order for messages to be sent in the standard X.400 format. 2. You have set up directory synchronization between your Exchange Server 2003 organization and the Lotus Notes organization of a company that has recently merged with your company. E-mail is working fine and you are able to verify syn- chronization between Active Directory and Notes, but Outlook users are complaining that when they view the schedules of Notes users, the information is generally out of date. What can you do to correct the problem? The Schedule tab of the Calendar Connector’s properties must be configured to synchronize calendar data. The default setting is Never, which does not synchronize calendar data, and depending on what schedule you create, your data may become out of date before it synchro- nizes again. 3. You are the administrator of two Exchange Server 2003 routing groups that have been connected by a T-1 line. Lately, the circuit has been very inconsistent, some- times very slow, and sometimes dropping connection altogether. Message traffic is suffering as a result. What can you do to improve the reliability of the message transfer over the unreliable connection? When bandwidth is reliable, you typically use Site Connectors to connect Exchange Server 2003 routing groups. However, X.400 connectors can be used to connect Exchange Server routing groups, as well, and they are useful when bandwidth is unreliable. This is because the X.400 connector uses messaging-based data transfer rather than remote procedure call (RPC), which requires a reliable connection. By implementing an X.400 connector, you can improve message transfer reliability in this situation. Page 5-41 Lesson 3 Review 1. Which of the following messaging systems is not supported by the Migration Wizard? a. Lotus cc:Mail b. SendMail c. Microsoft Mail d. Internet Mail The correct answer is b. Questions and Answers 5-49 2. You are trying to migrate a Lotus Notes server in the domain adatum.com to an Exchange Server 2003 organization in the fabrikam.com domain. You are per- forming a test migration using the Migration Wizard, and the wizard asks you to specify the name of your Lotus Notes server. After you do, you receive an error that the server cannot be contacted. You verify that the Notes server is running, and users in the adatum.com domain are not complaining about being unable to access e-mail. How would you troubleshoot this problem? One of the most common problems when migrating across domains is having DNS set up incor- rectly. You should first verify that you have connectivity and name resolution between the two domains by attempting to ping the Notes server by DNS name from the Exchange Server 2003 server. If you are able to resolve the DNS problem, you should be able to connect to the Notes server with the Migration Wizard. 3. You are involved in a migration of mail systems between two companies. Litware, Inc., which runs Exchange Server 2003, has acquired Contoso, which runs Novell GroupWise on the NetWare operating system. What type of information will you be able to migrate to Exchange Server 2003, and how will user accounts be handled? The Migration Wizard will be able to effectively migrate all user mailbox data, but it will not be able to migrate NetWare user accounts intact. The Migration Wizard will create new user accounts for the NetWare users in Active Directory and then associate the migrated mailboxes with the new user accounts. Page 5-42 Case Scenario Exercise: Requirement 1 1. Installing the Exchange Server 2003 version of the ADC requires a minimum of Windows 2000 Server SP3, but all servers except the new Server07 are running SP2. Before installing the ADC, should you update the service pack level to SP4 or simply upgrade to Windows Server 2003, since management wants to upgrade anyway? What influences your decision? You will need to install SP3 or SP4 for Windows 2000 Server rather than upgrade to Windows Server 2003. Only Exchange Server 2003 is supported on Windows Server 2003, so upgrad- ing your Windows 2000 Server systems to Windows Server 2003 will cause your Exchange Server 5.5 organization to fail. 2. Describe the process for upgrading Exchange Server 5.5 to Exchange Server 2003 at the corporate office. First you need to connect the existing Exchange Server 5.5 organization to Active Directory and have a two-way Recipient Connection Agreement configured. But before doing so, you need to install SP3 or SP4 for Windows 2000 Server on at least the server hosting the Active Directory Connector Service. Once you have the two directories replicating, you can install Exchange Server 2003 onto Server07 and have it join the existing Exchange Server 5.5 orga- nization. After the Exchange Server 2003 server is installed and the Site Replication Service is configured, you can begin moving mailboxes from the Exchange Server 5.5 server to the Exchange Server 2003 server by using the Active Directory Users And Computers console. 5-50 Chapter 5 Migrating from Microsoft Exchange Server and Other Mail Systems You should schedule the mailbox moves because users will need to update their Outlook pro- files to point to the new server. After the mailboxes are moved, you would move any connectors from the Exchange Server 5.5 server, as well as any public folder stores and other resources being hosted on the Exchange Server 5.5 server. Once all of the resources are reallocated to Server07, shut down Server05. Then repeat the process to move resources from Server06 to Server07. Page 5-43 Case Scenario Exercise: Requirement 2 1. What tool do you use to retain the SIDs while migrating Contoso’s user accounts to Litware, Inc., and what do you need to do to migrate the existing user passwords? The Active Directory Migration Tool is designed to migrate user account data while retaining SID history and ACL settings. The Migration Wizard is not a full-featured account migration tool; it is unable to migrate existing account information. It can only create new accounts in the target domain or match mailboxes to existing accounts. In order to migrate passwords, you have to install the password migration DLL file using Pwdmig.exe from the Windows Server 2003 instal- lation CD and then create a .pes file to be used during the password migration. 2. After successfully migrating Contoso’s existing user accounts to the litwareinc.com domain, what do you need to do prior to running Dcpromo, removing the contoso.com domain, and joining Contoso’s servers to the litwareinc.com domain? Migrating the user accounts with the Active Directory Migration Tool does not migrate the Exchange mailboxes. The mailboxes are still associated with Contoso user accounts, so you need to run the Migration Wizard to migrate the mailboxes to the Litware, Inc. Exchange Server organization and have the mailboxes associated with the migrated user accounts in the litwareinc.com domain. After running the Migration Wizard, users will need to log on to the litwareinc.com domain with their user accounts and edit their mail profiles to point to the new mail server. 6-1 6 Installing Microsoft Exchange Server 2003 Clusters and Front-End and Back-End Servers Exam Objectives in this Chapter: ■ Prepare the environment for the Microsoft Exchange Server 2003 deployment ■ Install, configure, and troubleshoot Exchange Server 2003 in a clustered environment ■ Manage, monitor, and troubleshoot Exchange Server clusters ■ Manage and troubleshoot front-end and back-end servers ■ Monitor, manage, and troubleshoot infrastructure performance Why This Chapter Matters Messaging systems are often a “mission critical” network service within an orga- nization. Therefore, minimizing the downtime of the e-mail servers is one of the top priorities of a network administrator. For companies that require the ultimate in performance and reliability, Exchange Server 2003 supports being installed on network load balanced and clustered servers, which use redundant hardware resources to ensure that there is not a single point of failure and that the applica- tions that run on them have as close to 100 percent uptime as possible. Another performance-maximizing benefit of Exchange Server 2003 is that it supports front- end and back-end architecture, which was introduced in Chapter 3, “Configuring a Microsoft Exchange Server 2003 Infrastructure.” This chapter focuses on Exchange Server organizations designed to support thou- sands of users with a server architecture that is more advanced than has been previously discussed. It is important to be just as comfortable working with Exchange Server 2003 in an enterprise clustered environment supporting thousands of users as in a small single-server environment supporting a few dozen users. [...]... be able to ■ Create an Exchange Server 2003 virtual server ■ Manage Exchange Server 2003 clustered services Estimated lesson time: 60 minutes Creating an Exchange Server 2003 Virtual Server The final step in configuring Exchange Server 2003 to run on a Windows Server 2003 cluster is to create the Exchange Server 2003 virtual servers The number of Exchange Server 2003 virtual servers you need to create... two-node active/ passive Exchange Server 2003 cluster, you will be setting up one Exchange Server 2003 virtual server If you are setting up a two-node active/active Exchange Server 2003 cluster, you will set up two Exchange Server 2003 virtual servers, since both server nodes will be active You must repeat this step for each active node that will run an Exchange Server 2003 virtual server In the practice... version of Exchange Server to Exchange Server 2003 has all of the requirements that exist when upgrading single servers, as discussed in Chapter 5, “Migrating from Microsoft Exchange Server and Other Mail Systems.” Practice: Installing Exchange Server 2003 in a Clustered Environment In this practice, you will configure a single-node Windows Server 2003 cluster and then install Exchange Server 2003 onto... and software: ■ Two Microsoft Windows Server 2003 servers installed into the tailspintoys.com Active Directory domain Server0 1 should be a domain controller, and Server0 2 should be a member server Server01 must have two network cards ■ Exchange Server 2003, Enterprise Edition Lesson 1 Installing Exchange Server 2003 in a Clustered Environment 6-3 Lesson 1: Installing Exchange Server 2003 in a Clustered... Windows Server 2003 Cluster Installing Exchange Server 2003 on a cluster is similar to other installation processes with which you are now familiar However, you must prepare the Windows Server 2003 cluster servers prior to installing Exchange Server 2003 Also, after installing Exchange Server 2003 on the nodes of the cluster, there are additional steps which are necessary to create the Exchange Server 2003. .. Service Instance ■ Exchange MS Search Instance 6-20 Chapter 6 Installing Microsoft Exchange Server 2003 Clusters and Front-End and Back-End Servers ■ SMTP Virtual Server Instance ■ Exchange HTTP Virtual Service Instance F06es06 Figure 6-6 An Exchange Server 2003 virtual server configuration The Message Transfer Agent Instance resource is created only in the first Exchange Server 2003 virtual server added... ■ Exchange Server 2003 supports two-node active/active clusters and up to eightnode active/passive clusters with at least one passive node Lesson 2 Managing an Exchange Server 2003 Cluster 6-19 Lesson 2: Managing an Exchange Server 2003 Cluster Once you have installed Exchange Server 2003 on a Windows Server 2003 cluster, there are additional administrative tasks to perform in order to create the Exchange. .. console to configure the Exchange Server 2003 virtual servers In the practice at the end of this lesson, you will set up a cluster, install Exchange Server 2003 on the first node, and use Cluster Administrator to configure the Exchange Server 2003 virtual server To upgrade to Exchange Server 2003 on an existing cluster, you use a method known as a rolling upgrade In this method, one server node is manually... resource appears as a resource of the Exchange Server 2003 virtual server Exercise 5: Create an Exchange Server 2003 System Attendant Resource 1 In Cluster Administrator, right-click the Exchange Server 2003 virtual server, and then click Bring Online You will see each of the resources go from Offline to Online Pending to Online 2 Right-click the Exchange Server 2003 virtual server, point to New, and then...6-2 Chapter 6 Installing Microsoft Exchange Server 2003 Clusters and Front-End and Back-End Servers Lessons in this Chapter: ■ Lesson 1: Installing Exchange Server 2003 in a Clustered Environment 6-3 ■ Lesson 2: Managing an Exchange Server 2003 Cluster 6-19 ■ Lesson 3: Installing Exchange Server 2003 in a Front-End and Back-End Configuration . to Exchange Server 2003, or install Exchange Server 2003 on a different server and move the Exchange Server 5.5 resources to the new server. ■ Exchange 2000 Server can be upgraded directly to Exchange. to Windows Server 2003. Only Exchange Server 2003 is supported on Windows Server 2003, so upgrad- ing your Windows 2000 Server systems to Windows Server 2003 will cause your Exchange Server 5.5. 2000 Server with SP4, you decide to do an interim in-place upgrade from Exchange Server 5.5 to Exchange 2000 Server, and then you will upgrade Exchange 2000 Server directly to Exchange Server 2003.