- Pentium® II 450 MHz
- 256 MB RAM
- 300 MB of free disk space
- SVGA monitor that supports 256 colors with the display set to 800 x 600 pixels or greater
- Microsoft® Windows® 2000 SP3 (server or workstation), Windows XP® Professional SP1, or Windows Server™ 2003 or later
- 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
- 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, or Microsoft SQL Server Desktop Engine (MSDE) v1.0 or 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
- Your SQL Server or MSDE must be properly secured in order for your BindView data to be protected. Please review the Microsoft SQL Server security guidelines from the following URLs:
- Users of Microsoft SQL Server 2000 and MSDE 2000 who have not installed SQL Server Service Pack 3 or later, or users of Microsoft SQL Server 7.0 who have not installed SP4 or later may have security vulnerabilities. Because BindView RMS utilizes SQL, we strongly recommend that you apply the proper updates to SQL Server and MSDE installations on machines hosting the BindView Information Server. Upgrading an existing BindView Information Server with the BindView RMS Console v8.00 upgrade will not upgrade your SQL Server or MSDE installation. For additional information about SQL Server and MSDE updates refer to Microsoft TechNet or contact BindView.
- You must have SQL Server or MSDE installed on a machine before you can install an Information Server on it. If you do not have SQL Server or MSDE installed on your machine, the BindView RMS setup program will allow you to install it.
- The language pack on your Windows 2000 server must be set to English. Details
- If your user name contains non-ASCII or Extended ASCII characters, before you install the Console or Information Server on a Windows 2000 machine, you must modify your System Properties. Details
- For SQL Server v7.0, we do not support renaming the SQL Server machine.
- If you install the Console or Information Server on a machine where Windows 2000 SP2 is installed, you must have the Microsoft Q304536 Hotfix installed on the machine also, or upgrade to Windows 2000 SP3. The Microsoft Q304536 Hotfix is included in the Microsoft Jet 4.0 SP6. You can review this Microsoft fix at the following URL: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q304536
- When you install the Console and Information Server you must have Windows Administrator rights to the machine. If the installation requires a reboot, you must log in again as the same user to complete the installation.
- To successfully use a bv-Control product, the product must be installed on both the Console and the Information Server machine. Details
- In specific cases, you may receive a DCOM access violation error when you attempt to open a Console installed with a remote Information Server. Details
- On the Choose Destination Location and Select Program Folder panels of the Infrastructure Setup install wizard, you cannot select a Destination Folder or Program Folder that contains non-ASCII or Extended ASCII characters.
- When installing only a Console on a machine, a user who is an administrator of the BindView Information Server and whose user ID has not been added to the BindView User Manager, can be added as a BindView Administrator. If you prefer that the user not be a BindView Administrator, their account can be created in the BindView User Manager and assigned to the BindView Console Users group prior to the user installing only a Console on a machine.
- If you install v8.00 of the BindView RMS Console and then install v7.1 of any bv-Control product, the installation of the v7.1 product will finish successfully, but the product will not appear in the BindView RMS Console. Version 8.00 of the BindView RMS Console is not compatible with earlier versions of bv-Control products. If this should happen, uninstall the v7.1 bv-Control product using the Windows Add/Remove Programs Control Panel and install the v8.00 version of the bv-Control product.
- You can use Windows 2000 Terminal Services or Windows XP Remote Desktop to install the BindView RMS Console and Information Server on a remote machine if the installation files are local to the machine or accessible via the UNC path. The BindView RMS Console installer must not be located on a mapped drive. If the installer is located on a mapped drive, the installation will fail.
- When installing on a Windows 2000 Server or Advanced Server machine that is a Domain Controller, you cannot install to any folder with a pathname longer than 70 characters.
- When using Microsoft SQL Server 2000, the BindView RMS Information Server can only use the default instance name for the SQL Server.
- The amount of space required to install the BindView RMS Console and Information Server is sometimes incorrectly displayed as 0 KB. This does not affect the installation if at least the minimum space in the System Requirements is available.
- You can upgrade from v7.20 SP3 or later of the BindView RMS Console and Information Server to v8.00 of the BindView RMS Console and Information Server. If you have an earlier version of the BindView RMS Console, please contact BindView Technical support for assistance in upgrading to this version.
- When you upgrade from v7.20 SP3 or later of the BindView RMS Console, all v7 BindView RMS Snap-in modules will be removed from the BindView RMS Console and will not be loaded. You must upgrade any installed snap-in modules separately to v8.00 or later . Please consult each v8.00 bv-Control product User Guide for information about upgrading that module.
- In specific cases, it is possible that the exporting process does not close when closing the BindView RMS Console. If this happens and you attempt to upgrade to v8.00, an error message will appear, indicating "Setup has detected a running instance of the BindView Information Server. Please stop all running queries and shut down all BindView RMS Consoles connected to this server before installing BindView RMS Console and Information Server." If this happens, use the Windows Task Manager to end the HandleExport.exe process or restart the machine that hosts the BindView RMS Console.
- When upgrading from v7.20 SP3 of the BindView RMS Console, the Console imports existing queries and task lists. If an error occurs when importing a task list, the queries that compose the task list may not be imported correctly. If this happens, you can manually re-import the task list from the /data/Shared/%machine name%/ directory on the BindView Information server and restart the BindView Information Server.
- When you migrate a domain user account to an Active Directory® domain, the Information Server user associated with the account will appear twice on the User Manager dialog when you open the Console after the migration. Details
- If you need to add multiple Domain users with identical Full Names, you must use the User Manager, accessed from the Normal View details pane on the Console. If you use the BindView RMS Console Configuration Wizard or the Add Users Wizard, you will not be able to successfully add Domain users with identical Full Names.
- If a Console is installed on a machine with a local Information Server, and if a user connects the local Console to a remote Information Server instead of to the local Information Server, the local Information Server cannot be used by any remote Console users.
- If the system date of the machine hosting the remote Information Server is earlier than the system date of the machine hosting a BindView RMS Console, the BindView RMS Console cannot connect to the remote Information Server. To connect the Console and remote Information Server, you must synchronize the dates on the remote Information Server and the Console, and then restart both machines.
- You cannot add other standalone Snap-ins to the .msc created by the BindView RMS Console installer. To use one Microsoft Management Console (MMC) to operate BindView RMS and other standalone Snap-ins, you must create a new .msc file. In addition, when using MMC 2.0 (included with Windows XP and Windows Server 2003), you cannot add the BindView RMS MMC Snap-in to an .msc file. Details
- The BindView RMS Console and Information Server check to ensure that the versions of the Console, the Information Server, and all bv-Control snap-ins installed on the Console and the Information Server are mutually compatible. If any incompatibilities are found, the console displays a dialog with the text in the \BindView\RMS\RMSInstallLocation.XML file. You can make changes to this text to match your environment and direct users to update packages for remote Consoles. The text in this file must use roman (ISO-8859-1) characters. Cyrillic, Japanese, and other multi-byte characters will not display correctly.
- When you connect the Console to a remote Information Server, the Pre-Defined folder will contain pre-defined queries for the bv-Control products installed on the remote Information Server machine, even if the bv-Control products are not currently added to the Console you are using. If a bv-Control product is not added to your Console, you will not be able to use the product's pre-defined queries, even though they appear in the Pre-Defined folder.
- If the Console and Information Server you use each reside on two separate machines with different time settings, the recorded start times will vary. The start time in the Task Status dialog reflects the time setting of the machine hosting the Console, and the start time in the dataset reflects the time setting of the machine hosting the Information Server.
- If a machine running Windows XP Professional with "Simple File Sharing" active hosts a BindView RMS Information Server, machines running the BindView RMS Console will not be able to connect to the BindView Information Server remotely. For remote BindView RMS Consoles to access the Information Server, Simple File Sharing must be disabled. Details
- Due to file size limitations set by Microsoft Word, you should only export a dataset as a Word for Windows document if the file size is less than 32 megabytes.
- Due to a Microsoft Office limitation, unattended exporting to an Excel (using OLE) file may fail depending on how Microsoft Office was installed on the Information Server machine. Details
- Exporting to a BindView Decision Support Center v3 file must either be an attended export or the export destination must be on the BindView Information Server machine. If the export is unattended and the destination is a machine other than the Information Server, the Task Status dialog will incorrectly report that the Export took place correctly.
- If the Console system date is older than the system date of the Information Server, licensing doesn't work properly and some queries may be unsuccessful. Details
- If you are using Windows 2000 SP3 and Internet Explorer 6.0 with no Service Pack installed, the Related Topics buttons in help topics will not appear.
- If the BindView RMS Console is hosted on a machine running Windows Server 2003, only users who are members of the Administrators group can create Schedules due to restrictions in Windows 2003 Server.
- To uninstall the Console, you must be a Windows Administrator. To uninstall the Information Server, you must be a Windows Administrator and a BindView Administrator. Details
- If you uninstall a v8.00 Console that is connected to a v8.00 Information Server, only the v8.00 Console is removed. However, a message may appear that states that the Information Server has been uninstalled also. You may disregard this message.
- When you uninstall the BindView RMS Console and Information Server, any bv-Control product folders in your \Program Files\BindView\RMS\Control folder will not be deleted. The bv-Control products in the folders will be removed, but the folders themselves will not be deleted, since you may have made manual additions to the contents. You may delete these folders manually if you choose.
- Upgraded to the latest version of the XML parser (Xerces.dll v2.6 and Xalan.dll v1.9).
- Improved handling of heavy loads and query execution by the BindView RMS Information Server.
- Improved scalability to enhance reliability in large installations.
- Created a tool that allows BindView Administrators to control the maximum amount of memory used by the Information Server's SQL Server.
- Improved performance of Baseline queries.
- Numerous improvements have been made to enhance stability and performance.
- Certain hotfixes released for the BindView RMS Console and Information Server v8.00 SP1 have been incorporated into this release.
- Enhanced disk file export.
- Added ability to run Task Lists in a user-specified sequence, with each task waiting until the prior task is complete before beginning.
- Enhanced detection of version mismatch between the versions of BindView RMS products installed on the machine hosting BindView RMS Console and the machine hosting the BindView RMS Information Server.
- ActiveAdmin can now be enabled on both a per user and per product basis. That is, some users can have no ActiveAdmin access, some in a subset of installed bv-Control products, and some in all installed bv-Control products.
- Numerous improvements have been made to enhance stability and performance.
- Certain hotfixes released for the BindView RMS Console and Information Server v8.00 have been incorporated into this release.
- Microsoft Windows NT 4.0 is no longer a supported platform for the BindView RMS Console or the BindView Information Server.
- This version of the BindView RMS Console and Information Server is not compatible with versions of bv-Control products earlier than v8.00. You must upgrade your bv-Control products at the same time you upgrade the BindView RMS Console and Information Server. This incompatibility is due to a change in the compiler used to generate BindView products.
- Added Multiple Product Installation capability to assist customers with upgrades and deployment of multiple bv-Control products.
- Removed the ability to export to Lotus® 1-2-3 format.
- Added the ability to define a custom message to display when a version incompatibility is detected between the BindView RMS Console and the BindView RMS Information Server.
- Corrected an error that prevented OLE export of Excel files to Exchange email servers if the export setup had an invalid disk file path set.
- Corrected an error that caused display of and modifications to the Credentials Database to be very slow if the BindView RMS Console Credentials Database contained a large number of credentials (250 or more entries).
- Corrected an error that caused scheduled execution of queries to fail after three or more days of continuous processing of scheduled queries.
- Corrected the following errors that could occur when exporting:
- When exporting to a Comma-Separated Value (CSV) file, the BindView RMS Console v7.30 and v7.30 SP1 can export field data to the incorrect column in the exported file. In addition, information in form fields is truncated. This error has been corrected, and CSV exports are processed correctly.
- When exporting to XML format the BindView RMS Console v7.30 SP1 fails to terminate the section of the file with a tag, making the XML file unusable. This error has been corrected.
- When exporting to a disk file and the target file already exists, the BindView RMS Console v7.30 SP1 did not prompt the user to replace the existing file with the new one. This error has been corrected, and the user will be prompted to replace existing files.
- When exporting to a Microsoft Excel file using OLE from the BindView RMS Console v7.30 SP1, it was not possible to export a form field beginning with a row of dashes. Excel would consider them to be part of a mathematical formula. In the BindView RMS Console v7.3 SP2, the dashes will be converted to underscore characters when exporting to Excel via OLE only.
- When exporting to Excel via OLE, an ambiguous error message would appear if Excel failed to start due to errors in the configuration of DCOM. This service pack replaces that error message with an unambiguous one. If an error appears indicating that your DCOM settings are not properly configured, please contact BindView technical support for assistance.
- When copying a Query, the original Query's historical data is no longer copied to the new Query. The new Query copy will generate its own set of historical data.
- Corrected an error that prevented the entry of numbers higher than 999 in the Record Count condition for Post Process Commands.
- Corrected an error that could cause exports to Novell GroupWise to fail when performed unattended.
- Corrected an error that prevented the "Is No" and "Is Not No" operators from matching records when used on descriptor Boolean fields.
- Corrected an error that prevented the Max Historical Runs setting from being saved properly.
- Added the ability to add the group "Everyone" to a query's security properties.
- Corrected a problem that caused an "Access Violation" error to appear when using ordinal value filters in the Filter Specification tab of the Query Builder dialog.
- Corrected an error that caused the results from the first Object Property Field in a query to appear in every Object Property Field in the query.
- Corrected an error that prevented certain BindView RapidFire Updates® from being processed correctly.
- Corrected an error that caused exports of fields with more than 32 KB of data to take up to several minutes per field.
- Corrected an error that caused an "Access Violation" error to occur when making changes to a Special Value used as a Filter Term in the Filter Specification tab of the Query Builder.
- Corrected an error which prevented changes to the "Table Name" to export to using the "SQL Server (Enhanced)" export format in the Export Setup dialog after the export was first configured.
- Updated handling of Unicode characters in all export types. Exports of foreign-language characters from reports are now greatly enhanced.
- Corrected an error that could occur when modifying existing credentials in a snap-in module's configuration wizard and then clicking the "Back" button to return to the credentials page in the wizard.
- Modified the About BindView RMS Console dialog to properly show which quickfixes are currently installed.
- Corrected an error that could cause automatic exports to Microsoft Excel from a task list post process command running on the BindView RMS Console machine to fail.
- Added the ability for snap-in modules to create custom filters for fields.
- Updated Task List "Run Program" post-process command to allow relative paths for the program to run. If the program to run is in the BindView\RMS\bin folder, only the relative path of the program from the \bin folder is required.
- Corrected an error in the way times were recorded when exporting to BindView DSC format or to the BindView Policy Compliance Center that could prevent the BindView Decision Support Center and BindView Policy Compliance Center from operating properly on computers whose time settings were not set to use the United States time and date format. When the Policy Compliance Center acquired the time information from the BindView Information Server, it would display a message reading "Error converting data type varchar to datetime."
- Query result sets exported in HTML (Enhanced) format now include the BindView logo in the exported file.
- If you created a baseline task list and added a large number of queries by clicking Add All, a message appeared in error indicating that "Data source in query binder
doesn't support baselining." This error has been corrected, and the incorrect message will not appear.
- The Enhanced SQL export format introduced in Hotfix CRB137628 could interfere with appending to existing SQL Exports. This has now been corrected.
- Previously, SQL Column names were truncated at 63 characters. SQL Exports now allow 128-character column names.
- If a field which required a descriptor was being used as the filter term for another field using the Another Field option in the Filter Term Definition dialog, the BindView RMS Query Builder would prompt for the descriptor but would fail to properly pass it to the Filter Term Definition dialog. This has now been corrected.
- Corrected a problem which could cause scheduled items to fail when the BindView RMS Console was not running, especially if the BindView RMS Console had never been run on the machine hosting the BindView Information Server.
- The HTML (Enhanced) export format included an "Errors" line even when no errors occurred. This has been changed, and the "Errors" line will only appear when errors occur.
- Corrected a problem that could prevent the BindView RMS Console from loading properly when a large query was started in the BindView RMS Console, the BindView RMS Console was closed while the query was running, and the Console was immediately reopened by the same user.
- Corrected an error that prevented Enhanced SQL Exports from being processed as part of a Task List's post process commands.
- Corrected an error that would improperly send information in queries in all uppercase to snap-in modules that were case-sensitive and were expecting mixed case or all lowercase.
- Corrected an error that could prevent operator information (Equal To, Greater Than, Less Than, and any other operator that compares two values) from being properly saved when used in a filter set to prompt the user for filter information when the query is run.
- Corrected an error that caused extra columns to be appended when exporting to Microsoft Excel 5.0, 7.0, and 8.0.
- Corrected an error that prevented changes to conditions in Post Process Commands for task lists if more than 999 records were in the current result set.
- Created a setting that allows snap-in modules to specify that items in the Scope page of the Query Builder are not sorted. The previous default was for all items to be sorted on the Scope Specification page in alphabetical order. This setting does not affect the appearance of any queries, only the way items appear on the Scope page of the Query Builder.
- Corrected an error that prevented Scheduled Tasks from completing properly if the BindView RMS Console used to create them was not running and the BindView RMS Console on the machine hosting the BindView Information Server had never been run.
- Change to SQL-based storage for Queries, Task Lists, Export Settings and Report Settings, for improved speed, reliability, and security of data. Everything previously stored in .bvd files is now stored in a SQL database.
- New "Create Schedule Wizard" enables running queries and task lists automatically without relying on a third-party product.
- The RMS Console and Information Server installation now uses the MSI installer.
- During upgrade installations, existing Pre-Defined reports are now backed up.
- Changes were made to the BVDXML utility used for importing and upgrading reports. All BVDXML activity is now logged to
\RMS\data\Report Items Import.log file.
- The BindView RMS Console now allows manual import of BVD files or folders of BVD files into the SQL database.
- The BindView RMS Console will now export as XML files any Queries, Task Lists, and Settings items created by the user.
- The BindView RMS Console now includes HTML content for Queries, Task Lists, and Setting objects. When you select an item in the Console tree, a description of the item's content and some basic operations will appear in the details pane in the Console window.
- The BindView RMS Console now includes an Exported Files Browser. The browser allows exploration of the pre-existing Personal and Shared folders on the hard disk.
- Exporting from a Task List now supports file name macros that can include Time, Date, Query name, Task List name, or other text.
- You may now add multiple queries to a single Task List in the same action.
- Task List Conditional Post-Process Commands can now run Post Process Commands based on the number of records returned by a query.
- Historical datasets can now be locked so that they will not be deleted automatically. This allows static Baselining in Task Lists.
- There have been minor changes to the user interface in the License Manager.
- New Enhanced HTML, XML and Enhanced SQL export formats have been added.
- Getting Started Guide - contains a high-level description on planning and deployment of the BindView RMS Console and Information Server, as well as evaluation scenarios and troubleshooting information.
- Online Help - contains information on how to use the product. You can access the Online Help by clicking the Help button in any dialog, by right-clicking an item and selecting Help from the action menu, or by pressing the F1 key.
The BindView RMS Console and Information Server are the principal infrastructure products of the BindView RMS product family. The BindView RMS Console (Console) is the primary user interface for bv-Control®products. The Console provides query, ActiveAdmin®, baseline, task list, chart, report, export, and scheduling features. The Information Server is the primary component for all BindView RMS product task processing and data storage.
The BindView RMS Console and Information Server product has minimum system requirements for installation and use. Before installing the BindView RMS Console and Information Server, ensure that your system meets these requirements:
We recommend that you review the following notes before using the BindView RMS Console and Information Server:
SQL Server/MSDE Security
Remote Information Servers
The following changes have been made in v8.00 Service Pack 2 of the BindView RMS Console and Information Server:
Your BindView product CD contains the following documentation:
Imported Document Id