Content on the CCS Manager may not be updated

book

Article ID: 170987

calendar_today

Updated On:

Products

Control Compliance Suite Databases MS SQL SRVR Control Compliance Suite Unix Control Compliance Suite Databases Oracle Control Compliance Suite Netware Control Compliance Suite Assessment Manager Control Compliance Suite Vendor Risk Manager Control Compliance Suite Exchange Control Compliance Suite Virtualization Security Manager Control Compliance Suite Vulnerability Manager Control Compliance Suite Windows Control Compliance Suite Response Assessment Module

Issue/Introduction

  • After updating a PACU on the CCS manager you may find that content with a specific Agent OS is not updated. 
  • For example, on the CCS Manager server you ran a PACU named CCS_11_1_2017-9_PACU_Win.exe successfully. The AIXRecommendedPatches.dat file in the C:\Program Files (x86)\Symantec\CCS\Reporting and Analytics\DPS\control\Unix\OS\AIX\bin folder is not updated and other .dat files in the folder such as C:\Program Files (x86)\Symantec\CCS\Reporting and Analytics\DPS\control\Unix\OS\Linux\bin folder, C:\Program Files (x86)\Symantec\CCS\Reporting and Analytics\DPS\control\Unix\OS\SunOS\bin folder, etc. are updated normally as expected.
  • Content on the CCS Manager may not be updated after updating a PACU

 

Cause

Generally .dat files in the bin folder will be updated if you ran a PACU on the CCS Manager server. But in rare cases, a certain content with a specific Agent OS will not be updated due to there is no new update since the last time PACU applied.

 

Environment

  • Control Compliance Suite 11.5

Resolution

This behavior is 'by design'. Please see the Cause section above for more details.

About PACU update details, please confirm below link. You can check which update has been updated in Release_Notes.pdf.