Applies to: Exchange Server 2013, Exchange Online
Topic Last Modified: 2013-01-08
Use the New-MigrationEndpoint cmdlet to configure settings for cutover or staged Exchange migrations, IMAP migrations, and remote moves.
For information about the parameter sets in the Syntax section below, see Syntax.
Syntax
New-MigrationEndpoint -ExchangeRemoteMove
<SwitchParameter> -RemoteServer <Fqdn> [-Credentials
<PSCredential>] <COMMON PARAMETERS>
|
New-MigrationEndpoint -Autodiscover
<SwitchParameter> -Credentials <PSCredential>
-EmailAddress <SmtpAddress> -ExchangeRemoteMove
<SwitchParameter> <COMMON PARAMETERS>
|
New-MigrationEndpoint -Credentials <PSCredential>
-ExchangeOutlookAnywhere <SwitchParameter> [-Authentication
<Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba |
LiveIdBasic | WSSecurity | Certificate | NegoEx | OAuth | Adfs |
Kerberos | Negotiate | LiveIdNegotiate | Misconfigured>]
[-EmailAddress <SmtpAddress>] [-ExchangeServer
<String>] [-MailboxPermission <Admin | FullAccess>]
[-NspiServer <String>] [-RpcProxyServer <Fqdn>]
[-SourceMailboxLegacyDN <String>] [-TestMailbox
<MailboxIdParameter>] <COMMON PARAMETERS>
|
New-MigrationEndpoint -Autodiscover
<SwitchParameter> -Credentials <PSCredential>
-EmailAddress <SmtpAddress> -ExchangeOutlookAnywhere
<SwitchParameter> [-MailboxPermission <Admin |
FullAccess>] [-SourceMailboxLegacyDN <String>]
[-TestMailbox <MailboxIdParameter>] <COMMON
PARAMETERS>
|
New-MigrationEndpoint -IMAP <SwitchParameter>
-RemoteServer <Fqdn> [-Authentication <Basic | Digest |
Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic |
WSSecurity | Certificate | NegoEx | OAuth | Adfs | Kerberos |
Negotiate | LiveIdNegotiate | Misconfigured>] [-Port
<Int32>] [-Security <None | Ssl | Tls>] <COMMON
PARAMETERS>
|
COMMON PARAMETERS: -Name <String> [-Confirm
[<SwitchParameter>]] [-DomainController <Fqdn>]
[-MaxConcurrentIncrementalSyncs <Unlimited>]
[-MaxConcurrentMigrations <Unlimited>] [-Organization
<OrganizationIdParameter>] [-SkipVerification
<SwitchParameter>] [-WhatIf [<SwitchParameter>]]
|
Examples
EXAMPLE 1
This example creates an endpoint for remote moves using Autodiscover to detect the settings.
Copy Code | |
---|---|
New-MigrationEndpoint -Name Endpoint1 -ExchangeRemoteMove -Autodiscover -EmailAddress tonysmith@contoso.com -Credentials (Get-Credential contoso\tonysmith) |
EXAMPLE 2
This example creates an endpoint for remote moves by specifying the settings manually.
Copy Code | |
---|---|
New-MigrationEndpoint -Name Endpoint2 -ExchangeRemoteMove -RemoteServer MRSServer.contoso.com -Credentials (Get-Credential Contoso.com\Administrator) |
Detailed Description
The New-MigrationEndpoint cmdlet configures settings for different types of migrations:
- Cross-forest move Move mailboxes
between two different on-premises Exchange forests. Cross-forest
moves require the use of a RemoteMove endpoint.
- Remote move In a hybrid deployment, a
remote move involves onboarding or offboarding
migrations. Remote moves require the use of a RemoteMove endpoint.
Onboarding moves mailboxes from an on-premises Exchange
organization to Exchange Online in Office 365, and uses a
RemoteMove endpoint as the source endpoint of the migration batch.
Offboarding moves mailboxes from Exchange Online in Office 365 to
an on-premises Exchange organization and uses a RemoteMove endpoint
as the target endpoint of the migration batch.
- Cutover Exchange migration Migrate all
mailboxes in an on-premises Exchange organization to Exchange
Online in Office 365. Cutover Exchange migration requires the use
of an Exchange endpoint.
- Staged Exchange migration Migrate a
subset of mailboxes from an on-premises Exchange organization to
Exchange Online in Office 365. Staged Exchange migration requires
the use of an Exchange endpoint.
- IMAP migration Migrate mailbox data
from an on-premises Exchange organization or other email system to
Exchange Online in Office 365. For an IMAP migration, you must
first create the cloud-based mailboxes before you migrate mailbox
data. IMAP migrations require the use of an IMAP endpoint.
- Local Move mailboxes between different
servers or databases within a single on-premises Exchange forest.
Local moves don't require the use of an endpoint.
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 |
---|---|---|---|
Autodiscover |
Required |
System.Management.Automation.SwitchParameter |
For an Exchange migration, the Autodiscover parameter specifies whether to get other connection settings for the on-premises server from the Autodiscover service. |
EmailAddress |
Required |
Microsoft.Exchange.Data.SmtpAddress |
The EmailAddress parameter specifies the Autodiscover email address. |
ExchangeOutlookAnywhere |
Required |
System.Management.Automation.SwitchParameter |
The ExchangeOutlookAnywhere parameter specifies the type of endpoint for staged and cutover migrations. |
ExchangeRemoteMove |
Required |
System.Management.Automation.SwitchParameter |
The ExchangeRemoteMove parameter specifies the type of endpoint for cross-forest and hybrid moves. |
IMAP |
Required |
System.Management.Automation.SwitchParameter |
The IMAP parameter specifies the type of endpoint for IMAP migrations. |
Name |
Required |
System.String |
The Name parameter specifies the name you give to the new migration endpoint. You can use the Name parameter when you run the New-MigrationBatch cmdlet. |
RemoteServer |
Required |
Microsoft.Exchange.Data.Fqdn |
The RemoteServer parameter specifies the remote server, which depends on the protocol type for moves:
|
Authentication |
Optional |
Microsoft.Exchange.Data.Directory.SystemConfiguration.AuthenticationMethod |
The Authentication parameter specifies the authentication
method used by the on-premises mail server. If you don't include
this parameter, |
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. |
Credentials |
Optional |
System.Management.Automation.PSCredential |
For all Exchange migration types, the Credentials parameter specifies the credentials to connect to the source or target endpoint. 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. |
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. |
ExchangeServer |
Optional |
System.String |
The ExchangeServer parameter specifies the on-premises source Exchange server for cutover and staged migrations. |
MailboxPermission |
Optional |
Microsoft.Exchange.Data.Storage.Management.MigrationMailboxPermission |
The MailboxPermission parameter specifies what permissions to use to access the source mailbox during Outlook Anywhere onboarding (staged Exchange migration and cutover Exchange migration). This parameter can’t be used for non-Outlook Anywhere migrations. The account specified must have one of the following permissions:
|
MaxConcurrentIncrementalSyncs |
Optional |
Microsoft.Exchange.Data.Unlimited |
The MaxConcurrentIncrementalSyncs parameter specifies the maximum number of incremental syncs allowed per endpoint. |
MaxConcurrentMigrations |
Optional |
Microsoft.Exchange.Data.Unlimited |
The MaxConcurrentMigrations parameter specifies the maximum number of mailboxes that are migrated during initial sync. This parameter is applicable for all migration types. |
NspiServer |
Optional |
System.String |
The NspiServer parameter specifies the remote Name Service Provider Interface (NSPI) server location for cutover and staged migrations. You must provide the FQDN of the server. |
Organization |
Optional |
Microsoft.Exchange.Configuration.Tasks.OrganizationIdParameter |
This parameter is reserved for internal Microsoft use. |
Port |
Optional |
System.Int32 |
For an IMAP migration, the Port parameter specifies the TCP port number used by the migration process to connect to the remote server. This parameter is required only when you want to migrate data from an on-premises IMAP server to cloud-based mailboxes. |
RpcProxyServer |
Optional |
Microsoft.Exchange.Data.Fqdn |
For a staged Exchange migration, the RpcProxyServer parameter specifies the FQDN of the RPC proxy server for the on-premises Exchange server. This parameter is required only when you don't use the Autodiscover parameter. |
Security |
Optional |
Microsoft.Exchange.Data.IMAPSecurityMechanism |
This parameter is reserved for internal Microsoft use. |
SkipVerification |
Optional |
System.Management.Automation.SwitchParameter |
The SkipVerification switch specifies whether to skip
verifying that the remote server is reachable when creating a
migration endpoint. The default value is |
SourceMailboxLegacyDN |
Optional |
System.String |
The SourceMailboxLegacyDN parameter specifies a mailbox on the target server. Use the LegacyExchangeDN for the on-premises test mailbox as the value for this parameter. The cmdlet tries to access this mailbox using the credentials for the administrator account on the target server. |
TestMailbox |
Optional |
Microsoft.Exchange.Configuration.Tasks.MailboxIdParameter |
The TestMailbox parameter specifies a mailbox on the target server. Use the primary SMTP address as the value for this parameter. The cmdlet tries to access this mailbox using the credentials for the administrator account on the target server. |
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.