You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Set-MigrationEndpoint.md
+6-104Lines changed: 6 additions & 104 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ schema: 2.0.0
8
8
## SYNOPSIS
9
9
This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
10
10
11
-
Use the Set-MigrationEndpoint cmdlet to edit settings for cutover or staged Exchange migrations, IMAP migrations, and remote moves.
11
+
Use the Set-MigrationEndpoint cmdlet to edit settings for cutover or staged Exchange migrations, IMAP migrations and remote moves.
12
12
13
13
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
14
14
@@ -17,41 +17,15 @@ For information about the parameter sets in the Syntax section below, see Exchan
Use the Set-MigrationEndpoint cmdlet to configure settings for different types of migration:
32
-
33
-
- Cross-forest move Move mailboxes between two different on-premises Exchange forests. Cross-forest moves require the use of a RemoteMove endpoint.
34
-
35
-
- 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.
36
-
37
-
- 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.
38
-
39
-
- 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.
40
-
41
-
- 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.
42
-
43
-
- 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.
44
-
45
-
For more information about the different move and migration scenarios, see:
46
-
47
-
- Mailbox moves in Exchange 2013
48
-
49
-
- Manage on-premises moves
50
-
51
-
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.
52
-
53
-
!!! Exchange Server 2016, Exchange Online
54
-
55
29
Use the Set-MigrationEndpoint cmdlet to configure settings for different types of migration:
56
30
57
31
- Cross-forest move: Move mailboxes between two different on-premises Exchange forests. Cross-forest moves require the use of a RemoteMove endpoint.
@@ -76,42 +50,14 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
76
50
77
51
## EXAMPLES
78
52
79
-
### Example 1 -------------------------- (Exchange Server 2013)
This example changes the MaxConcurrentIncrementalSyncs setting to 50 on the CutoverExchangeEndpoint01 migration endpoint using the NSPI server Server01.
85
-
86
-
### Example 1 -------------------------- (Exchange Server 2016)
This example changes the MaxConcurrentIncrementalSyncs setting to 50 on the CutoverExchangeEndpoint01 migration endpoint using the NSPI server Server01.
92
-
93
-
### Example 1 -------------------------- (Exchange Online)
This example changes the MaxConcurrentIncrementalSyncs setting to 50 on the CutoverExchangeEndpoint01 migration endpoint using the NSPI server Server01.
99
59
100
-
### Example 2 -------------------------- (Exchange Server 2013)
This example changes the MaxConcurrentMigrations setting to 10 on the Onboardingmigrationendpoint01 migration endpoint using the remote server, Server01.
106
-
107
-
### Example 2 -------------------------- (Exchange Server 2016)
This example changes the MaxConcurrentMigrations setting to 10 on the Onboardingmigrationendpoint01 migration endpoint using the remote server, Server01.
113
-
114
-
### Example 2 -------------------------- (Exchange Online)
The Credentials parameter specifies the credentials to use for connecting to the remote endpoint. Credentials should be used when creating either a staged or cutover Exchange endpoint or a RemoteMove endpoint.
181
-
182
-
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 (https://go.microsoft.com/fwlink/p/?linkId=142122).
183
-
184
-
185
-
186
-
!!! Exchange Server 2016, Exchange Online
187
-
188
124
The Credentials parameter specifies the credentials to use for connecting to the remote endpoint. Credentials should be used when creating either a staged or cutover Exchange endpoint or a RemoteMove endpoint.
189
125
190
126
This parameter requires you to create a credentials object by using the Get-Credential cmdlet. For more information, see Get-Credential (https://go.microsoft.com/fwlink/p/?linkId=142122).
191
127
192
128
193
-
194
129
```yaml
195
130
Type: PSCredential
196
131
Parameter Sets: (All)
@@ -222,24 +157,6 @@ Accept pipeline input: False
222
157
Accept wildcard characters: False
223
158
```
224
159
225
-
### -EmailAddress
226
-
This parameter is available only in the cloud-based service.
227
-
228
-
The EmailAddress parameter specifies the email address of an administrator account that can access the remote server.
229
-
230
-
```yaml
231
-
Type: SmtpAddress
232
-
Parameter Sets: (All)
233
-
Aliases:
234
-
Applicable: Exchange Server 2013
235
-
236
-
Required: False
237
-
Position: Named
238
-
Default value: None
239
-
Accept pipeline input: False
240
-
Accept wildcard characters: False
241
-
```
242
-
243
160
### -ExchangeServer
244
161
This parameter is available only in the cloud-based service.
The RemoteServer parameter specifies the remote server depending on the protocol type for moves.
357
-
358
-
- For Microsoft Exchange Server 2013 and Exchange Server 2010 moves, this parameter refers to the FQDN of a Client Access server or array, or group of Client Access servers behind a supported network load balancer.
359
-
360
-
- For IMAP moves, this parameter refers to the FQDN of the IMAP server.
361
-
362
-
363
-
364
-
!!! Exchange Server 2016, Exchange Online
365
-
366
271
The RemoteServer parameter specifies the remote server depending on the protocol type for moves:
367
272
368
273
- Exchange server moves: The FQDN of an Exchange server that has the Client Access role installed, a Client Access server array, or a group of Client Access servers that are located behind a supported network load balancer.
369
274
370
275
- IMAP moves: The FQDN of the IMAP server.
371
276
372
-
373
-
374
277
```yaml
375
278
Type: Fqdn
376
279
Parameter Sets: (All)
@@ -536,4 +439,3 @@ To see the return types, which are also known as output types, that this cmdlet
0 commit comments