Below are the steps to configure the Persistent Chat Message Health Test along with the Test users.
Lync/Skype Persistent Chat Message Health Test
This test verifies whether two users can exchange messages using the Persistent Chat service. The test logs two
users on to Lync Server 2013 or to Skype for Business 2015, connects the users to a persistent chat room,
exchanges a pair of messages, exits the chat room and logs off the two users.
This test will fail if you have not created a chat room or if the two test users have not been assigned a Persistent
Chat policy that provides access to the Persistent Chat service.
The test is not available for Lync 2010.
All The test uses the PowerShell Test-CsPersistentChatMessage –TargetPoolFqdn
<target fqdn> cmdlet. Before the cmdlet can work, you must use Setup
parameter to enable it.
• Run the Test-CsPersistentChatMessage cmdlet with the Setup
parameter from a computer that has access to the Lync/Skype server
topology.
NOTE: When you use the Setup parameter, you must also use the
TestUser1SipAddress and the TestUser2SipAddress parameters.
For example, suppose you are running the Test-CsPersistentChatMessage cmdlet with the Setup parameter for a
pool named LyncEnt-pool.domain.com. First you must create two test users in the pool. If you are
running the test against more than one Lync 2013 registrar pool, you must create same test users for each pool.
Creating a Test User for the Lync/Skype
Environment
Several of the Lync/Skype synthetic transaction health tests require test users. You must create test users for
each registrar pool against which you want to run health tests.
These test users are created using a Microsoft PowerShell cmdlet called NewCsHealthMonitoringConfiguration.
You execute the PowerShell cmdlet in the Lync Server Management
Shell on the Lync server or the Skype for Business Server Management Shell on the Skype server. For more
information about this cmdlet, go to www.microsoft.com.
The script has the following syntax:
New-CsHealthMonitoringConfiguration
-Identify <XdsGlobalRelativeIdentity>
-FirstTestUserSipUri <String>
-SecondTestUserSipUri <String>
[-Confirm [<SwitchParameter>]]
[-FirstTestSamAccountName <String>]
[-Force <SwitchParameter>]
[-InMemory <SwitchParameter>]
[-SecondTestSamAccountName <String>]
[-WhatIf [<SwitchParameter>]]
where:
An example use of the cmdlet follows:
New-CsHealthMonitoringConfiguration
-Identity LyncEnt-pool.domain.com
-FirstTestUserSipUri "sip:testuser1@domain.com"
-SecondTestUserSipUri "sip:testuser2@domain.com"