Page History

...

1. After installing the cluster agent service on all Listener nodes, open Server Manager.
2. In the Server Manager tree, click Server Manager > Features > Failover Cluster Manager. The system displays Failover Cluster Manager.
3. Select the cluster service group created for the cluster agent service. In the following example, AGroup001 is the cluster service group.
   
4. In the Server Name area, select the resource name of the cluster service group, and then click Properties in the Actions panel. In the following example, aoaglistener is the resource name. Failover Cluster Manager displays the Properties window. Click the Dependencies tab.
   
5. Verify that the Resource field displays the listener IP address.
6. In the Other Resources area of the Failover Cluster Manager window, select the resource of within the cluster service group, and then click select Properties in the Actions panel. In the following example, AGroup01 is the other resource name. Failover Cluster Manager displays the Properties window. Click the Dependencies tab.
   
7. Verify that the Resource field displays the listener name. Click Cancel to close this window.
8. After adding the resource information, right-click the cluster service group in the tree, and then select Add a resource > 4 - Generic Service. Failover Cluster Manager displays the New Resource Wizard to allow you to create the new resource.
9. In the Select Service page of the New Resource Wizard, select the cluster service agent from the available list. The cluster service names are displayed in the format SQLcomplianceAgent$[listener name] where [listener name] is a virtual SQL Server name. In the following example, SQLcomplianceAgent$AOAGLISTENER is the service name.
   Image Modified
10. Click Next, the New Resource Wizard displays the Confirmation window.
11. Verify that the displayed information is correct, and then click Next.
12. In the Configure Generic Service window, Failover Cluster Manager creates the new resource. Click Next.
13. In the Summary window, verify the information regarding the new resource, and then click Finish.
    Image Modified
14. In the Other Resources area of the Failover Cluster Manager window, select the SQLcomplianceAgent$[listener name] cluster service group, and then click Bring this resource online from the context menu. In the following example, SQLcomplianceAgent$AOAGLISTENER is the cluster service and is currently offline as noted in the Status column.
    
    Failover Cluster Manager bring the service online and displays the updated status, as shown in the following example.
    
15. The ‘SQLcomplianceAgent$[listener name]’ While the cluster service need to be online (see the screenshot below):

1. Select the ‘is online, select the SQLcomplianceAgent$[listener name]’ cluster service (in this case it is ‘SQLcomplianceAgent$AOAGLISTENER’) in the ‘Other Resources’ section. Left click the ‘Properties’ item cluster service, and then select Properties from the context menu. In the opened window, click the ‘Dependencies’ tab. Ensure the resource ‘Agroup01’ dependency is added (see the screenshot below):

1. Go to the ‘Registry Replication’ tab and click the ‘Add’ button. Specify ‘SOFTWARE\Idera\SQLcompliance’ registry key value. Press ‘OK’ button.

1. Press ‘OK’ button to close the ‘Properties’ of ‘SQLcomplianceAgent$[listener name]’ cluster service.

1. following example, SQLcomplianceAgent$AOAGLISTENER is the cluster service name. Failover Cluster Manager displays the Properties window.
2. Verify that the Agroup01 dependency is added, as shown in the following example.
   Image Added
3. On the Registry Replication tab, click Add. Failover Cluster Manager displays the Registry Key window.
4. Type SOFTWARE\Idera\SQLcompliance as the registry key value, and then click OK.
   Image Added
5. Close the Properties window by clicking OK.
6. Run SQLCM console application and open ‘Add Server’ wizard for [listener name] (virtual SQL server name, in this case ‘AOAGLISTENER’). Click ‘Next’ button.

...

The Listener scenario is recommended for users who want to audit only AlwaysOn databases on the Primary node using LISTENER. If you want to audit read-only Secondary nodes , use the Nodes scenario.