Export (0) Print
Expand All
Expand Minimize

Get-CsPersistentChatState

Lync Server 2013
 

Topic Last Modified: 2013-03-07

Returns the state of one or more Persistent Chat service pools. Persistent Chat pools can be in one of two states: Normal, in which the pool uses its primary databases; or FailedOver, in which the pool uses the backup databases defined in the topology. This cmdlet was introduced in Lync Server 2013.

Get-CsPersistentChatState [-Identity <XdsIdentity>] <COMMON PARAMETERS>
Get-CsPersistentChatState [-Filter <String>] <COMMON PARAMETERS>
COMMON PARAMETERS: [-LocalStore <SwitchParameter>]

The command shown in Example 1 returns the state of all the Persistent Chat servers configured for use in the organization.

Get-CsPersistentChatState

Get-CsPersistentChatState -Identity "PersistentChatServer:atl-gc-001.litwareinc.com"

Example 3 returns state information for all Persistent Chat servers in the domain litwareinc.com. To do this, the Filter parameter is included along with the filter value "*.litwareinc.com". That filter value causes the Get-CsPersistentChatState cmdlet to return information for all the Persistent Chat servers that have an Identity that ends with the string value ".litwareinc.com".

Get-CsPersistentChatState -Filter "*.litwareinc.com"

The command shown in Example 4 returns state information for all the Persistent Chat servers that are currently failed over. To carry out this task, the command first calls the Get-CsPersistentChatState cmdlet without any parameters; that returns a collection of all the Persistent Chat servers in the organization. That collection is then piped to the Where-Object cmdlet, which picks out only those servers where the PoolState property is equal to (-eq) "FailedOver".

Get-CsPersistentChatState | Where-Object {$_.PoolState -eq "FailedOver"}

The Get-CsPersistentChatState cmdlet returns the state of one or more Persistent Chat pools. Persistent Chat pools can be in either the Normal state (in which the pool uses its primary databases) or in a FailedOver state, in which the pool uses its backup databases. You can use the Set-CsPersistentChatState cmdlet to change the state of a Persistent Chat pool; when you change the state of the pool, Lync Server 2013 will automatically change the state of each individual server in the pool.

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

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

 

Parameter Required Type Description

Filter

Optional

System.String

Enables you to use wildcards when retrieving one or more Persistent Chat states. For example, to return all the Persistent Chat states for the domain litwareinc.com, use this syntax:

-Filter "*.litwareinc.com"

You cannot use both the Filter parameter and the Identity parameter in the same command.

Identity

Optional

Microsoft.Rtc.Management.Xds.XdsIdentity

Unique identifier for the Persistent Chat pool. For example:

–Identity "PersistentChatServer:atl-gc-001.litwareinc.com"

If this parameter is omitted then the Get-CsPersistentChatState cmdlet returns information for all your Persistent Chat states.

LocalStore

Optional

System.Management.Automation.SwitchParameter

Retrieves the Persistent Chat state data from the local replica of the Central Management store rather than from the Central Management store itself.

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

The Get-CsPersistentChatState cmdlet returns instances of the Microsoft.Rtc.Management.WritableConfig.Settings.PersistentChat.PersistentChatState object.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft