Example 1

The command shown in Example 1 returns information about the eligible principals for the Persistent Chat category ITChat.

	Copy Code
Get-CsPersistentChatEligiblePrincipal -PersistentChatPoolFqdn "atl-persistentchat-001.litwareinc.com" -Category "ITChat"

Example 2

In Example 2, information is returned for all the eligible presenters for the chat room HelpDeskChatRoom.

	Copy Code
Get-CsPersistentChatEligiblePrincipal -PersistentChatPoolFqdn "atl-persistentchat-001.litwareinc.com" -Room "HelpDeskChatRoom" -Presenters

Example 3

Example 3 is a variation on the command shown in Example 2; in this example, however, information is returned only for Persistent Chat presenters which do not represent user accounts. To do this, the Get-CsPersistentChatEligiblePrincipal cmdlet is first used to return all the presenters for the chat room HelpDeskChatRoom. That collection is then piped to the Where-Object cmdlet, which selects only those presenters where the PersistentChatPrincipalType property is not equal to (-ne) "user".

	Copy Code
Get-CsPersistentChatEligiblePrincipal -PersistentChatPoolFqdn "atl-persistentchat-001.litwareinc.com" -Room "HelpDeskChatRoom" -Presenters | Where-Object {$_.PersistentChatPrincipalType -ne "user"}

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.

Chat categories provide the option of specifying certain users as Creators; that is, users who are allowed to create chat rooms within the category. Likewise, chat rooms provide the option of specifying users as Managers and/or Presenters. In order to be assigned any of these roles, however, the users in question must appear on the AllowedMembers list for the specified category/room. You can retrieve the list of allowed members for a room or category by using the Get-CsPersistentChatRoom cmdlet and the Get-CsPersistentChatCategory cmdlets However, if a security group, OU, or domain has been added to the allowed members list you will not see the names of the users in that security group, OU, or domain. For example, if the security group FinanceManagers is on the allowed list you will not see the names of the users who belong to FinanceManagers; instead, you will only see the name of the group.

To view the names of all the users in that group (as well as the names of all the users on the allowed members list for a category or room) use the Get-CsPersistentChatEligiblePrincipal room instead.

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-CsPersistentChatEligiblePrincipal"}

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

None. The Get-CsPersistentChatEligiblePrincipal cmdlet does not accept pipelined data.

The Get-CsPersistentChatEligiblePrincipal cmdlet returns instances of the Microsoft.Rtc.Management.GroupChat.Cmdlets.ADPersistentChatPrincipal object.