Change Auditor 7.4 - User Guide


	NOTE: If User Account Control (UAC) is enabled, a confirmation dialog appears where you can authorize the Coordinator Configuration tool to use the required elevated rights.

Use the fields/options to enter the credentials to be used to access the designated SQL Server/instance as described below:

SQL server and instance

Enter the name or IP address of the SQL instance to be used. (i.e., <Server Name>\<Instance Name>). You can also click Browse to locate and select the SQL server and instance.


	NOTE: If your database is in a SQL AlwayOn Availability Group, specify the name of the availability group listener for the SQL Server name.

Name of database Catalog

This displays the name assigned to the Change Auditor database.

Connect using

Specify whether Windows authentication, Azure Active Directory authentication or SQL server authentication will be used when communicating with the SQL database instance. (The authentication method is set up when SQL is installed.)


	NOTE: Azure Active Directory authentication is only supported for SQL Managed Instances.

Depending on the authentication option selected, enter the appropriate user credentials.

•

Windows Authentication - this is selected by default and will use Windows authentication to access the database.

If you are using a group Managed Service Account:

•

The account must end with '$' and the password must be blank.

•

The domain should be entered in the Fully Qualified Domain Name format.

•

The Coordinator Configuration Tool must be run as the administrator. (Right-click and select Run as administrator.)

•

The coordinator host must be correctly configured to retrieve the managed password for the specified group Managed Service Account.

•

•

SQL Server Authentication - select this to use SQL Server authentication to access the database.

•

Azure Active Directory Authentication - select this to use Azure Active Directory authentication to access the database located on an Azure SQL Managed Instance.

Azure SQL Managed Instance:

•

For a private endpoint, specify the managed instance host name in the following format: MyHostName.dns_zone.database.windows.net

For private endpoint with default port, port specification is not explicitly required. For example: MyHostName.b1b2a3d4e5f7.database.windows.net

MyHostName.b1b2a3d4e5f7.database.windows.net,1433

•

For a public endpoint, specify the managed instance host name and port in the following format: MyHostName.public.dns_zone.database.windows.net,3342

For public endpoint, port specification is required. For example: MyHostName.public.b1b2a3d4e5f7.database.windows.net,3342

NOTE:

•

Azure SQL Managed Instance (PaaS) is supported using SQL authentication or Azure Active Directory Authentication with an encrypted connection. Windows authentication is not supported.

•

For an Azure SQL Managed Instance (PaaS), SQL authentication or Azure Active Directory authentication with an encrypted connection must be used.

•

Single User Mode is not supported during installation or upgrade when using Azure SQL Managed Instance. Ensure that all SQL connections to the Change Auditor database are closed before and during the upgrade.

•

Azure SQL Managed Instance (HA) high availability is supported using the read-write listener endpoint.

•

Performance may vary depending on network configuration, topology, and Azure SQL Managed Instance configuration.

Enter the user name for the account to be used to access the SQL server instance.

Password

Enter the password associated with the user account entered above.

Domain

Enter the domain name for the Windows account used to access the designated SQL server instance. (Only valid for Windows Authentication.)

Encrypt connection

Select to use SSL encryption for all data sent between the coordinator and the SQL server. To use this option, the SQL server must have a certificate installed and the format of the SQL server name specified must be an exact match to the name format used in the certificate (for example FQDN or NetBios).

Ports page

By default, Change Auditor dynamically assigns communication ports for each installed coordinator. However, using the Ports page of the Coordinator Configuration dialog, you can specify static SCP listening ports to be used to communicate with the coordinator.

If you upgraded from a 5.x installation where static ports were defined, these static ports are retained as part of the upgrade process. However, the Agent Port setting, which is used by 6.0 agents, is set to use a dynamic port. Check with your system administrator to determine whether this new connection should also be using a static port.

Enter the ports to use to communicate with the coordinator:


	NOTE: A zero (0) indicates that a dynamic port is being used. If you have set a static port and wish to use a dynamic port, change the port number back to 0.

Client Port

Enter the static port number to be used by the client to communicate with the coordinator.

Public SDK Port

Enter the static port number to be used by external applications to access the coordinator.

Agent Port

Enter the static port number to be used for communication between a agent and a coordinator.

Protection page

By default, Change Auditor stores the Active Directory and GPO protection templates in SQL. However, you can use the Protection page of the Coordinator Configuration dialog to store the Active Directory and GPO protection templates in Active Directory instead of SQL.

When you select to store your Active Directory and Group Policy protection templates in Active Directory, you can use the Security feature on the Active Directory Protection page or Group Policy Protection page to provide an additional layer of security. The additional setting is intended when you require tighter security ACLs on your Active Directory and GPO objects and templates (for example, the Change Auditor SQL database may not be fully secured by ChangeAuditor Administrators). For more information about setting this additional security on protected objects, see the Change Auditor for Active Directory User Guide.

Specify the appropriate option for storing Active Directory/GPO protection and ADAM (AD LDS) protection:

Store Active Directory/GPO protection in:

Select one of the following options:

•

SQL (default)

•

Store ADAM (AD LDS) protection in:

Select one of the following options:

•

SQL (default)

•

View coordinator status and statistics

To view coordinator status and statistics (Overview page):

Open the Overview page and if the Coordinator Status overview pane is not being displayed, click the arrow button on an overview pane and select one of the following commands:

•

Coordinator Status | Enterprise View

•

Coordinator Status | <domain>

This displays a pie chart depicting the current status of all the coordinators installed in either the entire enterprise or in a selected domain.

By default, this pane only includes installed coordinators in the pie chart. You can however, select the Show Uninstalled Coordinators check box to include uninstalled coordinators in the pie chart.

Double-clicking the pie chart displays the Coordinator Statistics page.

To view coordinator status/statistics (Coordinator Statistics page):

Open the Coordinator Statistics page.

Click Show Uninstalled Coordinators to include coordinators set as ‘uninstalled’. Click Hide Uninstalled Coordinators to exclude these coordinators from the display.

The values in the different event columns are links, which when selected will open up a new Search Results tab to display the related details for these events.

To view coordinator status/statistics on current coordinator only (coordinator system tray icon):

From the server where the coordinator is installed, right-click the coordinator system tray icon and select Coordinator Status.

This displays the Change Auditor Coordinator Status dialog with the status and statistics regarding the coordinator, database, agent connections and events and alerts.

Click OK to close this dialog.

Manage Change Auditor coordinators

To stop a coordinator:


	NOTE: You can use Action \| Agent Notifications to hide (or display) the desktop notifications that are displayed when these processes are performed.

From the server where the coordinator is installed, right-click the coordinator system tray icon and select Disable Coordinator.

On the confirmation dialog, click Yes to stop the coordinator service.

A message displays explaining that the coordinator is being stopped.

In addition, a desktop notification displays in the lower right-hand corner of your screen explaining that the selected coordinator is being disabled.

Once disabled, the coordinator system tray icon contains a red light indicating that the coordinator is disabled.

If you so choose, click Set Coordinator Uninstalled to flag the selected coordinator as ‘Uninstalled’.

Click Show Uninstalled Coordinators to include uninstalled coordinators in the Coordinator Statistics list. Click Hide Uninstalled Coordinators to exclude uninstalled coordinators from the display.

To start a coordinator:

•

From the server where the coordinator is installed, right-click the coordinator system tray icon and select Enable Coordinator.

A message displays explaining that the coordinator is being started.

In addition, a desktop notification is displayed in the lower right-hand corner of your screen explaining that the selected coordinator is being started.

Once restarted, the coordinator system tray icon no longer contains a red or yellow button indicating that the coordinator is now active.