Example 1

The command shown in Example 1 deletes the Persistent Chat endpoint that has the Identity "sip:pce@litwareinc.com". In this example, the SIP address is used for the Identity

	Copy Code
Remove-CsPersistentChatEndpoint -Identity "sip:pce@litwareinc.com"

Example 2

Example 2 deletes all the Persistent Chat endpoints configured for the pool atl-pcpool-001.litwareinc.com. To carry out this task, the command first uses the Get-CsPersistentChatEndpoint cmdlet and the PoolFqdn parameter to return all the endpoints for the pool atl-pcpool-001.litwareinc.com. The endpoints in that collection are then piped to, and removed by, the Remove-CsPersistentChatEndpoint cmdlet.

	Copy Code
Get-CsPersistentChatEndpoint -PoolFqdn "atl-pcpool-001.litwareinc.com" | Remove-CsPersistentChatEndpoint

Example 3

The command shown in Example 3 deletes all the Persistent Chat endpoints configured for use in the organization. To do this, the command first calls the Get-CsPersistentChatEndpoint cmdlet to return a collection of all the Persistent Chat endpoints. This collection is then piped to the Remove-CsPersistentChatEndpoint cmdlet, which deletes each endpoint in the collection.

	Copy Code
Get-CsPersistentChatEndpoint | Remove-CsPersistentChatEndpoint

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.

However, if you have users running legacy clients (such as Microsoft Lync 2010 these users might find the default Persistent Chat URIs difficult to work with and difficult to use when pointing their legacy client towards the pool. Because of this, administrators can use the New-CsPersistentChatEndpoint cmdlet to create an additional contact object for the pool, a contact object that provides a friendlier, easier-to-use URI. These endpoints can later be removed by using the Remove-CsPersistentChatEndpoint 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 command-line interface prompt:

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

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

The Remove-CsPersistentChatEndpoint cmdlet accepts pipelined instances of the Microsoft.Rtc.Management.ADConnect.Schema.OCSPersistentChatContact class.

None. The Remove-CsPersistentChatEndpoint cmdlet does not return objects or data.