What are the release notes for VigilEnt Security Agent for SQL Server 1.0? (NETIQKB24907)

  • 7724907
  • 02-Feb-2007
  • 08-Sep-2008

Resolution

goal
What are the release notes for VigilEnt Security Agent for SQL Server 1.0?

fact
VigilEnt Security Agent for Microsoft SQL Server 1.0

fix

Updating Previous Builds

If you are currently running a pre-release of this software (any build dated before August 8, 2002), you must obtain and implement VigilEnt Security Agent for Microsoft SQL Server Pre-release Patch from Technical Support.


Notes about the installation

When you install VigilEnt Security Agent for Microsoft SQL Server (VSA for SQL Server), the following services are created:

  • VigilEnt Security Manager DB Agent Service ? This service provides a communication interface between VigilEnt Security Agent for SQL.
  • Server and VigilEnt Security Manager ? VigilEnt Security Manager
  • Notification Agent Service ? This service lets you send alerts to selected personnel, or to the VigilEnt Security Manager console. This service is not created in the minimal install.
  • The installation also creates a Microsoft SQL Server login named, sqlcqr_vsm_agent.


Special Requirements for the SQLCQR_VSM_AGENT user

To run reports on a Microsoft SQL Server, the sqlcqr_vsm_agent login must have one of the following:

  • The system administrator role over the SQL Server where you want to run the report
  • A user account on the database where you want to run the report

Note: The sqlcqr_vsm_agent login must have the System Administrator role to run the ?Users without a Password? Common report and the ?sa with Null Password? Check-up report.

To perform actions on a Microsoft SQL Server, the sqlcqr_vsm_agent user must have one of the following:

  • The system administrator role over the SQL Server where you want to perform the action.
  • The db_owner role on the database where you want to perform the action.


Non-Applicable Reports and Actions

Due to the design of Microsoft SQL Server, the following VigilEnt Security Manager Common reports are not compatible with VigilEnt Security Agent for SQL Server:

  • Space Used by Owner
  • Disabled Users
  • Group List
  • Group Membership Summary
  • Groups User is a Member of Groups with No Users
  • Powerful Groups
  • User Last Access Date
  • User Password Last Change Date
  • Users in a Group
  • Users not a Member of Any Group
  • Users not Logged on Within X Days
  • Users with Expired Passwords
  • Users with Password = Username
  • Users with Weak Passwords

Due to the design of Microsoft SQL Server, the following VigilEnt Security Manager Common actions are not compatible with VigilEnt Security Agent for SQL Server:

  • Enable User
  • Disable User
  • Expire User Password
  • Unexpire User Password

Note: The ?Change User Properties? action only lets you change a login?s password. You cannot change the status of this account with VigilEnt Security Agent for SQL Server.


Icon Display issue in VigilEnt Security Manager

Upon start-up of the VigilEnt Security Manager console, a SQL Server icon may erroneously display a database server as unavailable when in actuality it is. You can verify the status of your SQL Servers by executing a heartbeat check or by performing tasks on them.

Additional Information

Formerly known as NETIQKB24907

Feedback service temporarily unavailable. For content questions or problems, please contact Support.