<div dir="ltr"><p>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.</p><p><strong>Product</strong>: BigFix Compliance</p><p><strong>Title</strong>: Availability of BigFix Compliance Analytics version 2.0 Patch 17</p><p><strong>Published site:</strong> SCM Reporting 169</p><p>This release includes Fixes for:</p><table class="gmail-MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="594" style="border-collapse:collapse">
<tbody><tr style="height:18.1pt">
<td width="103" valign="bottom" style="width:77.25pt;border:1.5pt solid black;background:rgb(98,156,245);padding:0.75pt 0.75pt 2.25pt;height:18.1pt">
<p class="MsoNormal" style="margin:0in;font-size:12pt;font-family:"Times New Roman",serif"><span lang="EN" style="font-size:10.5pt;color:black"> </span><span lang="EN" style="font-size:10.5pt"></span></p>
<p class="MsoNormal" style="border-width:medium;border-style:none;border-color:currentcolor;margin:0in;font-size:12pt;font-family:"Times New Roman",serif"><b><span lang="EN" style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black">DA #</span></b><span lang="EN" style="font-size:10.5pt;color:black"></span></p>
</td>
<td width="491" valign="bottom" style="width:368.55pt;border-width:1.5pt 1.5pt 1.5pt medium;border-style:solid solid solid none;border-color:black black black currentcolor;background:rgb(98,156,245);padding:0.75pt 0.75pt 2.25pt;height:18.1pt">
<p class="MsoNormal" style="border-width:medium;border-style:none;border-color:currentcolor;margin:0in;font-size:12pt;font-family:"Times New Roman",serif"><b><span lang="EN" style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black">Title</span></b><span lang="EN" style="font-size:10.5pt;color:black"></span></p>
</td>
</tr>
<tr style="height:17.1pt">
<td width="103" valign="bottom" style="width:77.25pt;border-width:medium 1.5pt 1.5pt;border-style:none solid solid;border-color:currentcolor black black;background:rgb(237,241,255);padding:0.75pt 0.75pt 7.5pt;height:17.1pt">
<p class="MsoNormal" style="border-width:medium;border-style:none;border-color:currentcolor;margin:0in;font-size:12pt;font-family:"Times New Roman",serif"><span lang="EN" style="font-family:"Aptos Narrow",sans-serif;color:black">KB0130358</span><span lang="EN" style="font-size:10.5pt;color:black"></span></p>
</td>
<td width="491" valign="bottom" style="width:368.55pt;border-width:medium 1.5pt 1.5pt medium;border-style:none solid solid none;border-color:currentcolor black black currentcolor;background:rgb(237,241,255);padding:0.75pt 0.75pt 7.5pt;height:17.1pt">
<p class="MsoNormal" style="border-width:medium;border-style:none;border-color:currentcolor;margin:0in;font-size:12pt;font-family:"Times New Roman",serif"><span lang="EN" style="font-family:"Aptos Narrow",sans-serif;color:black">The import fails to manage the display_name values</span></p>
</td>
</tr>
<tr style="height:17.1pt">
<td width="103" valign="bottom" style="width:77.25pt;border-width:medium 1.5pt 1.5pt;border-style:none solid solid;border-color:currentcolor black black;background:rgb(237,241,255);padding:0.75pt 0.75pt 7.5pt;height:17.1pt">
<p class="MsoNormal" style="border-width:medium;border-style:none;border-color:currentcolor;margin:0in;font-size:12pt;font-family:"Times New Roman",serif"><span lang="EN" style="font-family:"Aptos Narrow",sans-serif;color:black">KB0130344</span></p>
</td>
<td width="491" valign="bottom" style="width:368.55pt;border-width:medium 1.5pt 1.5pt medium;border-style:none solid solid none;border-color:currentcolor black black currentcolor;background:rgb(237,241,255);padding:0.75pt 0.75pt 7.5pt;height:17.1pt">
<p class="MsoNormal" style="border-width:medium;border-style:none;border-color:currentcolor;margin:0in;font-size:12pt;font-family:"Times New Roman",serif"><span lang="EN" style="font-family:"Aptos Narrow",sans-serif;color:black">Bigfix Compliance Import Job fails with errors<br>
1. Violation of PRIMARY KEY<br>
2. RuntimeError: Unable to find Subscribed Sites analysis</span></p>
</td>
</tr>
</tbody></table><p>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.</p><p>For customers with 2.0.16, and facing issues with import, upgrade to 2.0.17 and run the remediate import.</p><p>For all other versions, </p><p>1. Upgrade BigFix Compliance Analytics to version 2.0.17 to take advantage of the fixes</p><p>For first-time installation:</p><p>1. In the License Overview Dashboard in the BigFix console (BigFix Management domain), enable the SCM Reporting site.</p><p>2. In the Security Configuration domain in the console, open the Configuration Management navigation tree.</p><p>3. Select the Fixlet named BigFix Compliance Server 2.0 - First-time Install Fixlet under the BigFix Compliance Install/Upgrade menu tree node.</p><p>4. Follow the Fixlet instructions and take the associated action to install your BigFix Compliance deployment.</p><p>For upgrade installation: Refer to the prescribed upgrade steps for the BigFix Compliance version that you are using.</p><p>IMPORTANT: Before you start any upgrade process, perform a server and database backup.</p><p>A. For BigFix Compliance Analytics versions 1.9.x, 1.10.x and 2.0.x:</p><p>1. Make sure that you complete the server and database backup.</p><p>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.</p><p>3. In the Security Configuration domain in the console, open the Configuration Management navigation tree.</p><p>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.</p><p>5. Follow the Fixlet instructions and take the associated action to upgrade your BigFix Compliance deployment.</p><p>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.</p><p>B. For BigFix Compliance Analytics versions before 1.9:</p><p>1. Manually upgrade to version 1.10.1.48. The 1.10.1.48 installer can be found here <a href="http://software.bigfix.com/download/bfc/server/1.10/bfc-server-1.10.1.48.exe">http://software.bigfix.com/download/bfc/server/1.10/bfc-server-1.10.1.48.exe</a></p><p>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).</p><p>More information:</p><p>● BigFix Compliance Guides: <a href="https://help.hcl-software.com/bigfix/11.0/compliance/Compliance/SCA_Users_Guide/securityandcomplianceanalyticsuserguide.html">https://help.hcl-software.com/bigfix/11.0/compliance/Compliance/SCA_Users_Guide/securityandcomplianceanalyticsuserguide.html</a></p><p>● BigFix Forums - Release Announcements Channel: <a href="https://forum.bigfix.com/c/release-announcements/compliance">https://forum.bigfix.com/c/release-announcements/compliance</a></p><p>BigFix Compliance team<br>HCL BigFix</p><div><div><div id="gmail-_com_10" class="gmail-msocomtxt">
</div>
</div>
</div></div>