Skip to content

Commit 01dd524

Browse files
authored
Update Move-CsUser.md
remove note about changing mode to non-TEamsOnly after moving from onprem to cloud. we don't allow that anymore now that sfbo is retired.
1 parent ab0972a commit 01dd524

File tree

1 file changed

+4
-19
lines changed

1 file changed

+4
-19
lines changed

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

Lines changed: 4 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,6 @@ When moving a user to or from the Microsoft 365 cloud (TeamsOnly):
5050
>
5151
> - The `-MoveToTeams` switch is no longer required to move a user directly to Teams. Specifying this switch no longer has any impact, since users are always moved to TeamsOnly.
5252
> - If you are using Skype for Business Server 2015 with CU8 or later, we recommend you pass the `-UseOAuth` switch, which ensures the on-premises code authenticates using OAuth, instead of Legacy LiveID authentication. In Skype for Business Server 2019 and later versions, OAuth is always used hence the switch is not relevant on those versions.
53-
> - Prior to retirement of Skype for Business Online, organizations that still need to move users from on-premises to Skype for Business Online can do so uing a two-step process: First move the user from on-premises to TeamsOnly using `-Move-CsUser`, and after the move change the mode of the user to something other than TeamsOnly using `Grant-CsTeamsUpgradePolicy`. However, the ability to change a cloud user's mode to something other than TeamsOnly will soon be removed as part of Skype for Business Online retirement.
5453
> - Moving users from On-Premises to Teams requires TLS 1.2. TLS 1.0 and TLS 1.1 have been deprecated. Please visit [Disabling TLS 1.0 and 1.1 for Microsoft 365](/microsoft-365/compliance/tls-1.0-and-1.1-deprecation-for-office-365?view=o365-worldwide) and [Preparing for TLS 1.2 in Office 365 and Office 365 GCC](/microsoft-365/compliance/prepare-tls-1.2-in-office-365?view=o365-worldwide) for details.
5554
5655
## EXAMPLES
@@ -64,39 +63,25 @@ Move-CsUser -Identity "[email protected]" -Target "sipfed.online.lync.com" -Cre
6463

6564
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. It no longer matters whether the `-MoveToTeams` switch is specified.
6665

67-
### EXAMPLE 2: Move a user to Skype for Business Online
6866

69-
```powershell
70-
# From an on-premises Skype for Business Server or Lync Server 2013 management shell window, run:
71-
72-
$cred=get-credential
73-
Move-CsUser -Identity [email protected] -Target "sipfed.online.lync.com" -Credential $cred
74-
75-
# And then from a TeamsPowerShell window, remove TeamsOnly mode by running:
76-
77-
Grant-CsTeamsUpgradePolicy -Identity [email protected] -PolicyName $null
78-
```
79-
80-
In Example 2, the Move-CsUser cmdlet is first used to move the user account with sip address [email protected] to TeamsOnly in Microsoft 365. Then, using Teams PowerShell the mode is updated to remove TeamsOnly mode so the user can use Skype for Business Online.
81-
82-
### EXAMPLE 3: Move a user to another on-premises pool
67+
### EXAMPLE 2: Move a user to another on-premises pool
8368

8469
```powershell
8570
Move-CsUser -Identity "Pilar Ackerman" -Target "atl-cs-001.litwareinc.com"
8671
```
8772

8873
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.
8974

90-
### EXAMPLE 4: Move multiple users
75+
### EXAMPLE 3: Move multiple users
9176

9277
```powershell
9378
Get-CsUser -OU "ou=Finance,dc=litwareinc,dc=com" | Move-CsUser -Target "atl-cs-001.litwareinc.com"
9479
```
9580

96-
In Example 4, all the user accounts in the Finance organizational unit (OU) are moved to the Registrar pool atl-cs-001.litwareinc.com.
81+
In Example 4, all the user accounts in the Finance organizational unit (OU) are moved to the Registrar pool atl-cs-001.litwareinc.com in on-premises.
9782
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.
9883

99-
### EXAMPLE 5: Move multiple users listed in a file
84+
### EXAMPLE 4: Move multiple users listed in a file
10085

10186
```powershell
10287
Move-CsUser -UserList C:\Folder1\Folder2\file1.txt -Target "atl-cs-001.litwareinc.com" -Report C:\Folder1\Folder2\out.csv

0 commit comments

Comments
 (0)