Application Resilience policies for HCL BigFix

Application Resilience policies for HCL BigFix are supported on devices running:

• a supported version of the Windows operating system

• PowerShell version 5.1 or higher

  Due to PowerShell restrictions imposed by Microsoft, Application Resilience isn't supported for this application on devices running Windows 11 SE.

• one of the following versions of HCL BigFix:

  • 9.5.x or higher

    Significant software changes in higher versions may cause health checks to become invalid.

In addition to checking the version, the following table describes the health checks performed:

If you select Report higher versions as Compliant, higher versions report Compliant without running health checks.

Component	Test performed
Services	Installed	Running	Signed by
BES Client (BESClient.exe)	P	P	One of the signers entered in the policy configuration By default, Signers contains "HCL America Inc.".

You can configure an Application Resilience policy for HCL BigFix to enable the Application Resilience (RAR) component A lightweight software component of the Secure Endpoint Agent that detects the status of third party applications installed on a device. The component may also attempt to repair the third party application if it is non-compliant. The RAR component is deployed on a device only when the device is associated with a customized policy group and that policy group's Application Resilience policy is activated. to repair HCL BigFix if it's not functioning, or reinstall it if it's missing or can't be repaired.

Depending on the Absolute product licenses associated with your account, the Report and repair option, and the Report, repair, and reinstall option may not be available.

The RAR component of the Secure Endpoint Agent can respond to the following issues:

Issue	Resolution
Repair
The BES Client (BESClient.exe) service isn't running	The RAR component restarts the service.
The BES Client (BESClient.exe) service isn't installed and the service's executable can be detected on the device	The RAR component reinstalls the missing service.
Reinstall
Downgrades are not supported. If the version installed on a device is higher than the expected version, no action is taken.
The BES Client (BESClient.exe) service isn't installed and the service's executable cannot be detected on the device	The RAR component downloads and installs the configured version of the application.
HCL BigFix failed to be repaired, or the expected version isn't installed

If you want the Secure Endpoint Agent to reinstall HCL BigFix if it is non-functional or missing, you need to make the following files available:

• BES Client setup (setup.exe)
• masthead (.afxm)

To prepare the installer:

1. Download the BES Client setup (setup.exe) and the masthead (.afxm) files following the steps provided in the HCL BigFix documentation.

2. Select the setup.exe and the masthead .afxm files and add them to a new ZIP file.

   The ZIP file can have any name.

   Do not include any parent folders or subfolders in the ZIP file. Do not change the name of the setup.exe file.

The ZIP file can now be uploaded to the Secure Endpoint Console or hosted on your own server.

Before you activate an Application Resilience policy you need to configure the policy. You need to configure the application version in addition to the settings in Configuring Application Resilience policies.

To configure the application version:

Under HCL BigFix version, enter the version of HCL BigFix you expect to be running on your devices.

• The target version must be a sequence of digits separated by a period.

• You can use wildcard "*" characters in the version number.

  • Major version starting with 9: You can use wildcard "*" characters after the minor version number, for example, 9.5.* or 9.5.19.*.
  • Major version starting with 10 or higher: You can use wildcard "*" characters after the major version number, for example, 10.*.

Make sure the version you are entering is consistent with version 9.5.x or higher.