Application Resilience policies for SentinelOne
You can activate an Application Resilience policy for SentinelOne™ to collect information about the functional status of SentinelOne installed on your Windows devices and to view the results in reports. You can also configure the policy to attempt to repair or reinstall the application.

Application Resilience policies for SentinelOne 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 SentinelOne:
-
22.x or higher
Significant software changes in higher versions may cause health checks to become invalid.
- 3.x to 21.x
-

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 |
|
P | n/a | n/a |
|
P | ||
Application name | |||
The application uses the following name:
|


You can configure an Application Resilience policy for SentinelOne 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 attempt to repair SentinelOne 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 and Report, repair, and reinstall options may not be available.
The RAR component of the Secure Endpoint Agent can respond to the following issues:
Issue | Resolution |
---|---|
Repair | |
One or more of the following services aren't running:
|
The RAR component restarts each stopped service. Tamper Protection must be disabled in your SentinelOne configuration for the RAR component to successfully repair SentinelOne. |
One or more of the following services aren't installed and the service's executable can be detected on the device:
|
The RAR component reinstalls each missing service. Tamper Protection must be disabled in your SentinelOne configuration for the RAR component to successfully repair SentinelOne. |
Reinstall | |
Downgrades are not supported. If the version installed on a device is higher than the expected version, no action is taken. |
|
One or more of the following services aren't installed and the service's executable cannot be detected on the device:
|
If the application is installed, the RAR component uninstalls it. After the application is uninstalled, or if the application wasn't installed, the RAR component downloads and installs the configured version of the application. A device restart is required after the application is uninstalled. The Secure Endpoint Agent doesn't force the device to restart, so a status of Not Compliant continues to show in the Application Resilience reports until the device user performs a restart and the configured version of the application is downloaded and installed. You can review the report's Status details to determine if a restart is required. If Tamper Protection is enabled in your SentinelOne configuration and SentinelOne is installed on the device, the verification key must be correctly configured in Additional uninstallation commands for the RAR component to be able to successfully uninstall and reinstall SentinelOne. |
SentinelOne failed to be repaired, or the expected version isn't installed |

You can configure an Application Resilience policy for SentinelOne 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 attempt to reinstall SentinelOne if it's not functioning or missing.
The Report and repair option isn't supported. Depending on the Absolute product licenses associated with your account, 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 |
---|---|
Reinstall | |
Downgrades are not supported. If the version installed on a device is higher than the expected version, no action is taken. |
|
One or more of the following services aren't installed:
|
The RAR component downloads and installs the configured version of the application. Tamper Protection must be disabled in your SentinelOne configuration for the RAR component to successfully repair SentinelOne. |
One or more of the following services aren't running:
|
|
The expected version of SentinelOne isn't installed |


You can add a 32-bit installer, a 64-bit installer, or both. The installers:
-
must be EXE files
-
can have any file name

The RAR component looks for the following files names when checking pre-cached installers:
Component | File name |
---|---|
Installers | SentinelOne.exe |

The installer:
-
must be an EXE file
-
can have any file name

The RAR component looks for the following files names when checking pre-cached installers:
Component | File name |
---|---|
Installers | SentinelOne.exe |


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 SentinelOne™ version, enter the version of SentinelOne you expect to be running on your devices.
- The target version must be a sequence of digits separated by a period.
- You can use wild card "*" characters after the major version, for example, 22.* or 22.1.*.
Make sure the version you are entering is consistent with version 22.x or higher.
If you selected the Report, repair, and reinstall option, you also need to configure this setting in addition to the settings in Configuring Application Resilience policies.
To configure the SentinelOne specific setting:
-
[Optional] To only reinstall the application if it's missing, select the checkbox next to Do not reinstall or upgrade if the app is already installed. When this option is selected, the application is not reinstalled when either of the following conditions apply:
- The application version is lower than the expected version.
- The application can't be repaired.
-
[Optional] Under Additional installer commands, enter the applicable command-line parameters to configure any settings not covered by the policy configuration. If you don't configure any settings, the default values shown in the SentinelOne documentation are used.

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 SentinelOne™ version, enter the version of SentinelOne you expect to be running on your devices.
- The target version must be a sequence of digits separated by a period.
- You can use wild card "*" characters after the major version, for example, 3.*, 3.1.*, or 3.1.3.*.
Make sure the version you are entering is consistent with version 3.x to 21.x.
If you selected the Report, repair, and reinstall option, you also need to configure these settings in addition to the settings in Configuring Application Resilience policies.
To configure the SentinelOne specific settings:
- Under Site Token, enter your SentinelOne management Site Token. You can find the correct token by logging in to the SentinelOne Management Console.
-
[Optional] Under Additional installer commands, enter the applicable command-line parameters to configure any settings not covered by the policy configuration. If you don't configure any settings, the default values shown in the SentinelOne documentation are used.