Skip to content
This repository was archived by the owner on Feb 20, 2022. It is now read-only.

Commit 1f10c1b

Browse files
authored
Merge pull request MicrosoftDocs#3048 from nschonni/fix--skype/skype-ps/skype/Move-CsUser.md
fix: skype/skype-ps/skype/Move-CsUser.md
2 parents 3c2693f + da53408 commit 1f10c1b

File tree

1 file changed

+54
-57
lines changed

1 file changed

+54
-57
lines changed

skype/skype-ps/skype/Move-CsUser.md

Lines changed: 54 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -14,84 +14,80 @@ ms.reviewer:
1414

1515
Moves one or more user accounts enabled for Skype for Business Server to a new Registrar pool, or to Office 365 (either to Teams or Skype for Business Online).
1616

17-
1817
## SYNTAX
1918

20-
### (Default)
19+
### (Default)
20+
2121
```
2222
Move-CsUser [-Identity] <UserIdParameter> [-Target] <Fqdn> [-Credential <PSCredential>] [-MoveToTeams] [-HostedMigrationOverrideUrl <String>] [-BypassEnterpriseVoiceCheck] [-BypassAudioConferencingCheck] [-TenantAdminUserName] [-Confirm] [-Force] [-PassThru] [-WhatIf] [<CommonParameters>]
2323
```
2424

25-
26-
27-
28-
2925
## DESCRIPTION
3026

3127
The Move-CsUser cmdlet enables you to move a user account enabled for Skype for Business in the following scenarios:
32-
- from an on-premises Skype for Business deployment to Teams-only in Office 365 (or the reverse)
33-
- from an on-premises Skype for Business deployment to Skype for Business Online in Office 365 (or the reverse)
34-
- from one registrar pool to another, in an on-premises Skype for Business Server deployment.
35-
The Move-CsUser cmdlet affects only the user's Skype for Business Server account location; it does not move the user's Active Directory account to a new organizational unit (OU) or other new location.
28+
29+
- from an on-premises Skype for Business deployment to Teams-only in Office 365 (or the reverse)
30+
- from an on-premises Skype for Business deployment to Skype for Business Online in Office 365 (or the reverse)
31+
- from one registrar pool to another, in an on-premises Skype for Business Server deployment.
32+
33+
The Move-CsUser cmdlet affects only the user's Skype for Business Server account location; it does not move the user's Active Directory account to a new organizational unit (OU) or other new location.
3634

3735
When moving a user to or from Office 365 (either Skype for Business Online or Teams):
38-
- Skype for Business hybrid must be configured. For more information, see [Deploy hybrid connectivity between Skype for Business Server and Skype for Business Online](https://docs.microsoft.com/SkypeForBusiness/skype-for-business-hybrid-solutions/deploy-hybrid-connectivity/deploy-hybrid-connectivity).
39-
- To move a user to Office 365, specify the ProxyFqdn of the hosting provider as the Target. In most cases, this is "sipfed.online.lync.com" but in specialized environments there will be variants of this address. For more details, see [Move users between on-premises and cloud](https://docs.microsoft.com/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud).
40-
- When migrating from on-premises to the cloud, meetings are migrated from Skype for Business Server to online. If the `MoveToTeams` switch is specified, the meetings will be migrated to Teams meetings. Otherwise, meeetings are migrated to Skype for Business Online. Teams-only users can still join meetings hosted in Skype for Business. For details see [Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms).
41-
- Moving a user to Teams is achieved by specifying the MoveToTeams switch. This performs the same operations as a move to Skype for Business Online (without the specifying -MoveToTeams) and also performs the following actions:
42-
- TeamsUpgradePolicy with Mode=TeamsOnly is assigned to the online user account.
43-
- Meeting migration is triggered to move meetings to Teams instead of Skype for Business Online. This functionality is currently available to TAP customers only. For customers not in TAP, meetings are always migrated to Skype for Business Online.
44-
- Contacts are moved in all cases, unless -force is specified.
4536

46-
47-
> [!NOTE]
48-
> The MoveToTeams switch is only available on Skype for Business Server 2019 and CU8 for Skype for Business Server 2015. Organizations using other versions of Skype for Business Server must first move the user to Skype for Business Online, and then apply TeamsUpgradePolicy.
37+
- Skype for Business hybrid must be configured. For more information, see [Deploy hybrid connectivity between Skype for Business Server and Skype for Business Online](https://docs.microsoft.com/en-us/SkypeForBusiness/skype-for-business-hybrid-solutions/deploy-hybrid-connectivity/deploy-hybrid-connectivity).
38+
- To move a user to Office 365, specify the ProxyFqdn of the hosting provider as the Target. In most cases, this is "sipfed.online.lync.com" but in specialized environments there will be variants of this address. For more details, see [Move users between on-premises and cloud](https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud).
39+
- When migrating from on-premises to the cloud, meetings are migrated from Skype for Business Server to online. If the `MoveToTeams` switch is specified, the meetings will be migrated to Teams meetings. Otherwise, meetings are migrated to Skype for Business Online. Teams-only users can still join meetings hosted in Skype for Business. For details see [Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/en-us/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms).
40+
- Moving a user to Teams is achieved by specifying the MoveToTeams switch. This performs the same operations as a move to Skype for Business Online (without the specifying -MoveToTeams) and also performs the following actions:
4941

42+
- TeamsUpgradePolicy with Mode=TeamsOnly is assigned to the online user account.
43+
- Meeting migration is triggered to move meetings to Teams instead of Skype for Business Online. This functionality is currently available to TAP customers only. For customers not in TAP, meetings are always migrated to Skype for Business Online.
5044

45+
- Contacts are moved in all cases, unless -force is specified.
5146

47+
> [!NOTE]
48+
> The MoveToTeams switch is only available on Skype for Business Server 2019 and CU8 for Skype for Business Server 2015. Organizations using other versions of Skype for Business Server must first move the user to Skype for Business Online, and then apply TeamsUpgradePolicy.
5249
5350
## EXAMPLES
5451

55-
### ------- EXAMPLE 1: Move a user to Teams-----------------------
56-
```
52+
### ------- EXAMPLE 1: Move a user to Teams-----------------------
5753

54+
```powershell
5855
$cred=get-credential
5956
Move-CsUser -Identity "[email protected]" -Target "sipfed.online.lync.com" -MoveToTeams -Credential $cred
6057
```
6158

6259
In Example 1, the Move-CsUser cmdlet is used to move the user account with sip address [email protected] to Teams. This user will now be a Teams only user. If -Credential parameter is not specified, the admin will be prompted for credentials.
6360

64-
### ------- EXAMPLE 2: Move a user to Skype for Business Online ----
65-
```
61+
### ------- EXAMPLE 2: Move a user to Skype for Business Online ----
62+
63+
```powershell
6664
$cred=get-credential
6765
Move-CsUser -Identity [email protected] -Target "sipfed.online.lync.com" -Credential $cred
6866
```
6967

70-
In Example 2, the Move-CsUser cmdlet is used to move the user account with sip address [email protected] to Skype for Business Online. This is the same cmdlet usage as example 1, except the MoveToTeams switch is not specified.
68+
In Example 2, the Move-CsUser cmdlet is used to move the user account with sip address [email protected] to Skype for Business Online. This is the same cmdlet usage as example 1, except the MoveToTeams switch is not specified.
7169

72-
### -------- EXAMPLE 3: Move a user to another on-premises pool-------
73-
```
70+
### -------- EXAMPLE 3: Move a user to another on-premises pool-------
7471

75-
Move-CsUser -Identity "Pilar Ackerman" -Target "atl-cs-001.litwareinc.com"
72+
```powershell
73+
Move-CsUser -Identity "Pilar Ackerman" -Target "atl-cs-001.litwareinc.com"
7674
```
7775

7876
In Example 3, the Move-CsUser cmdlet is used to move the user account with the Identity Pilar Ackerman to the Registrar pool atl-cs-001.litwareinc.com.
7977

78+
### --------- EXAMPLE 4: Move multiple users ---------------------------
8079

81-
### --------- EXAMPLE 4: Move multiple users ---------------------------
82-
```
83-
80+
```powershell
8481
Get-CsUser -OU "ou=Finance,dc=litwareinc,dc=com" | Move-CsUser -Target "atl-cs-001.litwareinc.com"
8582
```
8683

8784
In Example 4, all the user accounts in the Finance organizational unit (OU) are moved to the Registrar pool atl-cs-001.litwareinc.com.
8885
To carry out this task, the command first uses the Get-CsUser cmdlet and the OU parameter to retrieve a collection of all the user accounts in the Finance OU. After the data has been retrieved, the information is piped to the Move-CsUser cmdlet, which moves each account in the collection to the Registrar pool atl-cs-001.litwareinc.com.
8986

90-
91-
9287
## PARAMETERS
9388

9489
### -Identity
90+
9591
Indicates the Identity of the user account to be moved.
9692
User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory display name (for example, Ken Myer).
9793
User Identities can also be referenced by using the user's Active Directory distinguished name.
@@ -102,7 +98,7 @@ For example, the Identity "* Smith" returns all the users with who have a displa
10298
```yaml
10399
Type: UserIdParameter
104100
Parameter Sets: (All), Identity
105-
Aliases:
101+
Aliases:
106102
Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
107103

108104
Required: True
@@ -118,11 +114,10 @@ If moving to an on-premises pool (either from another pool or from Office 365),
118114
119115
If moving to Office 365, this must be set to the ProxyFqdn value of the hosting provider. In most cases this is sipfed.online.lync.com. The value of the ProxyFqdn can be obtained using Get-CsHostingProvider
120116
121-
122117
```yaml
123118
Type: Fqdn
124119
Parameter Sets: (All)
125-
Aliases:
120+
Aliases:
126121
Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
127122

128123
Required: True
@@ -132,9 +127,8 @@ Accept pipeline input: False
132127
Accept wildcard characters: False
133128
```
134129
135-
136-
137130
### -MoveToTeams
131+
138132
If specified, the user will be moved to Office 365 as a Teams-only user. This will ensure incoming chats and calls land in the user's Teams client. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
139133
140134
```yaml
@@ -149,17 +143,14 @@ Accept pipeline input: False
149143
Accept wildcard characters: False
150144
```
151145
152-
153-
154146
### -Credential
155147
156148
Enables you to run the Move-CsUser cmdlet under alternate credentials, which is typically required when moving to Office 365. To use the Credential parameter you must first create a PSCredential object using the Get-Credential cmdlet. For details, see the Get-Credential cmdlet help topic.
157149
158-
159150
```yaml
160151
Type: PSCredential
161152
Parameter Sets: (All)
162-
Aliases:
153+
Aliases:
163154
Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
164155

165156
Required: False
@@ -173,12 +164,10 @@ Accept wildcard characters: False
173164
174165
The hosted migration service is the service in Office 365 that performs user moves. By default, there is no need to specify a value for this parameter, as long as the hosting provider has its AutoDiscover URL properly configured and you are using an admin account the ends in .onmicrosoft.com. If you are using a user account from on-premises that synchronized to the cloud, you must specify this parameter. See [Required administrative credentials](https://docs.microsoft.com/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud#required-administrative-credentials).
175166
176-
177-
178167
```yaml
179168
Type: String
180169
Parameter Sets: (All)
181-
Aliases:
170+
Aliases:
182171
Applicable: Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
183172

184173
Required: False
@@ -189,6 +178,7 @@ Accept wildcard characters: False
189178
```
190179
191180
### -BypassAudioConferencingCheck
181+
192182
By default, if the on-premise user is configured for dial in conferencing, moving the user to Office 365 will provision the user for Audio Conferencing, for an additional license is required. If you want to move such a user to Office 365 but do not want to configure them for Audio Conferencing, specify this switch to by-pass the license check. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
193183
194184
```yaml
@@ -202,8 +192,10 @@ Default value: None
202192
Accept pipeline input: False
203193
Accept wildcard characters: False
204194
```
195+
205196
### -BypassEnterpriseVoiceCheck
206-
By default, if the on-premise user is configured for Enteprise Voice, moving the user to Office 365 will provision the user for Microsoft Phone System, for an additional license is required. If you want to move such a user to Office 365 but do not want to configure them for Phone System, specify this switch to by-pass the license check. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
197+
198+
By default, if the on-premise user is configured for Enterprise Voice, moving the user to Office 365 will provision the user for Microsoft Phone System, for an additional license is required. If you want to move such a user to Office 365 but do not want to configure them for Phone System, specify this switch to by-pass the license check. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
207199
208200
```yaml
209201
Type: SwitchParameter
@@ -218,8 +210,8 @@ Accept wildcard characters: False
218210
```
219211
220212
### -TenantAdminUserName
221-
This is an optional parameter that if, specified, pre-populates the username of the tenant admin when moving users to or from Office 365. This can be useful for scenarios involving smart card authentication or 2 factor auth. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
222213
214+
This is an optional parameter that if, specified, pre-populates the username of the tenant admin when moving users to or from Office 365. This can be useful for scenarios involving smart card authentication or 2 factor auth. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
223215
224216
```yaml
225217
Type: UserIdParameter
@@ -232,15 +224,15 @@ Accept pipeline input: False
232224
Accept wildcard characters: False
233225
```
234226
235-
236227
### -Force
228+
237229
If present, moves the user account without moving contacts or meetings. Contacts and meetings are not recoverable.
238230
If not present, both the account and the associated data are moved.
239231
240232
```yaml
241233
Type: SwitchParameter
242234
Parameter Sets: (All)
243-
Aliases:
235+
Aliases:
244236
Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
245237

246238
Required: False
@@ -252,6 +244,7 @@ Accept wildcard characters: False
252244
253245
254246
### -Confirm
247+
255248
Enables you to bypass the confirmation prompt that would otherwise appear when you attempt to move a user.
256249
To bypass the confirmation prompt, include the Confirm parameter using this syntax:
257250
@@ -275,12 +268,13 @@ Accept wildcard characters: False
275268
```
276269

277270
### -Report
271+
278272
PARAMVALUE: String
279273

280274
```yaml
281275
Type: String
282276
Parameter Sets: Identity, Users
283-
Aliases:
277+
Aliases:
284278
Applicable: Skype for Business Server 2015, Skype for Business Server 2019
285279
286280
Required: False
@@ -291,13 +285,14 @@ Accept wildcard characters: False
291285
```
292286

293287
### -PassThru
288+
294289
Enables you to pass a user object through the pipeline that represents the user account being moved.
295290
By default, the Move-CsUser cmdlet does not pass objects through the pipeline.
296291

297292
```yaml
298293
Type: SwitchParameter
299294
Parameter Sets: (All)
300-
Aliases:
295+
Aliases:
301296
Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
302297
303298
Required: False
@@ -308,6 +303,7 @@ Accept wildcard characters: False
308303
```
309304

310305
### -WhatIf
306+
311307
Describes what would happen if you executed the command without actually executing the command.
312308

313309
```yaml
@@ -323,22 +319,24 @@ Accept pipeline input: False
323319
Accept wildcard characters: False
324320
```
325321

326-
327-
328322
### CommonParameters
323+
329324
This cmdlet supports the common parameters: `-Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).`
330325

331326
## INPUTS
332327

328+
### String
333329

334-
###
335-
String or Microsoft.Rtc.Management.ADConnect.Schema.ADUser object.
336330
The Move-CsUser cmdlet accepts a pipelined string value representing the Identity of a user account that has been enabled for Skype for Business Server.
331+
332+
### Microsoft.Rtc.Management.ADConnect.Schema.ADUser
333+
337334
The cmdlet also accepts pipelined instances of the Active Directory user object.
338335

339336
## OUTPUTS
340337

341-
###
338+
### None
339+
342340
The Move-CsUser cmdlet does not return a value or object.
343341
Instead, the cmdlet modifies instances of the Microsoft.Rtc.Management.ADConnect.Schema.ADUser object.
344342

@@ -353,4 +351,3 @@ Instead, the cmdlet modifies instances of the Microsoft.Rtc.Management.ADConnect
353351
[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype)
354352

355353
[Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms)
356-

0 commit comments

Comments
 (0)