Designing and Deploying Exchange Server 2007 in Software

Paint QR Code ISO/IEC18004 in Software Designing and Deploying Exchange Server 2007

4 Choose Move Mailbox from the Actions pane 5 Click the Browse button and select the Exchange 2007 server Storage Group \ Mailbox Database from the server list 6 Select Skip the corrupted messages Set the maximum number of messages to skip to 3 (or whatever your tolerance level is) and click Next

7 Set a move schedule that does not interfere with the users ability to work Move the mailboxes immediately is the default option Click Next

NOTE It is also possible to set the time limit on the Move Mailbox process Use this setting to avoid

interrupting the backup schedule or normal business work hours 8 Verify that the list of mailboxes to be moved is accurate and click Move 9 Once all the mailboxes have been moved, click Finish

5:

It is also possible to perform your entire transition utilizing the Exchange Management Shell (EMS) Although the EMS might be less conducive to moving one or two mailboxes, it is where you will find the most options for going about moving them When it comes to very large environments, the Exchange System Manager (ESM) is the proper tool to automate moving large batches of mailboxes The following are examples of how to use the Move-Mailbox command to transition mailboxes from Exchange 2000/2003 to Exchange Server 2007 (see Figure 5-5)

Moving a Single Mailbox The following cmdlets will move a legacy mailbox to Exchange 2007:

[PS] C:\>Move-Mailbox identity "UserNo2" TargetDatabase "Migration-E2K7\First Storage Group\Mailbox Database"

[PS] C:\>Get-Mailbox Database "Migration-E2K3\First Storage Group\Mailbox Store (Migration-E2K3) | Move-Mailbox TargetDatabase "Migration-E2K7\First Storage Group\Mailbox Database"

[PS] C:\>Get-Mailbox Server "Migration-E2K3" | Move-Mailbox TargetDatabase "Migration-E2K7\First Storage Group\Mailbox Database"

[PS] C:\>Get-Mailbox RecipientTypeDetails "LegacyMailbox" | Move-Mailbox TargetDatabase "Migration-E2K7\First Storage Group\Mailbox Database"

FIGURE 5-5

Part II:

It is possible to increase the number of threads that Move-Mailbox can use (see Figure 5-6) The default is 4 The EMC can only use four, but the EMS can be increased up to 30 if you add the following parameter to your Move-Mailbox command:

[PS] C:\>Get-Mailbox -RecipientsTypeDetails "LegacyMailbox" | Move-Mailbox -MaxThreads 8 - TargetDatabase "Mailbox Database"

There is, of course, a reason why it is limited to four out of the box Increasing MaxThreads too high on a server that cannot handle the additional I/O could cause the server to hang Adding the WhatIf parameter to the end of any of the preceding cmdlets will let you execute the command without actually doing anything to the mailboxes This could be helpful if you want to make sure the syntax in the command is correct before you try to move thousands of users

After the mailboxes are moved to Exchange Server 2007, they will no longer appear as legacy mailboxes in the Recipient Type Details It is possible to find out more details about how the Move-Mailbox process went (see Figure 5-7) The Application Log in Event Viewer on the target server will display three events for each moved mailbox Event 1006 is generated when the move has started Event 1007 is generated when the mailbox has moved Event 9354 is generated when the mailbox is deleted from the legacy server

FIGURE 5-6

5:

FIGURE 5-7

Migration Logs are also created in the %Program Files%\Microsoft\Exchange Server\ Logging\MigrationLogs directory on the target Exchange 2007 server These logs are helpful because they provide more detail about the process of moving mailboxes than the Event Logs do

The amount of time it takes you to move all the public folders and mailboxes, combined with the need to maintain legacy Exchange servers for incompatibility reasons, dictates how long your coexistence period will last You can actually calculate how long your mailboxes will take to move On average it will take an hour to move 2 4GB (gigabytes) of mail Your Disk Storage subsystem on the source and target servers, along with the quality and speed of the network that connects them, have the greatest impact on whether you get 2GB or 4GB per hour Other factors include the maintenance and backup schedules, business hours, and unforeseen events It is not as easy to calculate how long you must support an incompatible feature or application Suffice it to say that you will have to keep an Exchange 2000/2003 server in your organization until you no longer need the incompatible feature Coexistence during a transition is pretty smooth and very transparent to your users There are some administrative items that you will need to be familiar with that only apply to coexistence

Part II: