Configuring a watcher node to run synthetic transactions in Lync Server 2013


Topic Last Modified: 2014-02-07

After the System Center agent files have been installed, you must next configure the watcher node itself. The steps you take to configure a watcher node will vary depending on whether your watcher node computer lies inside your perimeter network or outside your perimeter network.

When you configure a watcher node, you must also choose the type of authentication method to be employed by that node. Lync Server 2013 enables you to choose one of two authentication methods: Trusted Server or Credential Authentication. The differences between these two methods are outlined in the following table:

Configuration Description Locations Supported

Trusted Server

Uses a certificate to impersonate an internal server and bypass authentication challenges.

This is useful for administrators who would prefer to manage a single certificate instead of many user passwords on each watcher node.

Inside the enterprise.

Note that, with this method, the watcher node must be in the same domain as the pools being monitored. If the watcher node and the monitored pools are in different domains, use Credential Authentication instead.

Credential Authentication

Stores user names and passwords securely in Windows Credential Manager on each watcher node.

This mode requires more password management, but is the only option for watcher nodes located outside of the enterprise. These watcher nodes cannot be treated as an endpoint trusted for authentication.

Outside the enterprise.

Inside the enterprise.

You should also verify that your firewall has inbound rules for both MonitoringHost.exe and PowerShell.exe. If these processes are blocked by the firewall then your synthetic transactions will fail with a 504 (server timeout) error.