Control Compliance Suite Reporting and Analytics
September 2012

Issue

  • The Windows Patch Assessment Check Library Technical Standards Pack in Control Compliance Suite Reporting and Analytics 9.0, 10.0, and 10.5.1 Content has been updated with the latest security updates as of September 2012. The supported XML version number is 2.0.0.2534.

See  CCS_WindowsPatchAssessmentCheckLibrary_Release_Notes_September_2012.htm

Note

If this Hotfix is applied on 2011-02 PCU the number of checks in the Windows Patch Assessment Check Library will be less than what it was before this Hotfix installation. This is because the standard after installation will contain checks for bulletins greater than or equal to January 2010. This is because 2011-03 PCU has the logic of splitting the standards before and after January 2010. To get all the checks before January 2010 apply the 2011-03 PCU.

If this Hotfix is applied on 2011-03 PCU only the standard Windows Patch Assessment Check Library will be upgraded. The Windows Patch Assessment Check Library Less Than Year 2010 will remain as it is.

Prerequisites

Performance improvements have been made for the Windows Patch Assessment standard in the 2011-2 PCU. From May 2011 onwards the Hotfix uses the performance improvements. Therefore, the installation of the 2011-2 PCU or a later version of the PCU is now a pre-requisite before installing the Hotfix. Failure to do so may affect the data collection and evaluation jobs if they are executed against the entire Windows Patch Assessment Standard.

Requirements

This Hotfix applies only to version 9.0, 10.0, and 10.5.1 of the Control Compliance Suite Reporting and Analytics, which must be installed before applying the Hotfix. Please contact technical support or your sales representative for information on obtaining Control Compliance Suite Reporting and Analytics.

Installing the Hotfix

Before you install this Hotfix , you must close any Control Compliance Suite console that is running.

To install the Hotfix:

  1. The Symantec Application Server Service must be running on the computer where the CCS Application Server is installed.
    The Symantec Directory Support Service, Symantec Management Services Service, and SymantecCCS services must be running on the machine where the CCS Directory Server is installed.
  2. Copy CCS_WindowsPatchAssessmentCheckLibrary_10.50.326.10022_September_2012_Update.exe to the computer where the Application Server is installed.
  3. Double-click CCS_WindowsPatchAssessmentCheckLibrary_10.50.326.10022_September_2012_Update.exe.
  4. In the Welcome panel of the InstallShield Wizard, click Next.
  5. In the Software License Agreement panel, read the agreement, click I accept the terms in the license agreement, and then click Next.
  6. In the Location to Save Files panel, in the Save files in folder text box, select or type the folder where you want to extract the files. Click Next.
  7. In the Welcome panel of Symantec Control Compliance Suite setup, click Next.
  8. In the Software License Agreement panel, read the agreement, click I accept the terms in the license agreement, and then click Next.
  9. In the panel that contains the list of Technical Standards Packs that are being upgraded, click Next. The Setup upgrades the Technical Standards Packs in the Control Compliance Suite.
  10. Click Finish.

Note: The exe file must be run in the context of a user who has rights on the Control Compliance Suite installation directory.

Hotfix contents

All Hotfix files are digitally signed for your protection.

The following table contains the Control Compliance Suite Reporting and Analytics Content files that have changed after the release of Control Compliance Suite Reporting and Analytics:

Control Compliance Suite Reporting and Analytics Content files

Version

SEForMSPatches.xml

-


Copyright © 2012 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, BindView, the BindView logo, and bv-Control  are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

The Licensed Software and Documentation are deemed to be “commercial computer software” and “commercial computer software documentation” as defined in FAR Sections 12.212 and DFARS Section 227.7202.