Upgrading an existing CCS and RMS deployment to CCS 11.0

Article:HOWTO76902  |  Created: 2012-05-07  |  Updated: 2012-05-08  |  Article URL http://www.symantec.com/docs/HOWTO76902
Article Type
How To


Subject


Upgrading an existing CCS and RMS deployment to CCS 11.0

If you are using RMS to collect asset data, you can upgrade to CCS to benefit from the new and improved data collection features offered by CCS 11.0.

CCS 11.0 allows you to upgrade the BV-Control for UNIX Agents with the CCS Agents. However, it is recommended, that until you complete the upgrade and perform data collection from the new deployment for the first time, you should maintain a co-existence of the BV-Control for UNIX Agents and the CCS Agents. Later, once you are sure that you are able to collect data from the new CCS Agents, you can remove the BV-Control for UNIX Agents from the target computers, and upgrade the remaining BV-Control for UNIX Agents in your deployment.

Let us assume that your existing deployment is as displayed in the following diagram:

Figure: Example of existing CCS + RMS deployment

Example of existing CCS + RMS deployment

Site A has the CCS Reporting and Analytics components: CCS Application Server, CCS Directory Server, CCS Consoles and the databases. Site A also has a Data Processing Service (DPS) with the roles of Load Balancer and Data Collector, with an RMS information server collecting data from Windows targets using Query Engines, and also collecting data from SQL targets.

Similarly, Site B has a DPS with the role of Data Collector and an RMS information server collecting data from Windows targets in two domains ABC.com and PQR.com, and collecting data from UNIX targets using the BV-Control for UNIX agents, and also collecting data from Oracle targets.

Refer to the following diagram to upgrade the existing deployment to CCS 11.0:

Figure: Example of upgraded deployment to CCS 11.0

Example of upgraded deployment to CCS 11.0

In Site A, you can upgrade the CCS Reporting and Analytics components: CCS Application Server and CCS Directory Server to CCS 11.0. Upgrading the core components also upgrades the CCS Consoles. You can upgrade the DPS to CCS Manager with the roles of Load Balance and Data Collector. As the CCS Manager performs all the roles of the Data Processing Service and also provides built-in support to collect data directly from agent-less and agent-based target computers, the RMS Information Server, Enterprise Configuration Service (ECS) and the Master Query Engine (MQE) components are no longer required. You can configure the CCS Manager to collect data directly from the Windows and SQL targets.

In Site B, you can upgrade the DPS to CCS Manager with the role of Data Collector. The CCS Manager can collect data directly from the target computer. As displayed in the diagram if the CCS Manager is in the domain ABC.com, ensure that there is a domain trust relationship between domains ABC.com and PQR.com, for the CCS Manager to collect data from targets in the domain PQR.com. Upgrade the BV-Control for UNIX agents to CCS Agents and configure the CCS Manager to collect data directly from the Windows, UNIX and Oracle targets.

Refer to the following procedural steps to upgrade both sites to CCS 11.0:

To upgrade a CCS and RMS deployment to CCS 11.0

  1. In Site A, upgrade CCS Reporting and Analytics components on Aps 1 computer to CCS Suite 11.0.

    See Upgrading the reporting and analytics components.

    See Upgrading the CCS components in the silent mode.

  2. Upgrade the Data Processing Service on Manager 1 computer to CCS Manager.

    CCS Manager continues to use the Data Processing Service port.

    See Upgrading the Data Processing Service to CCS Manager.

  3. Configure the CCS Manager on Manager 1 computer to collect data from Windows and SQL targets 1 and 2 in Site A.

    For information on configuring CCS Manager for data collection, See the Configuring data collectors section in the Symantec™ Control Compliance Suite 11.0 User Guide.

  4. CCS Manager can collect data using both agent-less and agent-based methods. If you want to collect data using the agent-based method, install and register the CCS Agents on Windows and SQL targets 1 and 2 to collect data using the agent-based method. Registering the CCS Agent establishes communication with the CCS Agent and the CCS Manager.

    See Supported target computers for agent-based data collection.

    See Installing the CCS Agent on Windows.

    See Registering the CCS Agent.

    See Installing and registering a CCS Agent on Windows in silent mode.

  5. If you want to collect raw-data from Microsoft SQL Server using the CCS Agent, install the SQL Server T4 snap-in on the Target 2 computer on which the CCS Agent is installed.

    See Installing the SQL Server T4 snap-in on CCS Agents for raw-data collection on SQL Server

  6. If you want to collect message based data using CCS Agent, install and configure the application modules for the respective platforms on the CCS Agents and CCS Managers.

    Perform the following steps:

  7. In Site B, upgrade the Data Processing Service on Manager 2 computer to CCS Manager.

    CCS Manager continues to use the Data Processing Service port.

    See Upgrading the Data Processing Service to CCS Manager.

  8. If you want to collect data using the agent-based method, install and register the CCS Agents on Windows and Oracle targets to collect data using the agent-based method. Registering the CCS Agent establishes communication with the CCS Agent and the CCS Manager.

    See Supported target computers for agent-based data collection.

    See Installing the CCS Agent on Windows.

    See Registering the CCS Agent.

    See Installing and registering a CCS Agent on Windows in silent mode.

  9. If you are collecting data from UNIX computers using the BV-Control for UNIX Agents, install and register CCS Agent on the Agent 1 and Agent 2 computers containing the BV-Control for UNIX Agent. Registering the CCS Agent establishes communication with the CCS Agent and the CCS Manager.

    See Supported target computers for agent-based data collection.

    See Installing the CCS Agent on UNIX.

    See Registering Symantec ESM agents on UNIX.

    See Installing and registering a CCS Agent on UNIX in silent mode.

    It is recommended, that until you complete the upgrade and perform data collection from the new deployment for the first time, you should maintain a co-existence of the BV-Control for UNIX Agents and the CCS Agents on Agent 1 and Agent 2 computers. Later, once you are sure that you are able to collect data from the new CCS Agents, you can remove the BV-Control for UNIX Agents from the Agent 1 and Agent 2 computers, and upgrade the remaining BV-Control for UNIX Agents in your deployment.

    See Performing a remote upgrade of BV-Control for UNIX agents.

  10. Configure the CCS Manager to collect data from Windows, Oracle and UNIX targets in Site B.

    As the CCS Manager is in the domain ABC.com, ensure that there is a domain trust relationship between domains ABC.com and PQR.com, for the CCS Manager to collect data from targets 5 and 6 in the domain PQR.com.

    If you have multiple Query Engines collecting data from target computers, you can replace 4 such Query Engines with 1 CCS Manager.

    For information on configuring CCS Manager for data collection, See the Configuring data collectors section in the Symantec™ Control Compliance Suite 11.0 User Guide.

  11. If you want to collect message based data using CCS Agent, install and configure the application modules for the respective platforms on the CCS Agents and CCS Managers.

    Perform the following steps:

  12. Import Assets into CCS. You can then evaluate the assets against mapped control statements, predefined and custom standards, and against external data systems.

    Perform one of the following steps:

    • If you are collecting data using the agent-less method, you can import assets from your network or you can import assets using the CSV, ODBC or LDAP data collectors. For information on importing assets or configuring the data collectors, see the Importing assets for the first time or Configuring data collectors sections in the Symantec™ Control Compliance Suite 11.0 User Guide.

      See Importing the assets for the first time

    • If you are collecting data using the agent-based method, run the Import assets and agents job to create agent-based assets. See the Importing assets and agents section in the Symantec™ Control Compliance Suite 11.0 User Guide.

      See Importing assets and agents

  13. Organize the assets in folders or groups. See the Creating asset groups section in the Symantec™ Control Compliance Suite 11.0 User Guide.

    See Asset groups

  14. Configure credentials. CCS lets you manage common credentials and asset credentials for agent-less and agent-based targets at a central location.

    Perform one of the following steps:

    • If you are collecting data using the agent-less method, add common platform and folder credentials. See the Configuring credentials section in the Symantec™ Control Compliance Suite 11.0 User Guide.

    • If you are collecting data using the agent-based method, add common platform and folder credentials, and set the appropriate agent configuration parameters in the agent.conf file.

      For information on adding common credentials, see the Configuring credentials section in the Symantec™ Control Compliance Suite 11.0 User Guide.

      For information on setting the agent configuration parameters, see the Configuring agents section in the Symantec™ Control Compliance Suite 11.0 User Guide.

      See Agent settings

  15. Configure routing rules. Routing rules let you define a particular site or a CCS manager to perform the tasks that are related to your assets or your agents. You can use routing rules to route CCS jobs based on your network environment or for achieving better load balancing. You can configure routing rules for assets based on IP range, Subnet, Expressions or Asset groups.

    For information on configuring routing rules, see the Configuring routing rules section in the Symantec™ Control Compliance Suite 11.0 User Guide.

    See Creating a routing rule .

  16. After you complete the upgrade, check the health and status of all CCS components from the CCS Console. For information on checking the health and status of the CCS components, see the Refreshing health and status section in the Symantec™ Control Compliance Suite 11.0 User Guide.


Legacy ID



v71960083_v74603629


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


Terms of use for this information are found in Legal Notices