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
Control Compliance Suite 11.5
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.
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.
Subscribing will provide email updates when this Article is updated. Login is required.