Skip to content

Commit 30ccef1

Browse files
committed
Update meeting room instructions
1 parent ca176ae commit 30ccef1

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

skype/skype-ps/skype/Enable-CsMeetingRoom.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ To enable a meeting room you must first create an Active Directory user account
1414
Note that, although meeting room objects are based on user accounts, these objects will not show up when you run the Get-CsUser cmdlet.
1515
This cmdlet was introduced in Lync Server 2013.
1616

17+
The process for creating and updating meeting rooms differs depending on your deployment of Skype for Business Online and Skype for Business Server. Make sure you are following the guidance here to set up your meeting rooms properly: https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-clients/with-office-365
18+
1719

1820
## SYNTAX
1921

@@ -38,6 +40,8 @@ Note that, for Skype for Business Server, there are no cmdlets for creating or r
3840
Instead, you use the Enable-CsMeetingRoom cmdlet to enable meeting rooms and the Disable-CsMeetingRoom cmdlet to disable meeting rooms.
3941
The resource account must already exist in order for you to enable the meeting room, and disabling a meeting room only removes that room from your collection of meeting rooms; it does not delete the resource mailbox account.
4042

43+
The process for creating and updating meeting rooms differs depending on your deployment of Skype for Business Online and Skype for Business Server. Make sure you are following the guidance here to set up your meeting rooms properly: https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-clients/with-office-365
44+
4145
The functions carried out by the Enable-CsMeetingRoom cmdlet are not available in the Skype for Business Server Control Panel.
4246

4347
To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

0 commit comments

Comments
 (0)