Application Resilience policies for Cisco Umbrella Roaming Client
You can activate an Application Resilience policy for Cisco Umbrella® Roaming Client to collect information about the functional status of Cisco Umbrella Roaming Client 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 polices for Cisco Umbrella Roaming Client only support the standalone Cisco Umbrella Roaming Client.

Application Resilience policies for Cisco Umbrella Roaming Client 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, the Report and repair, and the Report, repair, and reinstall options are not supported for this application on devices running Windows 11 SE.
-
one of the following versions of Cisco Umbrella Roaming Client:
-
3.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 |
Umbrella Roaming Client (ERCService.exe) | P | P |
One of the signers entered in the policy configuration By default, Signers contains "Cisco Systems Inc.", "CISCO SYSTEMS, INC.", and "CISCO SYSTEMS". |
Application name | |||
The application uses one of the following names:
|

You can configure an Application Resilience policy for Cisco Umbrella Roaming Client 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 Cisco Umbrella Roaming Client if it's not functioning or to 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 Umbrella Roaming Client (ERCService.exe) service isn't running |
The RAR component restarts the service. |
The Umbrella Roaming Client (ERCService.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 Umbrella Roaming Client (ERCService.exe) service isn'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. |
Cisco Umbrella Roaming Client failed to be repaired, or the expected version isn't installed |

If you want the Secure Endpoint Agent to reinstall Cisco Umbrella Roaming Client if it's non-functional or missing, you need to prepare the Cisco Umbrella Roaming Client installer.
To prepare the installer:
- Generate and download the Cisco Umbrella Roaming Client ZIP file from the Umbrella dashboard. Follow the steps provided in the Cisco Umbrella documentation.
- Navigate to the location where you saved the ZIP file and extract the MSI file to the location you want to store the extracted installer.
The MSI file can now be uploaded to the Secure Endpoint Console or hosted on your own server.

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

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 Cisco Umbrella Roaming Client version, enter the version of Cisco Umbrella Roaming Client 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 number, for example, 3.* or 3.0.* or 3.0.110.*.
Make sure the version you are entering is consistent with version 3.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 Cisco Umbrella Roaming Client 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.
-
Under Installation parameters:
-
[Required] enter the following command-line installation parameters:
- ORG_ID
- ORG_FINGERPRINT
- USER_ID
The values for these parameters can be found in the OrgInfo.json file or the example section of the readme.txt file that are part of the Cisco Umbrella Roaming Client ZIP file you downloaded in Preparing the installer. ORG_FINGERPRINT uses the value shown in FINGERPRINT ID. The following is an example of the required command-line parameters:
CopyORG_ID=222222 ORG_FINGERPRINT=1234567890abcdef USER_ID=111111
-
[Optional] enter any applicable command-line parameters to configure any settings not covered by the policy configuration. The following is an example of the required command-line parameters and one optional parameter:
CopyORG_ID=222222 ORG_FINGERPRINT=1234567890abcdef USER_ID=111111 HIDE_UI=1
-
For more information about the available command-line parameters, see Cisco's documentation.