Applies to: Exchange Server 2013, Exchange Online
Topic Last Modified: 2013-01-11
Use the Start-MigrationBatch cmdlet to start a move request or migration batch that was created with the New-MigrationBatch cmdlet.
For information about the parameter sets in the Syntax section below, see Syntax.
Syntax
Start-MigrationBatch [-Identity
<MigrationBatchIdParameter>] [-Confirm
[<SwitchParameter>]] [-DomainController <Fqdn>]
[-ForceNewMigration <SwitchParameter>] [-Organization
<OrganizationIdParameter>] [-Validate
<SwitchParameter>] [-WhatIf [<SwitchParameter>]]
|
Examples
EXAMPLE 1
This example starts the migration batch SEM1.
 Copy Code |
|
|---|---|
Start-MigrationBatch -Identity SEM1 |
|
Detailed Description
The Start-MigrationBatch cmdlet starts a pending migration batch that was created, but not started, with the New-MigrationBatch cmdlet.
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. In the cloud-based service, this parameter is reserved for internal Microsoft use. |
|
ForceNewMigration |
Optional |
System.Management.Automation.SwitchParameter |
The ForceNewMigration switch causes the migration process to create a subscription for any mailbox in the migration batch that was already migrated in a previous migration batch. Any existing subscriptions for mailboxes in the migration batch are deleted. |
|
Identity |
Optional |
Microsoft.Exchange.Management.Migration.MigrationBatchIdParameter |
The Identity parameter identifies the migration batch that you want to start. Use the migration batch Name parameter as the value for this parameter. Use the Get-MigrationBatch cmdlet to identify the name of the migration batch. |
|
Organization |
Optional |
Microsoft.Exchange.Configuration.Tasks.OrganizationIdParameter |
The Organization parameter is reserved for internal Microsoft use. |
|
Validate |
Optional |
System.Management.Automation.SwitchParameter |
The Validate parameter specifies whether to start the migration batch in the validation stage of the migration process. If you include this parameter, the migration performs a validation check of the mailboxes in the batch. |
|
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.