[BESAdmin-Announcements] Release notes for BigFix Compliance Analytics version 2.0 Patch 17

[Announcements for BES Administrators]

HCL BigFix is pleased to announce the release of BigFix Compliance
Analytics version 2.0 Patch 17.This release resolves the data import issue
identified in Patch 16 and includes all previous fixes. Customers who
delayed upgrading due to the known issue can safely update directly to
Patch 17.

*Product*: BigFix Compliance

*Title*: Availability of BigFix Compliance Analytics version 2.0 Patch 17

*Published site:* SCM Reporting 169

This release includes Fixes for:



*DA #*

*Title*

KB0130358

The import fails to manage the display_name values

KB0130344

Bigfix Compliance Import Job fails with errors
1. Violation of PRIMARY KEY
2. RuntimeError: Unable to find Subscribed Sites analysis

This release Fixes the issue where compliance import operations could fail
while processing modified site display name values. The fix reverts the
display name handling changes for site names to ensure import processing
remains stable and prevents datasource synchronization failures or database
constraint violations during ETL/import execution.

For customers with 2.0.16, and facing issues with import, upgrade to 2.0.17
and run the remediate import.

For all other versions,

1.      Upgrade BigFix Compliance Analytics to version 2.0.17 to take
advantage of the fixes

For first-time installation:

1.      In the License Overview Dashboard in the BigFix console (BigFix
Management domain), enable the SCM Reporting site.

2.      In the Security Configuration domain in the console, open the
Configuration Management navigation tree.

3.      Select the Fixlet named BigFix Compliance Server 2.0 - First-time
Install Fixlet under the BigFix Compliance Install/Upgrade menu tree node.

4.      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:

1.      Make sure that you complete the server and database backup.

2.      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.

3.      In the Security Configuration domain in the console, open the
Configuration Management navigation tree.

4.      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.

5.      Follow the Fixlet instructions and take the associated action to
upgrade your BigFix Compliance deployment.

6.      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:

1.      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

2.      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:
https://help.hcl-software.com/bigfix/11.0/compliance/Compliance/SCA_Users_Guide/securityandcomplianceanalyticsuserguide.html

●       BigFix Forums - Release Announcements Channel:
https://forum.bigfix.com/c/release-announcements/compliance

BigFix Compliance team
HCL BigFix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bigmail.bigfix.com/pipermail/besadmin-announcements/attachments/20260519/85bb886f/attachment.html>