Is the EventSentry agent cluster-aware? Can the EventSentry agent be installed on computers in Windows cluster?

Article ID: 98
Category: Installation
Applies to: 2.72 and newer
Updated: 2016-04-13

Yes, you can install the EventSentry service on cluster nodes by defining the EventSentry service as a cluster resource (service).

Please follow the instructions below (the instructions refer to Windows Server 2003 and newer) to install EventSentry in a cluster. For reference purposes, the following computer names will be used:

CLUSTER: Logical Node
CLUSTER1: First cluster node (physical)
CLUSTER2: Second cluster node (physical)

Step 1:
Add both of the physical nodes to the cluster (CLUSTER1, CLUSTER2) and Install the EventSentry service on both hosts, using the "Manage Agent(s) -> Install" option.

Step 2:
Using the Cluster Administrator, add a new resource of type Generic Service to your cluster group. Enter the following information on the screens in the wizard:

Screen 1: New Resource
Name: EventSentry
Description: EventSentry Service
Resource Type: Generic Service
Group: [Select a cluster group]

Screen 2: Possible Owners
Select both CLUSTER1 and CLUSTER2 as the possible owners of the resource.

Screen 3: Dependencies
You do not need to set dependencies.

Screen 4: Generic Service Parameters
Service Name: EventSentry
You do not need to set any start parameters.

Screen 5: Registry Replication
You do not need to specify a registry key here.

After pressing the FINISH button, the resource will be created. Now, right-click the resource and select Bring Online. This will start the EventSentry service on the active cluster node, for example CLUSTER1. The service should remain stopped on the passive node(s).

Step 3:
Using the "Services" MMC snap-in in "Administrative Tools", set the startup type of the EventSentry service on all cluster nodes to Manual, so that the cluster can manage the EventSentry service and ensure that only one instance of the EventSentry service is running at a time.

From now on, simply manage both cluster agents through remote update, that is, you should continue to push configuration updates and agent updates to both computers.

Remember that the service should only be running on one of the nodes at any given time, and the cluster should take care of that automatically since it is a cluster resource now.