Chatta subito con l'assistenza
Chat con il supporto

Change Auditor 7.4 - 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

Example deployment scenario

The following diagram shows two separate forests where Change Auditor will be deployed. Forest A is deployed first and then Forest B is added.

Forest A installation
1
Install the coordinator on a member server in Forest A. In this example, Coordinator.ForestA.com is used as the coordinator server.
While installing the first coordinator, make note of the “Installation name”. The same installation name is required when deploying agents to Forest B.
2
Install the client on either a workstation or member server. In this example, CAClient1.ForestA.com is used as the client computer.
3
Using the client, connect to the coordinator in Forest A to deploy agents to computers in Forest A. See Deploy Change Auditor Agents for more details about deploying agents.
At this point, Change Auditor should be fully deployed to the first forest in the organization (ForestA.com in this example).
Forest B installation

Option 1: Deploying agents to a foreign forest through the Change Auditor client

1
Using the client, connect to the coordinator in Forest A.
2
Deploy agents to the required computers in Forest B. (See Deploying agents to a foreign forest for details.)

Option 2: Installing agents manually in a foreign forest

1
Run the appropriate Agent MSI on the required computers in Forest B where the installation is required. The MSI should be launched from an elevated command prompt.
2
When prompted, select the This agent connects to a coordinator in a foreign forest option.
3
Enter the Active Directory root domain name of the remote forest where the agent will connect.
4
Enter a domain administrator account for the coordinator domain and click Next. Ensure that you use the following format: fully-qualified-domain-name\user.
5
Enter the Installation Name that the agent needs to join and click Next.
6
Click Install.
The agent will now connect to the coordinator in Forest A and the computer will be available in the Deployment tab of the Change Auditor client.

 

Workstation Agent Deployment

Workstation agents are required to capture login activity events when a Change Auditor for Logon Activity Workstation license is applied. This section provides recommendations for deploying agents necessary for auditing both domain workstations and non-domain workstations. It also includes instructions on manually deploying workstation agents.

•
Recommendations and deployment requirements
•
Manual workstation agent deployment
•
Deploying workgroup agents (non-domain workstations)

 

Recommendations and deployment requirements

All workstation agents
•
See the Release Notes for a full list of the minimum system requirements for workstation agents.
•
Quest recommends a phased approach to deploying workstation agents. Deploying a maximum of 100 workstation agents at a time allows you to monitor the coordinator performance before deploying another batch of agents
Deploying workstation agents (domain workstations)
•
The recommended installation is from the Deployment tab of the client. See Change Auditor agents.
•
Alternately, you can manually deploy workstation agents. See Manual workstation agent deployment.
Deploying foreign forest workstation agents (domain workstations)
•
The recommended installation is from the Deployment tab of the client. See Deploying foreign forest agents.
•
Alternately, you can manually deploy workstation agents. See Manual workstation agent deployment.

Manual workstation agent deployment

When installed manually, the workstation agent installer must be run as an account with the local administrator account privileges and with elevated User Account Control (UAC) permissions.

* 
NOTE: Depending on the UAC policies (see User Account Control (UAC) Settings), elevated UAC permissions may require starting the installer using one of the following methods:
•
Shift + Right-click installer to select ‘Run as a different user’
•
From the Windows Task Manager, select File | Run New Task, browse and select the Change Auditor Workstation Agent installer file, and select the ‘Create this task with administrative privileges’ option, then click OK.
To manually install a workstation agent:
1
Copy the appropriate agent installer package from the Change Auditor service installation directory to the workstation to monitor. The default directory is %ProgramFiles%\Quest\ChangeAuditor\Service\Change Auditor Workstation Agent (x64).msi.
2
Run the installer file on the workstation to open the Workstation Agent Setup wizard which steps you through the installation.
3
If the computer is member of the local forest where coordinator resides, select This agent connects to a coordinator in the local forest. If the computer is a workgroup member or member of a foreign forest where no coordinator resides, select This agent connects to a coordinator in a foreign forest. For more information see Installing agents in a foreign forest.
4
The Installation Name screen prompts you to enter the installation name to identify the database where the coordinator is located. Click Browse to select the required installation.
5
Choose the destination folder and click Next.
6
Click Next to begin the installation.
User Account Control (UAC) Settings
•
UAC policies typically use different settings for the ‘Administrator’ account and other accounts with Administrative privileges, so it may be easier to run the Change Auditor Workstation Agent installer with elevated UAC permissions if the Administrator account is used.
•
General UAC elevation and prompt level configurations can be accessed through the Control Panel User Access Control configuration.

•
More specific UAC policies can be configured in the Local Security Policy or a Group Policy Object (where appropriate) to determine whether all Administrators or the built-in Administrator account are run in Admin Approval Mode, the elevation prompt level, whether the secure desktop is used for prompting, whether elevation is possible without prompting, and so forth.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione