The bv-Control for Unix product is no longer configured in Control Compliance Suite ( CCS ) for Data Collection.

Article:TECH114877  |  Created: 2008-01-03  |  Updated: 2012-12-05  |  Article URL http://www.symantec.com/docs/TECH114877
Article Type
Technical Solution

Product(s)

Issue



The bv-Control for Unix snapin was fully configured and functional. Then it appears as though it is no longer configured. How to get the configuration back without having to reconfigure each host individually?

Symptoms
The bv-Control for Unix snapin status indicates it is not configured. It was configured previous to the new status.


Cause



MMC failure resulted in closure of all running apps. After the customer booted the BVIS and opened the RMS console. The bv-Control for Unix snapin is no longer configured. The credentials appear to remain.


Solution



The bv-Control for Unix product continues to appear as though it is not- configured.

Close the RMS console

Backup the following files by renaming the files;
\Program Files\Common Files\BindView\bv-Control\UNIXShared\Database\Scoping.mdb to Scoping.mdb.org


copy and rename-> \Program Files\Symantec\RMS\Control\UNIX\Database\oldScoping.mdb to
\Program Files\Common Files\BindView\bv-Control\UNIXShared\Database\Scoping.mdb

Open RMS console and verify that the bv-Control for Unix snapin is configured and has servers configured. 



Legacy ID



2008100310341653


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


Terms of use for this information are found in Legal Notices