Applies to: Exchange Server 2013, Exchange Online
Topic Last Modified: 2013-01-11
Use the Remove-MigrationBatch cmdlet to delete a migration batch that either isn't running or has been completed. If necessary, you can run the Get-MigrationBatch cmdlet to determine the status of a migration batch before you remove it.
For information about the parameter sets in the Syntax section below, see Syntax.
Syntax
Remove-MigrationBatch [-Identity
<MigrationBatchIdParameter>] [-Confirm
[<SwitchParameter>]] [-DomainController <Fqdn>] [-Force
<SwitchParameter>] [-Organization
<OrganizationIdParameter>] [-WhatIf
[<SwitchParameter>]]
|
Examples
EXAMPLE 1
This example removes the migration batch Cutover1.
 Copy Code |
|
|---|---|
Remove-MigrationBatch -Identity Cutover1 |
|
EXAMPLE 2
This example removes the corrupted migration batch LocalMove1.
| Copy Code |
|
|---|---|
Remove-MigrationBatch -Identity LocalMove1 -Force |
|
Detailed Description
The Remove-MigrationBatch cmdlet removes a migration batch. All subscriptions are deleted, and any object related to the migration batch is also deleted.
If you use the Force parameter with this cmdlet,
the individual user requests and subscriptions that were part of
the removed migration batch aren't removed. You have to remove the
individual migration user requests with the
Remove-MigrationUser <Identity> -Force
command.
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 Move and Migration Permissions" section in the Recipients Permissions topic.
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
Confirm |
Optional |
System.Management.Automation.SwitchParameter |
The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch. |
|
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. |
|
Force |
Optional |
System.Management.Automation.SwitchParameter |
The Force switch specifies whether to remove a corrupted migration batch. Corrupted migration batches have a status of Corrupted. If you try to remove a corrupted migration batch without using this switch, you receive an error saying the migrated batch can't be found. If you use this parameter to remove a corrupted migration batch,
the individual user requests (also called job items) and
subscriptions that were part of the removed migration batch aren't
removed. You have to remove the individual migration user requests
with the |
|
Identity |
Optional |
Microsoft.Exchange.Management.Migration.MigrationBatchIdParameter |
The Identity parameter identifies the migration batch that you want to remove. The value for this parameter is the name that was specified when the migration batch was created. |
|
Organization |
Optional |
Microsoft.Exchange.Configuration.Tasks.OrganizationIdParameter |
The Organization parameter is reserved for internal Microsoft use. |
|
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.