Control Compliance Suite 8.60 Data Collectors March 2009 Cumulative Hotfix (CHF=6)

Article:TECH115609  |  Created: 2009-01-13  |  Updated: 2012-02-06  |  Article URL http://www.symantec.com/docs/TECH115609
Article Type
Technical Solution


Issue



What steps are required to apply the March 2009 Cumalative Hot Fix?


Symptoms
 

Issues fixed in RMS Console and Information Server

This Hotfix addresses the following issues:

While exporting the data set report, the %Date% setting does not take the
regional settings into account while creating the name of the exported file.
This Hotfix corrects this issue and now the regional settings are taken into
account while creating the name of the exported file.

When you modify the Export Grid Post process Command in an existing Task
list, the export Setup dialog box appears. When you choose an export format
the Choose Export dialog box appears. In this dialog box, the default format
is always displayed as Acrobat Format (PDF). This Hotfix corrects this issue
and now the formerly selected export format is displayed.


You are not able to export unattendedRMSquery to virtual share. For example,
Windows Share Point Services. This Hotfix corrects this issue and now you
are able to export unattended RMS query to virtual share successfully.

Issues fixed in bv-Control for Microsoft Exchange
This Hotfix addresses the following issues:

It was not possible to report on more than 64 thousand public folders. This
Hotfix corrects this issue and you can now report on more than 64 thousand
public folders.


Issues fixed in bv-Control for Windows
This Hotfix addresses the following issues:


The CreateScopeFile command line utility gave run time error and did not
create the scope files successfully. This Hotfix corrects this error and the utility
now creates the scope file successfully.

During the data collection on the Machines data source, the field "Machine-
Date/Time" reported incorrect time with a difference of one hour. This
happened when the "Automatically adjust clock for daylight saving changes"
option on the Query Engine was checked. This Hotfix corrects this error and
the time is now reported correctly even if the "Automatically adjust clock for
daylight saving changes" option is checked.
This fix affects the following data sources and fields:

Machines                         Machine- Date / Time


Event Log (Security)             Event Date/Time


The data import jobs failed with an error "Unable to query active directory
attribute," if a specific Domain Controller was queried. This Hotfix corrects
this error and the data import jobs now run successfully for specific Domain
Controllers.

Issues fixed in bv-Control for UNIX
This Hotfix addresses the following issues:


A data import job on the agentless target computers of Sun Solaris 5.10 would
modify the date and time stamp of other UNIX files. This Hotfix resolves the
issue and now a data import job does not modify the date and time stamp of
any other UNIX files.

It was not possible to block the fields of the Users data source for all the users
using Exception Rules option. This Hotfix corrects the error. You can now
block the fields for all users through the ExceptionRules.ini or the
ExceptionRules.dat file.

The query reports of the fields, MAC Addresses and IP Interfaces of the
Machines data source would mismatch when executed on the target computers
of Sun Solaris 5.9. This Hotfix resolves the issue for all the UNIX operating
systems and the IP Interfaces for which no MAC address is determined now
reports a value, N/A.

The Search option of the Composite File Descriptor that is used to extract
information from all the directories of a folder would throw an exception. This
Hotfix resolves the issue and the Search option does not throw any exception
during the search operation.

Queries of the Packages data source would fail on the HP-UX target computers
if the package version was empty. This Hotfix resolves the issue and a default
value is reported for the queries of the Package data source for the HP-UX
package version.

Query reports for the field, Login: Last Date/Time of the Users data source
would return a value, Never as the last login date for all the users. This issue
would report on the target computers of HP-UX 11.31 version. This Hotfix
resolves the issues and the file to extract the last login information is changed
from var/adm/wtmp to /var/adm/wtmps.

Issues fixed in bv-Control for Oracle
This Hotfix addresses the following issues:


The checks of an oracle server, when executed, reports on servers that have
non-registered SIDs. This Hotfix resolves the issue. To enable reporting only
on a registered SID, navigate to the registry key,
HKEY_LOCAL_MACHINE\SOFTWARE\BindView\bv-Control for Oracle and
set DWORD ReportDataForRegisteredSIDs to 1.

The ORCL_LISTENERS table is populated invalidly with the ORACLE_HOME
values from the oratab file. This Hotfix resolves the issue. The
ORCL_LISTENERS now contains valid populated data with theORACLE_HOME
values of the oratab file.

The following error would display when a query of the Database data source
was executed:

"Unable to establish connection with the databaseORA06413: Connection not
open"

This Hotfix corrects the error and no exception is thrown when the query is
executed.


Issues fixed in bv-Control for NetWare
This Hotfix addresses the following issue:


The following error is thrown when the predefined queries of the folder,
\Pre-Defined\bv-Control for Netware\Storage Analysis\File\ are executed:
"Unknown field in query engine code error 0 in subsytem bvroot subsystem."
This Hotfix corrects the error and no error is thrown on executing the
predefined queries.



 


Solution



Below is a list of March 2009 updates that need to be applied and the order they are recommended to be applied;
It is strongly recommended that the readme notes are read before applying the updates,quickfixes or hotfixes:

Data Collection:

March. 2009 CHF:

ftp://ftp.symantec.com/public/english_us_canada/products/symantec_control_compli
ance_suite/8.6/updates/data_collectors/CCS_DataCollectors_8.60_March_2009_Up
date.exe

Readme:

ftp://ftp.symantec.com/public/english_us_canada/products/symantec_control_compli
ance_suite/8.6/updates/data_collectors/ReadMe_CCS_DataCollectors_8.60_March_
2009_Update.pdf

After applying the Sept update you must remember to update all your Query Engines;

Please referance the directions on how to update the Query Engines in the following KB article;

*Title
How to upgrade query engines in Control Compliance Suite (CCS) to the latest cumulative hotfix (CHF)

Published Externally
http://www.symantec.com/docs/TECH113542

Symantec_WIN_860_HF_WQN1531816.exe


After updating all the query Engines run a Health and Status Check to verify the updates have been applied sucessfully through out your environment:


Please referance the directions on how to run a Health and Status Check in the following KB article;

*Title
How to run a Health & Status Check for Control Compliance Suite (CCS) Data Collection.

Published ExternallyPublished Externally
http://service1.symantec.com/support/intrusiondetectkb.nsf/docid/2008051616333053

Verify that CHF=6 on BVIS as well as all Query Engines

After verifying your environment has been sucessfully updated to CHF=6. The next step would be ;


Please referance the directions on how to run a update Patch Assessment meta documents in the following KB article;

*Title
How to update Patch Assessment meta documents in Control Compliance Suite (CCS) for Windows Managed Server

Published Externally
http://service1.symantec.com/support/intrusiondetectkb.nsf/docid/2007100417170153

The next step would be to apply the;

CCS_DataCollectors_8.60_March_2009_Update

to all your Remote RMS 8.6 Consoles;





 



Legacy ID



2009041315134453


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


Terms of use for this information are found in Legal Notices