Example 1

The command shown in Example 1 returns information about all the centralized logging security groups configured for use in the organization.

	Copy Code
Get-CsClsSecurityGroup

Example 2

In Example 2, information is returned for a single centralized logging security group: the group with the Identity global/helpdesk.

	Copy Code
Get-CsClsSecurityGroup -Identity "global/HelpDesk"

Example 3

Example 3 returns information for all the centralized logging security groups configured at the global scope. To do this, the Filter parameter is included along with the filter value "global/*"; that filter value limits the returned data to groups configured at the global scope.

	Copy Code
Get-CsClsSecurityGroup -Filter "global/*"

Example 4

The command shown in Example 4 returns all the centralized logging security groups where the access level has been set to RedmondSupport. To carry out this task, the command first calls the Get-CsClsSecurityGroup cmdlet without any parameters; that returns a collection of all the available centralized logging security groups. That collection is then piped to the Where-Object cmdlet, which picks out only those groups where the AccessLevel property is equal to RedmondSupport.

	Copy Code
Get-CsClsSecurityGroup | Where-Object {$_.AccessLevel -eq "RedmondSupport"}

The centralized logging service (which replaces the OCSLogger and OCSTracer tools used in Microsoft Lync Server 2010) provides a way for administrators to manage logging and tracing for all computers and pools running Lync Server 2013. Centralized logging enables administrators to stop, start, and configure logging for one or more pools and computers by using a single command; for example, you can use one command to enable Address Book service logging on all your Address Book servers. This differs from the OCSLogger and OCSTracer tools, which had to be individually managed (including individually stopped and started) on each server. In addition, the centralized logging service also provides a way for administrators to search trace logs from the command, using Windows PowerShell command-line interface and the Search-CsClsLogging cmdlet.

With Lync Online, security groups are used to determine which users have access to the personally-identifiable information that is written to the log files. Security groups are created by using the New-CsClsSecurityGroup cmdlet and then are added to a collection of centralized logging configuration settings. You can return information about your centralized logging security groups by using the Get-CsClsSecurityGroup cmdlet.

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:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Get-CsClsSecurityGroup"}

Lync Server Control Panel: The functions carried out by the Get-CsClsSecurityGroup cmdlet are not available in the Lync Server Control Panel.

None. The Get-CsClsSecurityGroup cmdlet does not accept pipelined input.

The Get-CsClsSecurityGroup cmdlet returns instances of the Microsoft.Rtc.Management.WritableConfig.Settings.CentralizedLogging.SecurityGroup#Decorated object.