Microsoft Exchange 2000 Manuel d'utilisateur

Microsoft® Exchange 2000 Server to Microsoft Exchange Server 2003 migration and consolidation — white paper Executive summary...

Figure 5 b. Run the MMC. Enter mmc at the command prompt, and add the Active Directory Schema Plug-in to the console by right-clicking Active Dire

Figure 7 d. Right-click Active Directory Schema, and choose permissions. Verify that allow full control is set to the account that is performing t

Figure 8 e. Disconnect the current Schema Master and any other replicated domain controllers. f. Run adprep /forestprep on the Schema Master. Ad

b. Modify the system "HeapDecommitFreeBlockThreshold" Registry Key. Refer to Microsoft Knowledge Base Article 315407 for information on thi

Figure 10 c. In the Enter the object name to select text box, highlight the name of the new Exchange 2003 server, and click Check Names. See Figur

Symantec software had the option to continue file system protection while disabling real-time scanning of email. 7. Temporarily turn on circular logg

Figure 12 2. In Exchange Task Wizard, select Move Mailbox (see Figure 13), and then click Next. 16

Figure 13 3. Select the new server in the drop-down lists, and then click Next. 17

Figure 14 4. Select Skip corrupted items and create a failure report, and then click Next. 18

Figure 15 5. Select a time for the mailbox move, as shown in Figure 16. A period of least activity would be best, such as off hours. Keep in mind

Executive summary This paper describes a best practice process for consolidating servers and storage in a multiserver Microsoft® Exchange 2000 Server

Figure 16 6. Click Finish. Decommissioning old servers Decommissioning the old servers requires three steps. Be sure you follow these steps in se

Figure 17 b. Click Change, and select the new server as the Domain Naming Operations Master. Figure 18 2. Make the new server the Schema Mast

Figure 19 b. Right-click Active Directory Schema, and select Operations Master. Click Change, and select the name of the new server. Figure 20

Figure 21 b. Select the RID tab, and change the RID Master to new the server. Figure 22 c. Select the PDC tab, as shown in Figure 23. Change t

Figure 23 d. Select Infrastructure tab. Change the Infrastructure Master to the new server, and select OK. 24

Figure 24 4. Configure the new server to become a Global Catalog. a. Open the Active Directory Sites and Services console. b. Expand Sites and S

Figure 25 d. In the NTDS Properties window, select the Global Catalog checkbox so that the server can become a Global Catalog server. 26

Figure 26 This completes the key roles and services transfer. 5. Move existing connectors to the new Exchange server using Exchange System Manager

Mailbox move durations Mailbox migrations were conducted in groups containing one-third of the total number of users to be migrated. Because the total

Table 5 shows the average time encountered to move one mailbox. Again, a simulated user load of two-thirds of the total users was applied during the m

Overview HP conducted testing to show an Exchange 2000 Server to Exchange Server 2003 migration using the ”move mailbox” method. The testing also demo

Table 7. LoadSim scores test 2 Number of users/ LoadSim clients EVA3000 during move Number of users/ LoadSim clients EVA3000 after migration Migrati

Appendix A—Performance data The following table summarizes the test results for the final configurations. Table 8. Summary MSA1000 test EVA3000 test

Appendix B—Reference configuration The reference configuration is appropriate for the test scenarios, which did not exceed 3,000 users. Hardware purc

Table 11. SAN fabric components—Use when EVA3000 is selected Quantity Part number Description 2 AA980A HP StorageWorks SAN Switch 2/8V power pack 16

Table 15. HP Services Quantity Part number Description 1 HA109A3 HP CP 3Y Support Plus 14 HA109A3 699 For HP Internal Entitlement Purposes 1 HA

For more information The following documents and locations provide information regarding successful deployment of Microsoft Exchange Server on HP pro

The MSA1000 configuration included: • Array A—100 GB RAID 1+0, 36-GB 10,000-rpm disks, 20 disks, Selective Storage Presentation (SSP) enabled • Arra

Table 1. Number of mailboxes on each server at various stages of the migration process Server Before migration After first migration After second mig

The EVA3000 (2C2D) configuration included: • Twenty-eight 36-GB, 15,000-rpm disks • Two disk groups – Database disk group, 14 disks – Transaction

Table 2. Number of mailboxes on each server at various stages of the migration process Server Before migration After first migration After second mig

was manually replicated using Exchange System Manger. Additional information about using the pfmigrate utility can be found in the Microsoft Knowledge

Figure 3. Using the DiskPar utility to implement the fix for heavy write load disk performance 5. Add the new server to the domain. Because this i