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: skype/skype-ps/skype/Move-CsUser.md
+4-19Lines changed: 4 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,6 @@ When moving a user to or from the Microsoft 365 cloud (TeamsOnly):
50
50
>
51
51
> - 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.
52
52
> - 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.
54
53
> - 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.
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.
66
65
67
-
### EXAMPLE 2: Move a user to Skype for Business Online
68
66
69
-
```powershell
70
-
# From an on-premises Skype for Business Server or Lync Server 2013 management shell window, run:
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
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.
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.
97
82
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.
98
83
99
-
### EXAMPLE 5: Move multiple users listed in a file
84
+
### EXAMPLE 4: Move multiple users listed in a file
0 commit comments