Release Notes - bv-Control® for Microsoft® SQL Server v8.10

Article:TECH113286  |  Created: 2006-01-14  |  Updated: 2010-09-02  |  Article URL http://www.symantec.com/docs/TECH113286
Article Type
Technical Solution


Issue





 


Solution



bv-Control® for Microsoft® SQL Server v8.10

BindView's bv-Control for Microsoft SQL Server application provides a security solution for the SQL Server enterprise. Using bv-Control for Microsoft SQL Server, security administrators and auditors can easily pinpoint database access permissions and review configuration and security analyses before users experience system downtime or security violations. This application provides full-featured, query-based capabilities allowing security administrators and auditors to easily build custom queries for issues specific to their SQL Server environments, and perform queries across multiple servers simultaneously.

System Requirements

The bv-Control for Microsoft SQL Server product has minimum system requirements for installation and use. Before installing bv-Control for Microsoft SQL Server, ensure that your system meets these requirements.

The following minimum requirements include the requirements for the BindView RMS® Console and Information Server:

RMS Console

· Pentium® II 450 MHz


    · 256 MB RAM

    · 300 MB of free disk space

    · Microsoft® Windows® 2000 SP3 (server or workstation), Windows XP® Professional SP1, or Windows Server™ 2003 or later

    · SVGA monitor that supports 256 colors with the display set to 800 x 600 pixels or greater

    · Microsoft® Internet Explorer v5.5 SP1 or later

    · Microsoft® Outlook® 2000, Novell® GroupWise® v5.5, Lotus Notes® v5.0 or Lotus Domino (only required for e-mailing export files)

    · Microsoft® Excel (required for Excel (using OLE) export files)

    · Client for Microsoft® Networks


Information Server

· Pentium III 800 MHz


    · 512 MB RAM

    · 500 MB of free disk space

    · Microsoft Windows 2000 SP3 (server or workstation), Windows XP Professional SP1, or Windows Server 2003 or later

    · Microsoft SQL Server v7.0 or 2000, Microsoft SQL Server Desktop Engine (MSDE) v1.0 or 2000, Microsoft SQL Server Standard Edition v7.0 or 2000, Microsoft SQL Server Enterprise Edition v7.0 or 2000, Microsoft SQL Server Personal Edition 2000, Microsoft SQL Server Developer Edition 2000

    · Microsoft Internet Explorer v5.5 SP1 or later

    · Microsoft Outlook 2000, Novell GroupWise v5.5, Lotus Notes v5.0 or Lotus Domino (only required for e-mailing export files)

    · Microsoft Excel (required for Excel (using OLE) export files)

    · Client for Microsoft Networks


You must have administrative rights to the computer that you will be using.

Pre-Installation Requirements

Before installation of bv-Control for Microsoft SQL Server v8.10, ensure that the BindView RMS Console and Information Server v8.00 or later, is installed.

Known Issues

We recommend that you review the following notes before using bv-Control for Microsoft SQL Server with the BindView RMS Console:

· Remote Desktop Installation


    When installing the bv-Control for Microsoft SQL Server snap-in on a remote machine using Microsoft’s Remote Desktop Connection (RDC), the installation might fail if you map to the drive of the machine containing the installation files and run setup.exe. A workaround for this problem is to connect to the machine (containing the installation files) using the UNC (Universal Naming Convention) format: \\Computer name\Share name\<Path to the setup.exe file> . Alternatively, you can copy the installation files on the remote machine where the snap-in must be installed, and then run setup.exe.

    · If the database name contains the character, single quote ('), then the reports for these database might fail for some data sources.

    · If a job is run multiple numbers of times and is subsequently modified, then the query reports incorrect values for the fields Last run date, Last run duration, Last run outcome, Last run retries, and Last run time in the Job Steps data source.

    · If you execute a query using Database Roles data source, the Partial Permissions field displays 'Unknown' even if column level permissions are assigned to the role.

    · If local SQL credentials have been specified for querying against a target, then group resolution of Windows groups is not performed, as no Windows credentials are available.

    · If a domain is specified in FQDN format in the credentials database using Add Domain Credential and is subsequently specified as an Advanced Scope through All SQL Sever Instances in Domain, then the query might not report any data.

    · For the msdb database, if you execute a query using the Database File data source, the File Growth field reports an incorrect value.

    · If a query is scoped to the default scope, the query might remain in an outstanding state for a significant amount of time.

    · The fields Password Equal To, Password Same As Login Name, and Password Found In File? in the Server Logins data source are supported for Microsoft SQL Server 2000 only.

    · If the password hashes are made available in a file for password analysis, the fields Password Empty?, Password Equal To, Password Last Changed, and Password Same As Login Name? in the Server Logins data source do not report correct values for server logins having a comma (,).

    · When adding licenses, you may receive the error message: 'License XXXX-XXXX is of unknown type. Do you wish to add?' Click Yes to add the license, and the program will continue to run normally.

    · After you have installed the Microsoft SQL Server Enterprise Manager, you will need to start the Microsoft SQL Server service before launching and using the bv-Control for Microsoft SQL Server application. If the Microsoft SQL Server service is not restarted, you will receive a critical failure message stating that the SQL server does not exist.

    · In this release, while creating a query, you cannot add 'All Servers' as a scope in the Query Builder. However, if you have a previously saved 'All Servers' in a named scope and have upgraded to bv-Control for Microsoft SQL Server v8.10, then the scope will continue to work through that named scope.

    · For querying a Microsoft SQL server installed on a Windows XP SP2 machine, only Windows Authentication is supported.

    · If you execute a query using the Servers data source, the IsClustered field displays 'Unknown' for Microsoft SQL Server v7.0.

    · For the Transaction Logs data source:


· For online transaction logs, the Transaction Summary field does not show correct old and new column values for the modify transactions on tables with clustered indices.

        · For online transaction logs, the Transaction Summary and Additional Information fields do not show old values and new values for the modify transactions on variable length table columns.

        · For online transaction logs, the Transaction Summary field only shows the modified characters in the new value and old value columns for the modify transactions on table columns of string data types.

        · The Transaction Summary field does not display values for table columns with user-defined data types.

        · For backup and offline transaction logs, the Transaction Summary and Additional Information fields will be empty.

        · For backup and offline transaction logs, if read permissions are denied on the transaction log file, the message 'No records matched the specified query' will be displayed.

        · For backup and offline transaction logs, the User Name, Object Name, and Index Name fields will be empty.

        · For offline transaction logs the Server Name field will be empty.

        · For transactions performed by Microsoft SQL Server, the UserId field value will be 65,536(-1). For backup and offline transaction logs, an incorrect value will be displayed.

· For fields requiring enumeration of Microsoft Windows group membership, if permissions are denied while enumerating group memberships, then the group name itself will be displayed in the members list.

Change History

The following is a summary of the change history of bv-Control for Microsoft SQL Server v8.10:

· Ability to provide Advanced Scopes


    · Ability to provide SQL Server General Query Credentials

    · Ability to perform Password Analysis on local SQL Server users

    · The following three new data sources have been introduced:


· Database Backups

        · Database Roles Permissions

        · Job Steps

· Default Scope modified


    · New pre-defined queries for NSA best practices have been introduced

    · Server Logins data source overhauled to improve query performance

    · Permission evidence fields have been introduced in the existing permission related pre-defined queries


For more information about what's new in this release, please refer to the "What's New in This Release" topic in the bv-Control for Microsoft SQL Server Online Help.

Documentation

Your BindView product CD contains the bv-Control for Microsoft SQL Server Getting Started Guide in Adobe® Acrobat®.

The Getting Started Guide contains information about installing and configuring bv-Control for Microsoft SQL Server.

 

© 2005 BindView Corporation. All rights reserved.

 




 



Legacy ID



2006081414061553


Article URL http://www.symantec.com/docs/TECH113286


Terms of use for this information are found in Legal Notices