|
The information below provides installation guidance, known issues and troubleshooting tips for the Audit Collection Admin. This page is updated on a regular basis as new information becomes available.
This page was last updated on 12/15/2008.
The Audit Collection Admin consists of two components, a Server component which runs the data discovery processes and a Client which provides the console resources.
This must be installed on the ACS Collector running Operations Manager 2007 SP1 and Audit Collection Services.
Requirements
- Operations Manager SP1 and ACS must be installed and running.
- SecureVantage.Security.Base.Library.mp version 3.0.6500.0 or higher must be installed on RMS.
- Service Account with respective rights:
- ACS Audit Database: Read access, Create/Delete Tables and Stored Procedures
- Operations Manager Database: Read access
- Installation must be run on each ACS Collector, Admin Service must be manually started after each installation.
Supported Configurations
- 32bit and 64bit Operating Systems and/or SQL
- Single Collector, local and remote databases
- Multiple Collectors, local and remote databases
- Cluster Configurations
Unsupported Configurations
- Windows Server 2008
- SCOM web console access
- Multiple Audit Databases on single SQL Server, with 1 or more instances
Notes
- Beta Testers: Beta must be uninstalled prior to installing RC
This can be installed on the Management Server or any client machine with the Operations Console installed.
Requirements
- Audit Collection Admin - Service must installed and started properly on ACS Collector(s) in the management group.
- Operations Manager client must be installed on loca machine.
- Windows XP or Windows Server 2003
Notes
- Beta Testers: Beta must be uninstalled prior to installing RC
If you have any questions, comments, or issues, please contact us at support@securevantage.com and please help us out by referencing the product name and version number on your machine.
|
|
|
|