Topic Last Modified: 2013-02-21

Creates a PSTN or an Audio Conferencing Provider test that can then be assigned to a watcher node configuration. Watcher nodes are computers that periodically use Microsoft System Center Operations Manager and Lync Server 2013 synthetic transactions to verify that Lync Server components are working as expected. This cmdlet was introduced in Lync Server 2013.


New-CsExtendedTest -Name <String> -TestType <AudioConferencingProvider | PSTN> [-TestUsers <PSListModifier>]


Example 1

The commands shown in Example 1 create a new extended test (with the TestType of PSTN), then adds that extended test to a new watcher node for the pool In the first command in the example, the New-CsExtendedTest cmdlet is used to create an extended test named PSTN Test; this test includes the test users and (Note that these two test users must have already been configured using the Set-CsTestUserCredential cmdlet.) The resulting extended test object is then stored in a variable named $x.

In the second command, the new extended test is added to the newly-created watcher node for This is done by using the ExtendedTests parameter and the syntax @{Add=$x}.

Copy Code
$x = New-CsExtendedTest -TestUsers "", "" -Name "PSTN Test" -TestType "PSTN"

New-CsWatcherNodeConfiguration -TargetFqdn "" -PortNumber 5061 -TestUsers "","" -ExtendedTests @{Add=$x}

Detailed Description

If you are using Microsoft System Center Operations Manager to monitor Lync Server 2013 then you have the option of setting up "watcher nodes": computers that periodically, and automatically, run synthetic transactions in order to verify that Lync Server is working as expected. Watcher nodes are assigned to pools, and are managed using the CsWatcherNodeConfiguration cmdlets. Note that you do not need to install watcher nodes if you are using System Center Operations Manager. You can still monitor your system without using watcher nodes; the only difference is that any synthetic transactions you want to run will need to be invoked manually rather than automatically invoked by Operations Manager.

When you configure a watcher node, you have the option of adding a PSTN or an Audio Conferencing Provider test as an "extended test"; these extended tests can be used instead of or in addition to the standard set of tests run by a watcher node computer. Extended tests must be created using the New-CsExtendedTest cmdlet and then added to the appropriate watcher node.

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 "New-CsExtendedTest"}

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


Parameter Required Type Description




Friendly name to be given to the extended test.




Type of testing to be carried out by the extended test. Allowed values are:


* AudioConferencingProvider

You can only specify a single TestType per extended test.




SIP address of the user account(s) that will serve as test users. Multiple accounts can be specified by separating those accounts using commas; for example:

–TestUsers "", ""

You must specify at least two test users when using the PSTN TestType.

Input Types

None. The New-CsExtendedTest cmdlet does not accept pipelined input

Return Types

The New-CsExtendedTest cmdlet creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.WatcherNode.ExtendedTest object.

See Also