Example 1

The command shown in Example 1 modifies the centralized logging security group that has the Identity global/HelpDesk. In this example, the AccessLevel property is set to Tier3.

	Copy Code
Set-CsClsSecurityGroup -Identity "global/HelpDesk" -AccessLevel "Tier3"

Example 2

In Example 2, the access level is modified for all the centralized logging security groups configured at the global scope. To do this, the command first calls the Get-CsClsSecurityGroup cmdlet along with the Filter parameter; the filter value "global/*" limits the returned data to security groups configured at the global scope. Those groups are then piped to the Set-CsClsSecurityGroup cmdlet, which sets the AccessLevel property of each group to Tier3.

	Copy Code
Get-CsClsSecurityGroup -Filter "global/*" | Set-CsClsSecurityGroup-AccessLevel "Tier3"

Example 3

Example 3 shows how you can use a single command to change the access level for all the centralized logging security groups who share an existing access level. To carry out this task, the command first calls the Get-CsClsSecurityGroup cmdlet without any parameters in order to return a collection of all the centralized logging security groups. That collection is then piped to the Where-Object cmdlet, which selects only those groups where the AccessLevel is equal to (-eq) GlobalAccess. In turn, those groups are piped to the Set-CsClsSecurityGroup cmdlet, which takes each group and changes the AccessLevel to Tier3.

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

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 the Windows PowerShell command-line interface and the Search-CsClsLogging cmdlet.

With the Office 365 version of Lync Server, 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. After these groups have been created, you can modify their property values by using the Set-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 "Set-CsClsSecurityGroup"}

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

The Set-CsClsSecurityGroup cmdlet accepts pipelined instances of the Microsoft.Rtc.Management.WritableConfig.Settings.CentralizedLogging.SecurityGroup#Decorated object.

None. Instead, the Set-CsClsSecurityGroup cmdlet modifies existing instances of the Microsoft.Rtc.Management.WritableConfig.Settings.CentralizedLogging.SecurityGroup#Decorated object.