Applies to: Exchange Server 2013
Topic Last Modified: 2013-01-18
Use the Set-MoveRequest cmdlet to change move request options after the move request has been created. You can use the Set-MoveRequest cmdlet to recover from failed move requests.
Syntax
Set-MoveRequest -Identity <MoveRequestIdParameter>
[-AcceptLargeDataLoss <SwitchParameter>] [-BadItemLimit
<Unlimited>] [-BatchName <String>]
[-CompletedRequestAgeLimit <Unlimited>] [-Confirm
[<SwitchParameter>]] [-DomainController <Fqdn>]
[-IgnoreRuleLimitErrors <$true | $false>] [-LargeItemLimit
<Unlimited>] [-PreventCompletion <$true | $false>]
[-Priority <Lowest | Lower | Low | Normal | High | Higher |
Highest | Emergency>] [-Protect <$true | $false>]
[-RemoteCredential <PSCredential>] [-RemoteGlobalCatalog
<Fqdn>] [-RemoteHostName <Fqdn>] [-SkipMoving
<SkippableMoveComponent[]>] [-SuspendWhenReadyToComplete
<$true | $false>] [-WhatIf [<SwitchParameter>]]
|
Examples
EXAMPLE 1
This example changes the move request for Ayla to accept up to five corrupt mailbox items.
Copy Code | |
---|---|
Set-MoveRequest -Identity Ayla@humongousinsurance.com -BadItemLimit 5 |
Detailed Description
You can pipeline the Set-MoveRequest cmdlet from the Get-MoveRequestStatistics, Get-MoveRequest, or Get-Mailbox cmdlets.
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Mailbox moves" entry in the Recipients Permissions topic.
Parameters
Parameter | Required | Type | Description | ||
---|---|---|---|---|---|
Identity |
Required |
Microsoft.Exchange.Management.RecipientTasks.MoveRequestIdParameter |
The Identity parameter specifies the identity of the mailbox or mail user. You can use the following values:
|
||
AcceptLargeDataLoss |
Optional |
System.Management.Automation.SwitchParameter |
The AcceptLargeDataLoss parameter specifies that a large amount of data loss is acceptable if the BadItemLimit is set to 51 or higher. Items are considered corrupted if the item can't be read from the source database or can't be written to the target database. Corrupted items won't be available in the destination mailbox or .pst file. |
||
BadItemLimit |
Optional |
Microsoft.Exchange.Data.Unlimited |
The BadItemLimit parameter specifies the number of bad
items to skip if the request encounters corruption in the mailbox.
Use
|
||
BatchName |
Optional |
System.String |
The BatchName parameter specifies a different name for a batch. |
||
CompletedRequestAgeLimit |
Optional |
Microsoft.Exchange.Data.Unlimited |
The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. |
||
Confirm |
Optional |
System.Management.Automation.SwitchParameter |
The Confirm switch can be used to suppress the
confirmation prompt that appears by default when this cmdlet is
run. To suppress the confirmation prompt, use the syntax
|
||
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory. |
||
IgnoreRuleLimitErrors |
Optional |
System.Boolean |
The IgnoreRuleLimitErrors parameter specifies that the command won't move the user's rules to the target server running Microsoft Exchange. |
||
LargeItemLimit |
Optional |
Microsoft.Exchange.Data.Unlimited |
The LargeItemLimit parameter specifies the number of large items to skip if the request encounters such items in the mailbox. Use 0 to not skip any large items. If any number above 50 is specified, the AcceptLargeDataLoss parameter must also be specified. The default value is 0. We recommend that you use the default value of 0 and increase the LargeItemLimit parameter value only when large items are encountered. |
||
PreventCompletion |
Optional |
System.Boolean |
The PreventCompletion parameter specifies that this
cmdlet initializes, but isn't completed. This parameter accepts
|
||
Priority |
Optional |
Microsoft.Exchange.MailboxReplicationService.RequestPriority |
The Priority parameter specifies the order in which this request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. |
||
Protect |
Optional |
System.Boolean |
This parameter is reserved for internal Microsoft use. |
||
RemoteCredential |
Optional |
System.Management.Automation.PSCredential |
The RemoteCredential parameter specifies an administrator who has permission to perform the mailbox move, for example, Administrator@ humongousinsurance.com. This parameter requires the creation and passing of a credential object. This credential object is created by using the Get-Credential cmdlet. For more information, see Get-Credential. |
||
RemoteGlobalCatalog |
Optional |
Microsoft.Exchange.Data.Fqdn |
The RemoteGlobalCatalog parameter specifies the FQDN of the global catalog server for the remote forest. |
||
RemoteHostName |
Optional |
Microsoft.Exchange.Data.Fqdn |
The RemoteHostName parameter specifies the FQDN of the cross-forest organization from which you're moving the mailbox. |
||
SkipMoving |
Optional |
Microsoft.Exchange.Management.RecipientTasks.SkippableMoveComponent[] |
The SkipMoving parameter allows certain stages of a mailbox move to be skipped for debugging purposes. Do not use this parameter unless directed to do so by a support professional or specific documentation. |
||
SuspendWhenReadyToComplete |
Optional |
System.Boolean |
The SuspendWhenReadyToComplete parameter specifies whether to suspend the move request before it reaches the status of CompletionInProgress. The move request then has a status of AutoSuspended. You can manually complete the move by using the Resume-MoveRequest command. |
||
WhatIf |
Optional |
System.Management.Automation.SwitchParameter |
The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch. |
Input Types
To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.
Return Types
To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.