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 (Windows Server 2008) or the Role (Windows Server 2012 and later) created for the cluster agent service. 
4. In the Server Name area, right-click the resource name and click Properties. Failover Cluster Manager displays the Properties window. 
5. Click the Dependencies tab.
6. Verify that the Resource field displays the listener IP address.
7. In the Other Resources area of the Failover Cluster Manager window, right-click the the resource within the cluster service group or the role, and select Properties. Failover Cluster Manager displays the Properties window. 
8. Click the Dependencies tab.
9. Verify that the Resource field displays the listener name. Click Cancel to close this window.
10. After adding the resource information, right-click the Cluster Service Group (Windows Server 2008) or the Role (Windows Server 2012 and later) in the tree, and point to Add a resource.
11. Click on Generic Service. Failover Cluster Manager displays the New Resource Wizard.
12. In the Select Service page, 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. 
13. Click Next, continue following the wizard, and click Finish. 
14. In the Other Resources area of the Failover Cluster Manager window, right-click the SQLcomplianceAgent$[listener name], and Bring Online the resource. 
15. While the cluster service is online, right-click the SQLcomplianceAgent$[listener name] cluster service, and click Properties.
16. On the General tab verify that the Role is added.

17. On the Registry Replication tab, click Add. Failover Cluster Manager displays the Registry Key window.

    Note
    The Registry Replication tab is not available in Windows Server 2012. If you are using Windows Server 2012, you must use the "Add-ClusterCheckpoint" PowerShell cmdlet to add the necessary setting. For more information, see Add ClusterCheckpoint.

18. Type the specific registry path. To obtain the correct path, go to the IDERA Cluster Configuration Console and copy the Replicated Registry Key from the SQLcompliance Agent details.    
19. Click OK. The new root registry key appears in the Registry Replication tab of the Properties window, as shown in the following example.
20. Close the Properties window by clicking OK.

3. Add the Listener to SQL Compliance Manager

Use the following steps to add the listener to SQL Compliance Manager for auditing.

1. Start the IDERA SQL Compliance Manager Management Console and click New > Registered SQL Server. SQL Compliance Manager displays the SQLcm Configuration Wizard - Add Server.
2. In the SQL Server window, specify or browse the listener you want to register with SQL Compliance Manager, and click Next. 
3. In the SQL Server Cluster window, check This SQL Server instance is hosted by a Microsoft SQL Server Cluster virtual server box, and click Next. This step makes the listener into a virtual SQL Server name.
4. In the SQLcompliance Agent Deployment window, verify that the Manually Deploy is selected, and click Next. This option is required for all virtual SQL Servers.
5. In the Select Databases window, check the AlwaysOn database that you want to audit, and click Next.  
6. SQL Compliance Manager displays the AlwaysOn Availability Group Details window including a list of all nodes where the AlwaysOn database is replicated. Note that this window appears only if the database selected for auditing is AlwaysOn. The wizard skips this window for regular databases.
7. If the AlwaysOn Availability Group Details window is displayed, click Next to continue.
8. In the Audit Collection Level window, select the desired audit collection level for the database, and click Next.
9. In the Permissions Check window, SQL Compliance Manager verifies that all the required permissions are in place on the SQL Server instance you want to audit.
10. After all operations are complete and all permissions checks pass, click Next. The Summary window displays the audit settings for the SQL Server instance.
11. Click Finish to close the wizard. SQL Compliance Manager displays the newly-added SQL Server instance and AlwaysOn database in the Explore Activity tree.
12. Make all necessary audit settings for the listener and AlwaysOn databases, and then update the configuration and begin collecting data. It is recommended to update the configuration before collecting data because users are unaware of  which node is PRIMARY. After updating the configuration, be sure to click Refresh in the node context menu to apply the settings to the displayed information.

After configuration, review some Additional information