Software requirements

You must install/configure the following prerequisites before installing the CCS components:

Table: Prerequisites required to install CCS

Prerequisite

Description

SQL Server

The following versions of SQL Server are supported:

  • Microsoft SQL Server 2008 SP1, SP2 (supported for both 32-bit and 64-bit computers)

  • Microsoft SQL Server 2008 R2 (supported for both 32-bit and 64-bit computers)

  • Microsoft SQL Server 2012 (supported for both 32-bit and 64-bit computers)

  • Microsoft SQL Server 2014 (supported for both 32-bit and 64-bit computers)

Note:

Microsoft SQL Server 2005 is supported only if you are upgrading from an earlier version of CCS.

You must manually install the software or use an existing installation. CCS creates a production database and a reporting database to store the compliance data. Depending on the scale of the deployment, you might require one or more Microsoft SQL Server installations.

It is recommended that the Application Server should be configured to use the SSL connections for the Microsoft SQL Server instances that host the CCS databases. If you use SSL connections, you must ensure that you configure them before you install CCS. Refer to the Microsoft SQL Server documentation (http://support.microsoft.com/kb/316898) for information about configuring SSL connections.

These requirements are for a standalone database server.

Microsoft .Net Framework 3.5 SP1

To install .Net 3.5 SP1 on Windows Server 2008, in the Prerequisites panel of the CCS Setup, expand Microsoft .Net Framework 3.5 SP1 and check Install.

To install .Net 3.5 SP1 on Windows Server 2008 R2, in the Windows Server 2008 Server Manager, go to Features > Add new Feature. Select .Net Framework 3.5.1 features and click Next to complete the installation.

Oracle Instant Client 12.1

If you are collecting data from the Oracle platform, you require the Oracle Instant Client 12.1 files to run on the CCS Manager. If the files are not present on the CCS Manager then the data collection job for Oracle fails. To install the Oracle Instant Client 12.1, locate the Oracle Instant Client version 12.1 files on the Oracle product support website and download the Instant Client Package - Basic package. Unzip the contents of the package to a directory at a known location, and add the directory path to the PATH environment variable at system level.

Oracle Instant Client 12.1 is not installed by default while installing CCS. You can install Oracle Instant Client 12.1 before or after you install CCS.

See Installing the Oracle Instant Client for data collection on Oracle.

Internet connection for CCS service

CCS services require access to certificate revocation list (CRL) published by Symantec at location http://crl.verisign.com in order to validate the digital signatures of the assembly. This ensures security by verifying that the certificates with which the assemblies are signed are not in the revocation list.

Symantec recommends that you enable the Internet connection on the computers where the CCS Application Server or CCS Console is installed.

CCS Manager does not require internet access.

Java Runtime Environment (JRE) 1.7_03 or later

If you are upgrading the ESM Console and ESM Utilities to version 11.1, you require JRE 1.7_03 or later to run the ESM Console and ESM Utilities.

Table: Prerequisites required to use the CCS Web Console and the Policy Central

Configuration

Description

Browsers

Symantec has verified the functioning of the CCS Web Console and the Policy Central on the following versions of specified Web browsers:

Perform the following browser specific configurations on the computer from which you are accessing the CCS Web Console or the Policy Central.

If you are using the Internet Explorer browser:

  • Add the FQDN of the CCS Application Server to Trusted sites.

  • Enable the Windows Integrated Authentication.

  • Logon automatically with the current username and password or logon automatically only in the intranet zone.

  • Enable the Active Scripting setting for JavaScript execution

  • Go to Tools > Compatibility View Settings and uncheck the option Display intranet sites in Compatibility View.

If you are using the Mozilla Firefox browser:

  • Open Firefox, and in the address bar, type about:config.

  • In the Search bar, type network.negotiate to filter the list.

  • Double-click network.negotiate-auth.delegation-uris, and add the FQDN of the CCS Application Server in the dialog box.

  • Double-click network.negotiate-auth.trusted-uris, and add the FQDN of the CCS Application Server in the dialog box.

If you are using the Google Chrome browser:

  • In the Settings, click Show Advanced Settings.... and under Network, click Change proxy settings.... Add the FQDN of the CCS Application Server to Local Intranet.

Screen resolution

Symantec recommends a screen resolution with an aspect ratio of 1280 x 1024 to view the CCS Web Console.

Internet Information Service (IIS)

For the CCS Application Server installed on Windows Server 2008 or Windows Server 2012, ensure that you use Windows Authentication and Static Content. If there is no Windows authentication on the server, then you can add it through the Add Role Services dialog box for Web Server (IIS), in Server Manager.

CCS Web Console works using both HTTP or HTTPS protocol. If you want to use HTTPS protocol, ensure that you have enabled HTTPS protocol on the computer on which CCS Web Console is installed. If not, then refer to the support website for Microsoft to install HTTPS.

You require the following MIME types for the CCS Web Console:

.js

.css

.htm

.html

.exe

.deploy

Service Principal Name (SPN)

You must setup Service Principal Names' (SPN) after installing CCS 11.1 or upgrading to CCS 11.1.

CCS 11.1 provides a batch file containing the SPN setup script. The SPN script file contains the set SPN commands to set the required SPNs for the CCS components. Provide the script file to the domain administrator to create the Service Principal Names. You can export the batch file from the CCS Suite installer after installing the Application Server, or by using the VerifyDelegation utility located inside the <Install_Directory>\Application Server folder

Set up an SPN with the NetBIOS name and the fully qualified domain name (FQDN) of the domain user account in whose context the application pool executes. SPN can be set up from the Application Server or the DC.

Execute the following commands on the CCS Application Server where IIS 6 or IIS 7 is used. For IIS 7, you must execute these commands only in the following cases.

  • IIS 7 is used with Kernel Mode Authentication disabled.

  • IIS 7 is used with Kernel Mode Authentication enabled and the useAppPoolCredentials attribute set to TRUE.

By default, the Kernel Mode Authentication is enabled.

  • SetSpn.exe -a http/Application_Server_computer's_NetBIOS_name DomainName\UserName

  • SetSpn.exe -a http/Application_Server_computer's_FQDN DomainName\UserName

    The setspn is a command-line utility.

Note:

You can associate an SPN with a single user account.

Do the following on the Windows Server computers to enable delegation for the Application Server's service account.:

  • In the user properties, go to the Delegation tab, and select the option Trust this Computer for delegation to any service (Kerberos only).

ASP.NET v4.0.30319

Perform respective tasks to install the application on the CCS Application Server that is installed on Windows Server 2008 or Windows Server 2012.

ASP.NET v4.0.30319 Web Service Extensions

On the CCS Application Server computer, in the IIS Manager, you must set the value as Allowed for the ASP.NET v4.0.30319 Web Service Extensions.

If ASP.NET v4.0.30319 is not present on the computer, the CCS setup installs the ASP.NET v4.0.30319. You can perform this procedure once the CCS setup installs the prerequisites and displays the Welcome panel.

To set the value on Windows Server 2008 and Windows Server 2012, in the Internet Information Services (IIS) Manager, in the Connections Pane, click the server node in the tree. On the server home page, under IIS, double-click ISAPI and CGI Restrictions. Right-click ASP.NET v4.0.30319 and click Allow.

To set the value on Windows Server 2003, in the Internet Information Services (IIS) Manager, in the left Pane, click the server node in the tree, and then click Web Service Extensions. On the Web Service Extensions page, selectASP.NET v4.0.30319 and click Allow.

HTTP Activation for .NET Framework 4.5

To launch Policy Central on a Windows 2012 computer, HTTP must be activated for .NET Framework 4.5.

In the Server Manager, under Roles and Features, navigate to ASP under Webserver(IIS) > Web Server > Application Development and select HTTP Activation under WCF Services.

Full-Text Search on SQL Server

Policy Central uses the Full-Text Search feature of the SQL Server to search in policy documents.

The CCS setup installs the following prerequisites automatically during the UI based installation:

Note:

You must install all prerequisites manually if you are performing a silent installation of the CCS components. CCS setup does not install any prerequisites automatically during the silent installation.

Table: Prerequisites installed automatically during CCS installation

Configuration

Description

Microsoft .NET 4.0 framework

Installs automatically.

Microsoft Visual C++ 2010 redistributable framework

Installs automatically.

Microsoft installer 4.5

Installs automatically.

Microsoft Access Database Engine 2010

Installs automatically.

SQL Database Management Objects (SQL-DMO) 8.05.1054

Installs automatically.

CCS supports only version 8.05.1054 of the SQL-DMO for data collection. You must have the correct SQL DMO version on the CCS Manager computers for agent-less data collection and CCS Agent computers for agent-based data collection. If the SQL-DMO version is other than version 8.05.1054, you may experience problems in data collection. For example, the Members field in the server login datastore may show value as "UNKNOWN".

The SQL DMO version 8.05.1054 files for 32 bit and 64 bit operating systems are located in the Redist folder of the product media. The filenames are SQLServer2005_BC and SqlServer2005_BC_x64.

Crystal Reports 2010

Installs automatically during the CCS Suite installation.

You must install Crystal Reports 2010 on the CCS Manager computer that is configured with the Reporter role.

To install Crystal Reports 2010 manually, in the Prerequisites panel of the CCS Setup, expand Crystal Reports and check Install. You can also install Crystal Reports 2010 using the CrystalReportsDotNet.MSI file from the <installation directory>/Symantec/CCS/Reporting and Analytics/WebPortal/Console/Redist folder of the CCS Application Server or you can install CrystalReportsDotNet.MSI from the Redist folder of the product media

Crystal Reports 2010 hot fix

Installs automatically during the CCS Suite installation.

If the hot fix fails to install automatically, you must install the hot fix manually. For example, while installing CCS on Windows Server x64, incase of hot fix installation failure, the Warning panel of the CCS Setup displays the following error message:

Access to the path C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win64_x64.

To install the hot fix manually on Windows Server x64, extract the secSSOwin64_x64 file located in the Redist folder of the product media, to the location C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win64_x64\. Extract the secSSOwin32_x86 file located in the Redist folder of the product media, to the location C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\

To install the hot fix manually on Windows Server x86, extract the secSSOwin32_x86 file located in the Redist folder of the product media, to the location C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\

ADAM SP1 instance

Installs automatically.

Symantec LiveUpdate Client

Installs automatically.

Symantec Help

Installs automatically.
Imported Document ID: HOWTO107122
Legacy ID: v65836875_v105506697

Thanks for your feedback. Let us know if you have additional comments below. (requires login)

    © 1995-2020 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.