Installing and configuring watcher nodes in Lync Server 2013
Topic Last Modified: 2013-11-07
Watcher nodes are computers that periodically run Lync Server synthetic transactions. Synthetic transactions are Windows PowerShell cmdlets that verify that key end user scenarios—such as the ability to sign in to the system, or the ability to exchange instant messages—are working as expected. For Lync Server 2013, System Center Operations Manager can run the synthetic transactions shown in the following table. There are three different synthetic transaction types shown in the table:
Default. These are the synthetic transactions that a watcher node will run by default. When you create a new watcher node, you have the option of specifying which synthetic transactions that node will run. (That's the purpose of the Tests parameter used by the New-CsWatcherNodeConfiguration cmdlet.) If you do not use the Tests parameter when the watcher node is created, it will automatically run all the Default synthetic transactions and will not run any of the Non-default synthetic transactions. That means, for example, that the watcher node will be configured to run the Test-CsAddressBookService test, but will not be configured to run the Test-CsExumConnectivity test.
Non-default. As the name implies, Non-default synthetic transactions are tests that watcher nodes do not run by default. However, the watcher node can be enabled to run any of the Non-default synthetic transactions. You can do this when you create the watcher node (by using the New-CsWatcherNodeConfiguration cmdlet), or at any time after that. Many of the Non-default synthetic transactions require extra setup steps. For details, see Special setup instructions for synthetic transactions in Lync Server 2013.
Extended. Extended tests are a special type of Non-default synthetic transaction. Unlike other synthetic transactions, Extended tests can be run multiple times during each pass. This can be useful when verifying behavior such as multiple public switched telephone network (PSTN) voice routes for a pool. This can be configured simply by adding multiple instances of an Extended test to a watcher node.
For details about the process of adding other synthetic transactions to a watcher node, see Managing watcher nodes in Lync Server 2013. You can use the Lync Server Management Shell to remove synthetic transactions from a watcher node.
The synthetic transactions available to watcher nodes include the following:
| Cmdlet Name (Test Name) | Description | Synthetic Transaction Type |
|---|---|---|
Test-CsAddressBookService (ABS) |
Confirms that users are able to look up users that aren’t in their contact list. |
Default |
Test-CsAddressBookWebQuery (ABWQ) |
Confirms that users are able to look up users that aren’t in their contact list via HTTP. |
Default |
Test-CsIM (IM) |
Confirms that users are able to send peer-to-peer instant messages. |
Default |
Test-CsP2PAV (P2PAV) |
Confirms that users are able to place peer-to-peer audio calls (signaling only). |
Default |
Test-CsPresence (Presence) |
Confirms that users are able to view other users’ presence. |
Default |
Test-CsRegistration (Registration) |
Confirms that users are able sign in to Lync. |
Default |
Test-CsAudioConferencingProvider (ACP) |
Not used with the on-premises version of Lync Server 2013 |
Extended |
Test-CsPstnPeerToPeerCall (PSTN) |
Confirms that users are able to place and receive calls with people outside of the enterprise (PSTN numbers). |
Non-default, Extended |
Test-CsAVConference (AvConference) |
Confirms that users are able to create and participate in an audio/video conference. |
Default |
Test-CsAVEdgeConnectivity (AVEdgeConnectivity) |
Confirms that the A/V Edge servers are able to accept connections for peer-to-peer calls and conference calls. |
Non-default |
Test-CsDataConference (DataConference) |
Confirms that users can participate in a data collaboration conference, an online meeting that includes activities such as whiteboards and polls. |
Non-default |
Test-CsExumConnectivity (ExumConnectivity) |
Confirms that a user can connect to Exchange Unified Messaging (UM). |
Non-default |
Test-CsGroupIM (GroupIM) |
Confirms that users are able to send instant messages in conferences and participate in instant message conversations with three or more people. |
Default |
Test-CsGroupIM –TestJoinLauncher (JoinLauncher) |
Confirms that users are able to create and join scheduled meetings via a web address link. |
Non-default |
Test-CsMCXP2PIM (MCXP2PIM) |
Confirms that mobile device users are able to register and send instant messages. |
Non-default |
Test-CsPersistentChatMessage (PersistentChatMessage) |
Confirms that users can exchange messages by using the Persistent Chat service. |
Non-default |
Test-CsUnifiedContactStore (UnifiedContactStore) |
Confirms that a user's contacts can be accessed through the unified contact store. The unified contact store provides a way for users to maintain a single set of contacts that can be accessed by using Lync 2013, Outlook, and/or Outlook Web Access. |
Non-default |
Test-CsXmppIM (XmppIM) |
Confirms that an instant message can be sent across the XMPP (Extensible Messaging and Presence Protocol) gateway. |
Non-default |
You do not need to install watcher nodes in order to use System Center Operations Manager. If you do not install these nodes, you can still get real-time alerts from Lync Server 2013 components when an issue occurs. (The Component and User Management Pack does not use watcher nodes.) However, watcher nodes are required if you want to monitor end-to-end scenarios by using the Active Monitoring Management pack.
Note
Administrators can also run synthetic transactions manually, without needing to use, or install, Operations Manager. For details about the various Test-Cs cmdlets, see the Lync Server 2013 cmdlets index.
Depending on the size of your deployment, synthetic transactions may use a large amount of computer memory and processor time. For this reason, we recommend that you use a dedicated computer as a watcher node. For example, you should not configure a Front End Server to act as a watcher node. Watcher nodes should meet the following hardware specifications:
Note
A legacy Microsoft Lync Server 2010 watcher node cannot be collocated on the same machine with a Lync Server 2013 watcher node. This is because the core system files for Lync Server 2010 and Lync Server 2013 cannot be installed on the same computer.
However, Lync Server 2013 watcher nodes can simultaneously monitor both Lync Server 2013 and Lync Server 2010. The Default synthetic transactions are supported on both product versions.
Lync Server 2013 watcher nodes may be deployed inside or outside of an enterprise to help verify:
Connectivity to pools for users inside the enterprise.
Connectivity through perimeter networks for remote users who work outside the enterprise.
Connectivity to branch office appliances.
Connectivity to Lync Server 2010 inside the enterprise and through perimeter networks.
Different authentication options are available for inside and outside of the enterprise to help simplify administration. For details, see Configuring a watcher node to run synthetic transactions in Lync Server 2013.
To configure a computer to act as a watcher node, you must complete the following steps after you have installed System Center Operations Manager and imported the Lync Server 2013 management packs.
Before you install the Lync Server 2013 core files and the System Center agent files, you should also make sure that the watcher node computer meets all the prerequisites for installing Lync Server 2013. In addition, the watcher node computer should also have the following items installed:
| Hardware component | Minimum requirement |
|---|---|
CPU |
One of the following:
|
Memory |
8 GB |
Network operating system |
|
The full version of .NET Framework 4.5.
Windows Identity Foundation.
Windows PowerShell 3.0.
As soon as all these prerequisites have been met, you can configure the watcher node by:
Installing the Lync Server 2013 core files on the watcher node computer.
Installing System Center Operations Manager agent on the watcher node computer.
Running the Watchernode.msi executable file.
Using the CsWatcherNodeConfiguration cmdlets to configure test users to be employed by the watcher node.