![skype permissions settings skype permissions settings](https://its.uiowa.edu/sites/its.uiowa.edu/files/styles/large/public/wysiwyg_uploads/Adding%20Delegate.png)
Unlike the Windows PowerShell cmdlets, CLSController cannot define new scenarios, manage scope at a site or global level, and many other limitations of a finite command set that cannot be dynamically configured. While CLSController does provide a fast and efficient way to issue commands and get results, the command set for CLSController is limited by the finite commands that you have available from the command line. Windows PowerShell provides a rich method to configure and define scenarios, and to reuse those scenarios in a meaningful way for your troubleshooting scenarios. There are fundamental differences between the command-line commands that you can run in Windows PowerShell or CLSController. To return a list of all the RBAC roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Skype for Business Server Management Shell or the Windows PowerShell prompt: Get-CsAdminRole | Where-Object To configure the Centralized Logging Service scope by using the Skype for Business Server Management Shell, you must be a member of either the CsAdministrator or the CsServerAdministrator role-based access control (RBAC) security groups, or a custom RBAC role that contains either of these two groups. The Centralized Logging Service can be run at a scope that includes a single computer or a pool of computers, at a site scope (that is, a defined site such as the site Redmond that contains a collection of computer and pools in your deployment), or at a global scope (that is, all computers and pools in your deployment). This is not to say that there is no use for these cmdlets in on-premises deployments, but their use is a more advanced topic that is not covered in this documentation. The settings defined in these cmdlets will not hinder or cause any adverse behavior, but they are designed for use with Microsoft 365 or Office 365 and will not yield the expected results in on-premises deployments.
![skype permissions settings skype permissions settings](https://techwiser.com/wp-content/uploads/2019/04/fix-skype-microphone-not-working-issue-1.png)
CsClsSecurityGroup cmdlets: Get-CsClsSecurityGroup, Set-CsClsSecurityGroup, New-CsClsSecurityGroup, and Remove-CsClsSecurityGroup.CsClsSearchTerm cmdlets: Get-CsClsSearchTerm and Set-CsClsSearchTerm.CsClsRegion cmdlets: Get-CsClsRegion, Set-CsClsRegion, New-CsClsRegion, and Remove-CsClsRegion.Although they may appear to work, the following cmdlets are not designed to function with Skype for Business Server 2015 on-premises deployments: Not all Windows PowerShell cmdlets listed for the Centralized Logging Service are intended for use with Skype for Business Server 2015 on-premises deployments.