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

Application Resilience policies for Netskope 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 Netskope:
-
84.x or higher
Significant software changes in higher versions may cause health checks to become invalid.
- 74.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 |
Netskope Client Service (stAgentSvc.exe) | P | P |
One of the signers entered in the policy configuration By default, Signers contains "netSkope Inc" and "Netskope, Inc." . |
Application name | |||
The application uses the following name:
|

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 |
Netskope Client Service (stAgentSvc.exe) | P | P | netSkope Inc |
Application name | |||
The application uses the following name:
|

You can configure an Application Resilience policy for Netskope 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 Netskope 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 | |
The Netskope Client Service (stAgentSvc.exe) isn't running |
The RAR component restarts the service. |
The Netskope Client Service (stAgentSvc.exe) 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 Netskope Client Service (stAgentSvc.exe) 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. |
Netskope failed to be repaired, or the expected version isn't installed |

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

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


Before you activate an Application Resilience policy you need to configure the policy. If you are using version 84.x or higher, you need to configure the application version in addition to the settings in Configuring Application Resilience policies.
To configure the application version:
-
Under Application version, select 84.* or higher from the drop-down menu.
-
Under Netskope version, enter the version of Netskope 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 after the major version, for example, 84.* or 84.13.*.
Make sure the version you are entering is consistent with version 84.x or higher.
-
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 Netskope specific settings:
-
[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 Installer commands, enter the applicable command-line parameters to configure any additional settings required. If your configuration requires an installation token or your add-on manager host name, you can add them here.

Before you activate an Application Resilience policy you need to configure the policy. If you selected the Report, repair, and reinstall option, configure these settings in addition to the settings in Configuring Application Resilience policies.
To configure the Netskope specific settings:
-
[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] In Installation Token, enter the token used to install Netskope if it's required for your configuration.
- [Optional] In Netskope Add-on Manager hostname, enter your add-on manager host name. For example, addon.goskope.com or addon.eu.goskope.com.
-
[Optional] Under Additional installation commands, enter the applicable installation command-line parameters to configure any settings not covered by the policy configuration. For example, the following command-line parameters may include:
- mode=peruserconfig
- userconfiglocation={path}
- autoupdate={on|off}
- installmode=idP
For more information on the installation token, the add-on manager host name, and available command-line parameters, see Netskope's documentation.