Set-CsPersistentChatConfiguration

Set-CsPersistentChatConfiguration
    [[-Identity] <XdsIdentity>]
    [-Confirm]
    [-DefaultChatHistory <Int16>]
    [-Force]
    [-MaxFileSizeKB <UInt32>]
    [-ParticipantUpdateLimit <UInt32>]
    [-RoomManagementUrl <String>]
    [-WhatIf]
    [<CommonParameters>]

Set-CsPersistentChatConfiguration
    [-Confirm]
    [-DefaultChatHistory <Int16>]
    [-Force]
    [-Instance <PSObject>]
    [-MaxFileSizeKB <UInt32>]
    [-ParticipantUpdateLimit <UInt32>]
    [-RoomManagementUrl <String>]
    [-WhatIf]
    [<CommonParameters>]

The Persistent Chat service (which replaces the Group Chat service used in Microsoft Lync Server 2010) provides organizations with messaging and collaboration capabilities similar to those found in Internet discussion forums: users can exchange messages in real-time, yet can also revisit and restart those conversations at any time. Conversations can be based around specific topics, and these conversations can be made available to everyone or to only a selected set of users. Likewise, individual chat rooms can be configured so that anyone can post a message or configured so that only designated presenters can post messages.

The Persistent Chat service is managed, in part, by Persistent Chat configuration settings, which dictate such things as the number of previously-posted chat messages immediately available when you log on to a chat room (the chat history) or the maximum size of a file that can be uploaded to (or downloaded from) the service. These settings can be configured at the global or the site scope, or at the service scope (that is, you can have a custom collection of settings assigned to an individual Persistent Chat pool).

Skype for Business Server Control Panel: To modify an existing collection of Persistent Chat configuration settings using the Skype for Business Server Control Panel, click Persistent Chat, click Persistent Chat Configuration, then double-click the collection to be modified.

Set-CsPersistentChatConfiguration -Identity "global" -DefaultChatHistory 100

The command shown in Example 1 sets the DefaultChatHistory property of the global Persistent Chat configuration settings to 100.

Get-CsPersistentChatConfiguration | Set-CsPersistentChatConfiguration -DefaultChatHistory 100

In Example 2, the DefaultChatHistory property is set to 100 for all the Persistent Chat configuration settings. To carry out this task, the command first uses the Get-CsPersistentChatConfiguration cmdlet to return a collection of all the Persistent Chat configuration settings in the organization. This collection is then piped to the Set-CsPersistentChatConfiguration cmdlet, which modifies the DefaultChatHistory property for all the items in the collection.

Get-CsPersistentChatConfiguration -Filter "site:*" | Set-CsPersistentChatConfiguration -DefaultChatHistory 100

Example 3 shows how you can modify the DefaultChatHistory property for all the Persistent Chat configuration settings applied to the site scope. To do this, the command first calls the Get-CsPersistentChatConfiguration cmdlet along with the Filter parameter; the parameter value "site:*" limits the returned data to setting collections configured at the site scope. These settings are then piped to the Set-CsPersistentChatConfiguration cmdlet, which changes the DefaultChatHistory property for each settings collection to 100.

Get-CsPersistentChatConfiguration | Where-Object {$_.DefaultChatHistory -gt 100} | Set-CsPersistentChatConfiguration -DefaultChatHistory 100

In Example 4, the DefaultChatHistory property is modified for any collection of Persistent Chat configuration settings where the default chat history is currently greater than 100. To carry out this task, the command first uses the Get-CsPersistentChatConfiguration cmdlet to return a collection of all the Persistent Chat configuration settings in use in the organization. This collection is then piped to the Where-Object cmdlet, which picks out only those settings where the DefaultChatHistory property is greater than (-gt) 100. In turn, that filtered collection is piped to the Set-CsPersistentChatConfiguration cmdlet, which takes each item in the filtered collection and sets the value of the DefaultChatHistory property to 100.

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.

The Set-CsPersistentChatConfiguration cmdlet accepts pipelined instances of the Microsoft.Rtc.Management.WritableConfig.Settings.PersistentChat.PersistentChatConfiguration object.

Instead, the Set-CsPersistentChatConfiguration cmdlet modifies existing instances of the Microsoft.Rtc.Management.WritableConfig.Settings.PersistentChat.PersistentChatConfiguration object.