Sunday, January 2, 2011

Exchange 2010 Move Request, Import, and Export Considerations

Given the number of new features in Exchange 2010, there are some new considerations to take into account. The first of these I will explore, as I can see it being something that my crew would find useful, is around move request, imports and exports.

Mailbox move requests and export/import requests can back up, as Exchange does not purge them automatically by default. For mailbox move requests, you can set an expiration time to whatever you like by using the following commands:

To set a 30 day automatic expiry for successful move requests:

Set-OrganizationConfig -DefaultExpirySuccessfulMR 30.0:00:00

To define that a move request does not automatically expire:

New-MoveRequest -DoesNotExpire $True

If you aren’t currently setting these to expire, you may want to consider setting this value (especially if you are performing migrations, or restructuring.

Unfortunately, I don’t believe you can manually set up expiration for Export/Import requests, however (New-Mailbox(EX/IM)portRequest is introduced in E2010 SP1). To purge these, you’d be looking at something like:

Get-MailboxImportRequest -Status Completed | Remove-MailboxImportRequest

Also, some nifty functionality was introduced around move requests as well (for those that perform mailbox moves often). You can now kick off a move that auto-suspends right before completion, and then resume them later on when the moves actually need to finalize and switch over.

To create the move request for all users in the “Seattle” office:

Get-Mailbox -Filter {Office -eq 'Seattle'} | New-MoveRequest -SuspendWhenReadyToComplete -SuspendComment 'Move Queued by Joshua on 22-Dec-2010 10:00' -BatchName ‘East Lake Users’ –BadItemLimit 1 -TargetDatabase 'DB1'

To resume the autosuspended moves to finalize the move:

Get-MoveRequest -MoveStatus 'AutoSuspended' -BatchName ‘East Lake Users’ | Resume-MoveRequest

No comments: