Unable to import the Control Compliance Suite (CCS) Agents after deploying a cloned operating system

book

Article ID: 170597

calendar_today

Updated On:

Products

Control Compliance Suite Exchange

Issue/Introduction

Unable to import the Control Compliance Suite (CCS) Agents after deploying a cloned operating system even if Agents registration success.

 

Cause

The agent installation and registration process is machine specific and that is the reason we ask user to perform separate installation on every host. In creating of master image, the agent installation contains details of main host only like hostname. During installation machine hostname gets register in my config files and if we will follow imaging process we will need to make changes in many places only for hostname like folders and config files.

 

Environment

Control Compliance Suite 11.5

Resolution

This method of deployment is not validated. What Symantec recommends is "Installing and registering a CCS Agent on Windows in silent mode" method only. For information on how to install and register a CCS Agent in silent mode, see Deployment Guide below.

Symantec™ Control Compliance Suite Planning and Deployment Guide: Version: 11.5
https://symwisedownload.symantec.com/resources/sites/SYMWISE/content/staging/DOCUMENTATION/9000/DOC9294/en_US/4.0/CCS_Planning_and_Deployment.pdf

The sample of the bat files for silent execution is provided in the install packages, that can be used to deploy to the Agent system remotely. For the wealth of deploying a bat file, customer can use a third party tool like Symantec Altiris Software Development Kit (ASDK) or can use a login-script created by Group Policy Object (GPO) in the Active Directory environment, which is not outlined in Symantec Deployment Guide.