HCL BigFix is pleased to announce the release of BigFix Compliance Analytics version 2.0 Patch 14
Product : BigFix Compliance
Published site: SCM Reporting v160
BigFix Compliance Analytics version 2.0 Patch 14 includes enhancements and fixes.
Highlights of this release:
· Upgrade Rails to 7.2.2.1
· Update JRE Version to 8.0.8.45
· Update IBM WebSphere Application Server Liberty version to 25.0.0.7
· Mobile (Android, iOS) and ESXi Support
· NVD Source change for Vulnerability Data
Following are the Fixed Jira Tickets in this release.
DA (Defect Article) | Issue key | Summary |
---|---|---|
KB0122461 | BSU-17671 | Compliance error Error: 1 of the originally defined computers has been deleted. |
KB0121387 | BSU-17611 | Saved ReportConfigure view issue |
KB0121747 | BSU-17584 | Compliance report saveas default view |
KB0120746 | BSU-17449 | BigFix Compliance LDAP configuration issue |
KB0120156 | BSU-17279 | Compliance Vulnerability Data |
KB0116163 | BSU-16201 | Unexpected behaviour of Vulnerable Computers in Vulnerability Report. |
Actions to take:
- Upgrade BigFix Compliance Analytics to version 2.0.14 to take advantage of the fixes.
For first-time installation:
-
In the License Overview Dashboard in the BigFix console (BigFix Management domain), enable the SCM Reporting site.
-
In the Security Configuration domain in the console, open the Configuration Management navigation tree.
-
Select the Fixlet named BigFix Compliance Server 2.0 - First-time Install Fixlet under the BigFix Compliance Install/Upgrade menu tree node.
-
Follow the Fixlet instructions and take the associated action to install your BigFix Compliance deployment.
For upgrade installation: Refer to the prescribed upgrade steps for the BigFix Compliance version that you are using.
IMPORTANT: Before you start any upgrade process, perform a server and database backup.
A. For BigFix Compliance Analytics versions 1.9.x, 1.10.x and 2.0.x:
-
Make sure that you complete the server and database backup.
-
It is recommended to stop the BigFix Compliance Server or at least disable scheduled Data Imports to ensure that Data Import is not in progress during the upgrade.
-
In the Security Configuration domain in the console, open the Configuration Management navigation tree.
-
Under the BigFix Compliance Install/Upgrade menu tree item, select the BigFix Compliance Server 2.0 - Upgrade Fixlet which automatically installs and upgrades to the new version.
-
Follow the Fixlet instructions and take the associated action to upgrade your BigFix Compliance deployment.
-
Update the data schema. To do this, log in to the BigFix Compliance web interface from the host server and proceed with configuration. Upgrading the data scheme is expected and it will take some time to complete. NOTE: Automatic upgrade installation only affects installations running under the LocalSystem account. Follow the Fixlet instructions to install the update manually if this fix cannot be applied.
B. For BigFix Compliance Analytics versions before 1.9:
-
Manually upgrade to version 1.10.1.48. The 1.10.1.48 installer can be found here http://software.bigfix.com/download/bfc/server/1.10/bfc-server-1.10.1.48.exe
-
After manually upgrading to version 1.10.1.48, use the BigFix Compliance Server 2.0 Upgrade Fixlet to upgrade to version 2.0 (See step A).
More information:
· BigFix Compliance Guides: HCL Software 404 Page
· BigFix Forums - Release Announcements Channel: https://forum.bigfix.com/c/release-announcements/compliance
BigFix Compliance team
HCL BigFix