Example 1

The command shown in Example 1 returns information about all the Persistent Chat policies configured for use in the organization.

	Copy Code
Get-CsPersistentChatPolicy

Example 2

In Example 2, information is returned only for the per-user Persistent Chat policy with the Identity RedmondPersistentChatPolicy.

	Copy Code
Get-CsPersistentChatPolicy -Identity "RedmondPersistentChatPolicy"

Example 3

In Example 3, information is returned for all the Persistent Chat policies configured at the site scope. This is done by including the Filter parameter and the parameter value "site:*".

	Copy Code
Get-CsPersistentChatPolicy -Filter "site:*"

Example 4

In Example 4, information is returned only for those Persistent Chat policies in which Persistent Chat is enabled. To do this, the Get-CsPersistentChatPolicy cmdlet is first called without any parameters in order to return a collection of all the Persistent Chat policies configured for use in the organization. This collection is then piped to the Where-Object cmdlet, which picks out only those policies where the EnablePersistentChat property is equal to True ($True).

	Copy Code
Get-CsPersistentChatPolicy | Where-Object {$_.EnablePersistentChat -eq $True}

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.

By default, users are not granted access to the Persistent Chat service; that access can only be granted if the user is managed by a Persistent Chat policy that allows for the user of the service. When you install Lync 2013, all your users are managed by a global Persistent Chat policy in which the use of Persistent Chat is disabled. If you want to give all your users access to the service you can simply set the EnablePersistentChat property in this global policy to True. Alternatively, you can create additional policies at the site or at the per-user scope, and thus provide Persistent Chat access to some users while denying this access to other users.

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 command-line interface prompt:

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

Lync Server Control Panel: To view Persistent Chat policy information in the Lync Server Control Panel, click Persistent Chat and then click Persistent Chat Policy.

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

The Get-CsPersistentChatPolicy cmdlet returns instances of the Microsoft.Rtc.Management.WritableConfig.Policy.PersistentChat.PersistentChatPolicy object.