MCITP Microsoft Exchange Server 2007 Messaging Design and Deployment Study Guide phần 5 ppt

Migrating from Exchange 2000 Server or Exchange Server 2003 315 8. Next, choose the type of installation. This exercise covers the Typical installation, which installs the Hub Transport, Client Access, and Mailbox server roles. (If you plan to deploy cluster Mailbox server, Unified Messaging server, or Edge Transport server roles, or per- haps one or two server roles, you should choose Custom installation instead of Typical.) On the Installation Type page, click Typical Exchange Server Installation as shown below. If you want to change the installation path, click on Browse, locate the appropriate path, and then click OK. Click Next. 9. To establish mailflow between the Exchange 2000/2003 and the Exchange 2007 routing groups, you need to create a routing-group connector. On the Mail Flow Settings page, click Browse to locate an Exchange 2003 Bridgehead server. (In my lab environment, this is TOREX2K server.) Select an Exchange 2003 Bridgehead server to which you will create the initial routing group connector, as shown below, and then click OK. Click Next to continue. EXERCISE 7.10 (continued) 81461c07.fm Page 315 Thursday, December 13, 2007 9:13 AM 316 Chapter 7  Planning a Migration to Exchange Server 2007 10. After you click Next on the Mail Flow Settings page, the Exchange 2007 Setup wizard will go through a set of prerequisite checks to ensure that you have all the necessary soft- ware, Windows components, and hotfixes installed. Click Install to begin the installation, as shown below. 11. Setup will then prepare your organization, copy Exchange files from the source (DVD ROM) to the destination path on your hard drive, and install the server roles automatically. Click Finish, as shown below. EXERCISE 7.10 (continued) 81461c07.fm Page 316 Thursday, December 13, 2007 9:13 AM Migrating from Exchange 2000 Server or Exchange Server 2003 317 To perform an unattended installation, you can use something similar to the following syntax: Setup/mode:install /roles:ClientAccess,HubTransport,Mailbox /LegacyRoutingServer:Exch2000.yourcompany.com Finalizing Your Exchange 2007 Installation Now that you’ve installed Exchange 2007 let’s move on to the post-installation tasks. Some of these post-installation tasks will validate the installation by verifying that it completed with- out any serious warnings or errors, while others will ensure that your server is operational and configured properly for your environment. If you didn’t get any warnings or errors during the installation, there is a good chance that everything is in perfect shape, and then you just have to go through finalizing your deployment, which is explained in the next section. The post-installation tasks include the following: Exchange 2007 Services. Verify that you have Exchange 2007 services installed and started automatically. Review the Exchange Setup log files. This involves reviewing the ExchangeSetup.log and ExchangeSetup.msilog log files located under the %systemdrive%\ExchangeSetupLogs folder to ensure that there are no errors related to Exchange 2007 installation. The ExchangeSetup .log contains all the information about the status of prerequisite and system Readiness Checks. It also contains information about every task that is performed during the Exchange Server setup and is the most important log available for troubleshooting pre- and post-installation warning and errors. Verify Exchange folder structure. Verify the Exchange folder structure created during installation. The default folder is located at C:\Program Files\Microsoft\Exchange Server. Table 7.5 shows the default folder structure. TABLE 7.5 Table 7.5. The Default Exchange Folder Structure Folder Contents Bin Executables that are used for management of the Exchange server ClientAccess Client Access Server configuration files Logging Log files Mailbox Schema files, .dll files, database files, and database log files for the Mailbox databases and public-folder databases 81461c07.fm Page 317 Thursday, December 13, 2007 9:13 AM 318 Chapter 7  Planning a Migration to Exchange Server 2007 Review event logs. This involves examining the Windows application logs and the system logs for any warnings, information, and errors related to the Exchange Server 2007 setup and services. Verify server roles are installed. Ensure that you can open Exchange Management Con- sole and can see your Exchange Server 2007 servers, including the one you just installed. Obtain the latest Exchange critical updates. Exchange Server 2007 is constantly evolving. To avoid threats, problems, and security issues, it is essential to patch your Exchange Server 2007 with the latest service packs and security patches. We recommend installing the latest patches and service pack after testing them in a lab. Run Microsoft Exchange Best Practice Analyzer. It is a good idea to run the Exchange Best Practices Analyzer tool to configure Exchange Server 2007 according to Microsoft Exchange best practices. Finalizing Deployment of the Exchange Server 2007 Server Now that you’ve installed Exchange 2007, let’s finalize the deployment. The first time you launch the Exchange Management Console, the Exchange node will be selected, and you’ll find two new tabs under this node: Finalize Deployment and End-to-End Scenario. You must examine the recommended deployment tasks listed in both tabs and perform the ones that are relevant to your environment. The tasks listed in Finalize Deployment tab are important because they apply to default features that need additional configuration. Figure 7.2 shows you the Finalize Deployment tab. Scripts Exchange Management Shell scripts Setup XML configuration files and data TransportRoles\agents Binary files for agents TransportRoles\data Data files used by the mail queue and ADAM TransportRoles\Logs Log files for message tracking and routing TransportRoles\Pickup: Message awaiting delivery to submission queues TransportRoles\Shared Configuration files for agents UnifiedMessaging Configuration and setup files for Unified Messaging and speech recognition TABLE 7.5 Table 7.5. The Default Exchange Folder Structure (continued) Folder Contents 81461c07.fm Page 318 Thursday, December 13, 2007 9:13 AM Migrating from Exchange 2000 Server or Exchange Server 2003 319 The End-to-End Scenario tab provides a list of optional tasks that are relevant for your envi- ronment. Although they are optional, it’s a good idea to review and complete them. Figure 7.3 shows you the End-to-End Scenario tab. FIGURE 7.2 The Finalize Deployment tab FIGURE 7.3 End-to-End Scenario tab 81461c07.fm Page 319 Thursday, December 13, 2007 9:13 AM 320 Chapter 7  Planning a Migration to Exchange Server 2007 Licensing Exchange Server 2007 Exchange 2007 has a built-in grace period of 120 days, which means that you have to license your product within that grace period. The first time you launch the Exchange Management Console, you will see the warning message shown in Figure 7.4. FIGURE 7.4 Licensing grace period warning If you have a Standard or Enterprise product key ready, it is a good time to license your Exchange Server 2007. Exercise 7.11 outlines the steps to license Exchange Server 2007. EXERCISE 7.11 Licensing Exchange Server 2007 To license the Exchange Server 2007, follow these steps: 1. Log on to Exchange Server 2007. 2. Open the Exchange Management Console, and then select the Server Configuration work center node. 3. Select the server that requires the product key. 4. In the action pane, click the Enter Product Key link. 5. In the Enter Product Key wizard, enter your Exchange 2007 product key and click Enter. 6. Click Finish. 7. To verify that your Exchange Server 2007 has been properly licensed, open the Properties page for your server by right-clicking on your server and then clicking on Properties. 8. You should see a product ID number under the General tab. If your Exchange Server 2007 is not licensed, it will show Unlicensed instead of a product ID number. If you have licensed your Exchange Server 2007 with an Enterprise key, you cannot down- grade or convert it to a Standard edition. To license from Exchange Management Shell, use the Set-ExchangeServer command: Set-ExchangeServer –Identity Servername –ProductKey. 81461c07.fm Page 320 Thursday, December 13, 2007 9:13 AM Migrating from Exchange 2000 Server or Exchange Server 2003 321 Coexistence: Life After Installation You’ve successfully installed and licensed Exchange 2007. Now, with Exchange Server 2007 running in an Exchange 2003 organization, you are in coexistence mode. What’s next? The following sections describe the tasks you will need to perform to complete your migration, including moving mailboxes, configuring user profiles, and replicating public folders. In the Mean Time: Administration Tips for Exchange 2003 and Exchange 2007 Coexistence In coexistence mode, there are several considerations for performing day-to-day administra- tion tasks. Some features are not available in Exchange 2007, which means you will need to use the Active Directory Users and Computers (ADUC) MMC snap-in and Exchange System Manager. On the other hand, there are certain features available only in Exchange 2007, which will require you to use Exchange 2007 tools. Although the transition can be confusing, you’ll get the hang of it over time. Some of the administrative tasks that you need to consider in coexistence mode are as follows:  Do not use the Active Directory Users and Computers (ADUC) MMC snap-in to manage your Exchange 2007 recipient objects.  Exchange Server 2007 server will inherit most of the Exchange 2003 global settings auto- matically because these settings (for example, Internet message formats, SMTP connectors, recipient policies, and Exchange delegation permissions) are stored in Active Directory. All users’ mailboxes on the Exchange Server 2007 servers will inherit these settings.  All organization-level settings should be managed using Exchange Management Con- sole (EMC) or Exchange Management Shell (EMS) instead of using Exchange 2003 System Manager.  Perform all recipient management tasks by using EMC or EMS instead of the Active Directory Users and Computers (ADUC) MMC snap-in.  To create, manage, remove, and move Exchange 2007 mailbox-enabled users, use EMC or EMS. You also can use Exchange 2007 management tools to manage an Exchange 2003 mail- box as long as the mailbox has been created with the Exchange System Manager tool.  To create, manage, remove, and move Exchange 2003 mailbox-enabled users, use the ADUC MMC snap-in and Exchange System Manager.  To manage any Exchange 2003 and Exchange 2007 mail-enabled objects in a coexistence environment, you can use the ADUC MMC snap-in, EMC, or EMS. There is no restric- tion on managing mail-enabled objects, except for dynamic distribution groups. The dynamic distribution group uses the new Exchange 2007 OPATH format for its recipient filter and cannot be managed by using the older Exchange tools. Use EMC or EMS to maintain dynamic distribution groups.  To manage Exchange 2003 Recipient Update Service (RUS), you have to use Exchange System Manager. This service is no longer part of the Exchange 2007 product, and there- fore cannot be managed with EMC or EMS.  To move mailboxes to Exchange Server 2007, use EMC or EMS instead of the Exchange System Manager. 81461c07.fm Page 321 Thursday, December 13, 2007 9:13 AM 322 Chapter 7  Planning a Migration to Exchange Server 2007 Moving Mailboxes: Using the Exchange 2007 Move Mailbox Wizard and the Move-Mailbox cmdlet The preferred method to migrate from Exchange 2000 or 2003 environments is the Move Mailbox wizard or the Move-Mailbox cmdlet. The Move Mailbox wizard has been around for a while, and it has been improved over the years. In Exchange 2000, the Move Mailbox wizard did not have a scheduling option and had a lot of performance issues. Exchange 2003 and later versions have excellent performance and a scheduling option that allows you to execute mailbox moves after office hours. The Move Mailbox wizard supports multithreading operations to move multiple mailboxes simultaneously and has the ability to deal with corrupt mailbox entries. If it encounters any problems, the wizard automatically attempts to move the mailbox item by item instead of all at once. Active Directory Users and Computers cannot be used to move mailboxes from Exchange 2003 to Exchange 2007. The Move Mailbox wizard and the Move-Mailbox cmdlet have many different uses, including upgrades, database moves, realignments, physical location changes, mailbox merges, load balanc- ing, troubleshooting, forest merging, and much more. The Move Mailbox method is ideal for orga- nizations that require new hardware and operating systems or that want to reconstruct their Exchange organization. Using Move Mailbox is also an effective way to minimize the risk associated with a migra- tion from an Exchange Server 2003 server to an Exchange Server 2007 server. The greatest advantage of this approach is in having the ability to build a new system with all the software, settings, third-party utilities, applications, patches, and tools before you even move mailboxes to your Exchange server. However, there are few disadvantages and limitations associated with Move Mailbox wizard and the Move-Mailbox cmdlet. You cannot use the Move Mailbox wizard to move mailboxes across forests. In a multi-forest scenario, you must use the Move-Mailbox cmdlet instead of the wizard. Also, the Move Mailbox wizard is an intra-organizational migration tool that cannot be used as an inter-organizational migration tool. This means that you are limited to using the wizard within the same Exchange organization. You can move mailboxes between Exchange 2000, Exchange 2003, and Exchange 2007 servers by using the Move Mailbox wizard and the Move-Mailbox cmdlet. The Move-Mailbox cmdlet can communicate only with Windows 2003 domain controllers. In a cross-forest mailbox move, if you have only a Windows 2000 domain controller, then you cannot use the Move-Mailbox cmdlet to move mailboxes to an Exchange 2007 forest. Here’s how the Move Mailbox process works. The Move Mailbox wizard has a built-in multi- thread functionality. This feature dramatically reduces the time required to move multiple mail- boxes without stressing your Exchange server. The wizard can make multiple MAPI connections 81461c07.fm Page 322 Thursday, December 13, 2007 9:13 AM Migrating from Exchange 2000 Server or Exchange Server 2003 323 to the source server, read contents, and write those contents from the source mailbox to the target mailbox on the target server. As soon as it finishes the move operation, it updates the user’s attributes in the Active Directory with the location of the new housed server rather than the old mailbox server. This tool provides you with more granular control. You can either move an individual user or multiple users simultaneously. Check out the following features: Schedule. In Exchange 2003 and later, you can schedule mailbox moves. Of course, you don’t ever want to perform mailbox moves during normal working hours because of the interruptions and lost productivity. Scheduling allows you to define not only a start time but also an end time for the mailbox move. If you are moving many mailboxes and you want to define an end time because of a scheduled reboot or other jobs, you can simply define an end time and it will terminate the outstanding move operations. You can then reschedule to move the remaining mailboxes that were not moved in time. Error control. The Move Mailbox wizard has built-in functionality to handle corrupted items during the mailbox move. If the wizard encounters corrupted items in a user’s mail- box, it can do one of two things: it can be set to create a failure report without moving the mailbox, or it can skip the corrupted items, move the other items, and create a failure report at the end. The beauty of this option is that you can define the number of corrupted items to skip and set the value. Now that you are familiar with the Move Mailbox wizard and the Move-Mailbox cmdlet, it’s time to move mailboxes from the existing Exchange servers to the Exchange 2007 envi- ronment. In fact, the migration is as simple as selecting the mailbox or mailboxes, and then selecting the new destination server and database. Exercise 7.12 outlines the steps for moving mailboxes with the Move Mailbox wizard. EXERCISE 7.12 Moving Mailboxes Using the Move Mailbox Wizard To move mailboxes to the Exchange Server 2007, do the following: 1. Log on to your Exchange Server 2007. 2. Open the Exchange Management Console, and then select the Recipient Configuration. 3. Click on Mailbox container. You will see a list of mailboxes. In the details column, you will see mailboxes flagged as either Legacy Mailbox or as Mailbox User. Mailboxes flagged as Legacy are still on Exchange Server 2003 and need to be migrated to Exchange Server 2007. Mailboxes already on Exchange Server 2007 are shown as Mailbox User. 4. To select the specific mailboxes that you want to move, you can click on a mailbox, hold down the Shift key and select a group of mailboxes, or hold down the Control key and click on the specific mailboxes that you want to migrate. 5. Click on Move Mailbox action in the right column. 81461c07.fm Page 323 Thursday, December 13, 2007 9:13 AM 324 Chapter 7  Planning a Migration to Exchange Server 2007 6. Choose the server, storage group, and the Mailbox database to which you want to move the mailbox(es), as show below. Click Next to continue. 7. At the Move Options screen, shown below, you can adjust the settings to specify how you want to manage corrupted messages in a mailbox during the move. You can choose Skip the Mailbox or Skip the Corrupted Messages if corrupted messages are found dur- ing the move process. Usually, we choose to skip the corrupt messages if we want to complete the migration. However, in some scenarios you may want to further trouble- shoot the problem and, therefore, you may want to choose Skip the Mailbox. If you decide to skip the corrupted messages, you can also define the number of corrupted items to skip and set the value. Click Next to continue. EXERCISE 7.12 (continued) 81461c07.fm Page 324 Thursday, December 13, 2007 9:13 AM [...]... E:\support\Exdeploy and then press Enter 5 Type pfmigrate.wsf /S :Exchange2 00 3server /T :Exchange2 00 7server /R /F:c:\pflog.log to create a report of public-folder replication between the Exchange 2003 and Exchange 2007 servers 6 Type pfmigrate.wsf /S :Exchange2 00 3server /T :Exchange2 00 7server /SF /A /F:c:\ pflog.log to replicate system folders from Exchange 2003 to Exchange 2007 7 Type pfmigrate.wsf /S :Exchange2 00 3server. .. the Exchange Server 2007 installation DVD-ROM and would like to perform an in-place upgrade of your existing Exchange servers Which of the following can be upgraded to Exchange 2007 by using an in-place upgrade methodology? A Exchange 5. 5 B Exchange 2000 C Exchange 2003 D Exchange 2000 and Exchange 2003 E None of the above 2 You are planning to re-harvest your Exchange Server 2003 for Exchange 2007 deployment. .. installation of a new Exchange 2007 Mailbox server It is time to activate Exchange Server 2007 Which of the following PowerShell commands must you use to perform the activation for a server named SERVERA? A Set-LicenseServer SERVERA -ProductKey B Set-ExchangeLicenseServer SERVERA -ProductKey C Set-ExchangeServer SERVERA -ProductKey D Set-ExchangeServer -Identity SERVERA -ProductKey 81461c07.fm Page 350 Thursday,... Notes to Microsoft s unified communications and collaboration platforms that are part of Microsoft Exchange Server 2007, Microsoft Office 2007 system, and Microsoft Office SharePoint Server 2007 technologies When planning a migration from Notes, you will need to consider several factors, including the Domino Directory, messaging, and applications, as shown in Figure 7 .5 FIGURE 7 .5 Notes and Microsoft. .. process must have the Exchange Organization Administrator role on Exchange Server 2007 servers and the Exchange Full Administrator role on the Exchange Server 2003 server 81461c07.fm Page 343 Thursday, December 13, 2007 9:13 AM Decommissioning the Old Infrastructure 343 Once your organization no longer needs Exchange Server 2003 servers, it’s time to upgrade to the Exchange 2007 organization by removing/decommissioning... a non -Exchange environment to Exchange 2007 involves installing Exchange 2007 and then migrating mailboxes, user data, and other information to Exchange 2007 Migration from SendMail, Qmail, and GroupWise to Exchange 2007 is outside the scope of the exam and the scope of this book This section provides an overview of the process of analyzing, planning, and migrating from Lotus Notes to Exchange 2007. .. Server 2003 server updates the client that the mailbox is now located on the Exchange Server 2007 server 3 The client updates the Exchange Server 2007 entry in the client’s registry Once this update occurs, it does not need to be repeated 4 The client sends requests to the Exchange Server 2007 5 Subsequent logons from that client go directly to the Exchange Server 2007 as the client has new server information... strategies and migration concerns in mixed and coexistence modes We spent a great amount of time preparing our Active Directory forest for an Exchange Server 2007 deployment, and then we took a step-by-step walk through installing Exchange 2007 prerequisites, which eventually led us to Exchange 2007 installation We then discussed how to move mailboxes from Exchange 2003 to Exchange Server 2007 by using... /S :Exchange2 00 3server /T :Exchange2 00 7server /A /F:c:\pflog.log to replicate public folders from Exchange 2003 to Exchange 2007 8 After all public folders have replicated, type pfmigrate.wsf /S :Exchange2 00 3server / T :Exchange2 00 7server /D to remove the old replicas from the Exchange Server 2003 server 9 Open the pflog.log file to ensure that replication has occurred successfully and that a copy of each... classes, objects, and attributes or modifying the existing ones B Create the Exchange organization in AD C Create the Microsoft Exchange system objects container in the root domain partition to store Exchange configuration data and information D Add local and remote domains E Modify SMTP parameters for all Exchange Server 2003 servers to communicate with Exchange Server 2007 servers F Create an Exchange routing . license your Exchange Server 2007. Exercise 7.11 outlines the steps to license Exchange Server 2007. EXERCISE 7.11 Licensing Exchange Server 2007 To license the Exchange Server 2007, follow. to run the Exchange Best Practices Analyzer tool to configure Exchange Server 2007 according to Microsoft Exchange best practices. Finalizing Deployment of the Exchange Server 2007 Server Now. messaging, and applications, as shown in Figure 7 .5. FIGURE 7 .5 Notes and Microsoft coexistence and migration Directory Identity Messaging Applications Active Directory Microsoft Exchange 2007 SharePoint