Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Change Auditor 7.2 - Installation Guide

Installation Overview Install Change Auditor Add Users to Change Auditor Security Groups Connecting to the Clients Deploy Change Auditor Agents Upgrade Change Auditor Installation Notes and Best Practices Deployment Options Workstation Agent Deployment Agent Comparison Install an agent to audit ADAM (AD LDS) on workgroup servers Windows Installer Command Line Options

Pre-upgrade considerations

Review these special considerations before running an upgrade.

Coordinator upgrades

Coordinator upgrades may take longer than expected due to additions to the Changes Auditor database schema. The duration of the upgrade is dependent on the number of events generated in the last 45 days prior to the upgrade. The estimated time is approximately 1 minute for 1 million events.

Larger, more active environments should prepare for coordinator downtime of several hours during the upgrade process. You can view the upgrade progress in the coordinator logs or by connecting the upgraded client to the coordinator.

Upgrading a coordinator that is using Azure SQL Managed Instance for the database configuration

Single User Mode is not supported during installation or upgrade when using Azure SQL Managed Instance.

* 
NOTE: Do not open a connection to the SQL database while upgrading.

Upgrading a coordinator that is using SQL AlwaysOn Availability Groups for the database configuration

When upgrading Change Auditor databases that are part of a SQL AlwaysOn Availability Group, the upgrade can be performed while connected to the availability group listener. The upgrade will take place on the primary database and SQL will replicate any changes to the other databases in the availability group. Ensure that all SQL connections to the primary database are closed before and during the upgrade.

Services using Change Auditor SDK

Stop any services that use the Change Auditor SDK, such as Active Roles or GPOADmin, before starting the upgrade process.

Server collation differences

Starting with Change Auditor 6.0, on the coordinator startup the database collation is checked against SQL server collation. If they are different, the coordinator stops and logs the “Database collation differs from server collation” warning. If it is not possible to update collation of the SQL server, use the AllowCollationSwitch registry key to allow proceeding with rebuilding Change Auditor database according to the new collation. However, using this in environment with large number of events in the database significantly increases the load on SQL server. See the Change Auditor Technical Insight Guide for more information about setting this registry key.

Upgrading Change Auditor agents on high volume Exchange servers

It is critical that Change Auditor for Exchange agent upgrades be scheduled for maintenance intervals or other periods of low user mailbox activity for any configuration of Exchange Server. Change Auditor for Exchange agent upgrades should not be attempted on an active Exchange Server cluster node in any case. Attempting to upgrade the agent on a busy Exchange Server may result in:

•
Exchange 2013 mailbox role: failed agent upgrade, unwanted RpcClientAccess service restart, or unscheduled Exchange cluster node failover
•
Exchange 2013 client access role: unwanted IIS Exchange application pool restarts.

To eliminate the possibility of unscheduled Exchange Server downtime, perform agent upgrades to Exchange Servers during periods of low or no mailbox activity. When upgrading agents on busy Exchange Servers, it is also recommended that you manually stop the agent before upgrading to avoid a possible timeout on the stop command. Verify that the Change Auditor agent service is stopped on the Exchange Server before proceeding with the agent upgrade.

Alert Configuration (Evaluation Frequency)

This setting is no longer available. If you want to reduce the amount of email produced from alert-enabled searches, you must set the "AlertScanPeriod" registry key setting on the coordinator computer:

HKLM\SOFTWARE\Quest\ChangeAuditor\Coordinator

Value: AlertScanPeriod
Type: DWORD
Default value: 60 seconds
Description: Specifies the time interval between generating alerts.

Upgrade Change Auditor

To ensure success, upgrade the Change Auditor components in the following order:

•
Step 1: Upgrade all coordinators (and database schema)
•
Step 2: Upgrade all clients
•
Step 3: Upgrade the agents

Step 1: Upgrade all coordinators (and database schema)

During an upgrade of the first coordinator, the Change Auditor database is upgraded. Before proceeding with the coordinator upgrade, backup the database.

* 
NOTE: Change Auditor 7.0 and above requires a new license for all modules.
* 
IMPORTANT: As of Change Auditor version 7.0.4, Microsoft Graph API permissions are required for the web application to audit Azure Active Directory. and Office 365. Due to this, any existing Azure Active Directory and Office 365 templates must be updated.

Azure Active Directory and Office 365 auditing will not occur if the permission requirements are not met.

See the Office 365 and Azure Active Directory auditing User Guide for details on updating the templates and the required permission.
To upgrade all coordinators (and database schema):
1
Stop all coordinators.
2
Log on to the coordinator server to upgrade and run the autorun.exe file.
3
On the Install page, click Install for the Install Change Auditor Coordinator option to invoke the Coordinator Setup wizard.
4
Follow the Change Auditor Coordinator Setup wizard.
5
After the Change Auditor Coordinator Setup wizard has successfully finished, wait until the coordinator goes from an ‘Initializing’ status to a ‘Running’ status. To determine the coordinator’s status, right-click the Change Auditor coordinator system tray icon and select the Coordinator Status option.
6
Continue to upgrade the remaining coordinators one at a time following steps 2 to 4.

Step 2: Upgrade all clients

Step 2: Upgrade all clients
To upgrade a client:
1
From a workstation, laptop, or member server, run the autorun.exe file.
2
On the Install page, click Install for the Install Change Auditor Client option to start the Client Setup wizard.
3
Follow the Change Auditor Client Setup wizard.
See Install the client for more detailed information about the Client Setup wizard.
To upgrade a Change Auditor web client:
1
On the IIS server, run the autorun.exe file.
2
On the Install page, click Install for the Install Change Auditor Web Client option to start the Change Auditor Web Client Setup wizard.
3
Follow the Change Auditor Web Client Setup wizard.
See the Change Auditor Web Client User Guide for more detailed information about the Change Auditor Web Client Setup wizard.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation