NOTE: If you have not added the appropriate user accounts to either the ChangeAuditor Administrators or ChangeAuditor Operators group, you are denied access to the coordinator when you open the client. See Add Users to Change Auditor Security Groups for more information about these security groups and SQL database roles. |
Quest recommends that you deploy a server agent to all servers (domain controllers and member servers) to track configuration changes in real time. For workstations, deploy a workstation agent to only those that you want to monitor for login activity. See Agent behavior notes for information about how the different types of agents connect to the coordinators in your environment and the limits set for agent connections.
NOTE: See the Installation Notes and Best Practices for notes on deploying agents for Change Auditor for Exchange and Change Auditor for Authentication Services. |
NOTE: The Deployment page does not display nonmember objects, such as ADAM workgroup servers or nondomain workstations, because agents cannot be deployed to non-member objects using the Deployment tab. See Install an agent to audit ADAM (AD LDS) on workgroup servers for more information about manually installing agents to workgroup servers. See Workstation Agent Deployment for more information about manually installing agents to non-domain workstations. |
IMPORTANT: Minimum permissions
The Agent Deployment wizard runs under the security context of the currently logged on user account. Therefore, you must have administrative authority to install software on every target computer. You must be a Domain Admin in every domain that contains servers that you are targeting for installation. If you are targeting domain controllers only, membership in the Enterprise Admins group grants you authority to all domain controllers in the forest. |
The following procedures step you through the process of deploying agents. See the Change Auditor User Guide for procedures on using the advanced options and setting up auto deployment of new servers.
1 |
Verify that the user account you are using to deploy agents is at least a Domain Admin in every domain that contains servers or workstations where agents will be deployed. |
3 |
Open the client. If agents have not yet been deployed, select the Deployment tab. Otherwise, use View | Deployment. |
4 |
From this list, select an entry and select Credentials | Set to enter the proper user credentials for installing agents on the selected domain. |
5 |
After entering the proper credentials, select the entry back on the Deployment page and select Credentials | Test. If you get a Valid Creds status in the Deployment Result column, you can start deploying agents to that domain. |
7 |
Select one or more servers or workstations on the Deployment page and click Install or Upgrade. |
• |
NOTE: To cancel a pending deployment task, select the server or workstation and then click Install or Upgrade. On the Install or Upgrade dialog, click Clear Pending. |
9 |
As agents are successfully connected to the coordinator, the corresponding Deployment Result cell displays ‘Success’, the Agent Status cell displays ‘Active’ and a desktop notification displays in the lower right-hand corner of your screen. |
You can upgrade to Change Auditor 7.0 from the following upgrade paths.
You cannot upgrade directly to version 7.0. You must upgrade to 6.8 first. |
Review these special considerations before running an upgrade.
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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center