Application Resilience Policies for McAfee Drive Encryption

You can activate an Application Resilience policy for McAfee® Drive Encryption to collect information about the functional status of McAfee Drive Encryption installed on your Windows devices and view the results in reports. You can also configure the policy to attempt to repair or reinstall McAfee Drive Encryption, McAfee Endpoint Encryption Agent, and McAfee Drive Encryption Go (if selected in the policy configuration).

Application Resilience policies for McAfee Drive Encryption are supported on devices running a supported version of the Windows operating system and one of the following versions of:

  • McAfee Drive Encryption:

    • 7.x or higher

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

  • McAfee Endpoint Encryption Agent:

    • 7.x or higher

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

  • McAfee Drive Encryption Go (if selected in the policy configuration):

    • 7.x or higher

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

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

This platform requires the installation of McAfee Endpoint Encryption Agent on the organization's devices.

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

Component Test performed
Services Installed Running Signed by

  • McAfee Endpoint Encryption Agent (MfeEpeHost.exe)

  • McAfee Drive Encryption SGX Service (MDECryptService.exe)

  • McAfee Drive Encryption Go (EegoService.exe)1

 P P

McAfee, Inc.

1 Only checked if selected in the policy configuration

You can configure an Application Resilience policy for McAfee Drive Encryption to enable the Application Resilience (RAR) component A lightweight software component of the Absolute 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 McAfee Drive Encryption, McAfee Endpoint Encryption Agent, or McAfee Drive Encryption Go if they aren't functioning, or reinstall them if they are missing or can't be repaired.

NOTE  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 Absolute agent can respond to the following issues:

Issue

Resolution
Repair

One or more of the following services aren't running:

  • McAfee Endpoint Encryption Agent (MfeEpeHost.exe)

  • McAfee Drive Encryption SGX Service (MDECryptService.exe)

  • McAfee Drive Encryption Go (EegoService.exe)1

The RAR component restarts the service.

One or more of the following services aren't installed and the service's executable can be detected on the device:

  • McAfee Endpoint Encryption Agent (MfeEpeHost.exe)

  • McAfee Drive Encryption SGX Service (MDECryptService.exe)

  • McAfee Drive Encryption Go (EegoService.exe)1

The RAR component reinstalls each missing service.
Reinstall

One or more of the following services aren't installed and the service's executable cannot be detected on the device:

  • McAfee Endpoint Encryption Agent (MfeEpeHost.exe)

  • McAfee Drive Encryption SGX Service (MDECryptService.exe)

  • McAfee Drive Encryption Go (EegoService.exe)1

The RAR component downloads and installs the configured version of McAfee Endpoint Encryption, McAfee Endpoint Encryption Agent, or McAfee Encryption Go.

NOTE  Downgrades are not supported. If the version installed on a device is higher than the expected version, no action is taken.
McAfee Drive Encryption, McAfee Endpoint Encryption Agent, or McAfee Drive Encryption Go failed to be repaired, or the expected versions aren't installed

1 Only checked if selected in the policy configuration

For each application, you can add a 32-bit installer, a 64-bit installer, or both. The installers:

  • must be MSI files

  • can have any file name

The RAR component looks for the following files names when checking pre-cached installers:

Component File name
Installers
  • McAfeeEEAgent.msi
  • McAfeeDE.msi
  • McAfeeDEGo.msi1

1 Only required if selected in the policy configuration

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 versions:

  1. Under McAfee Endpoint Encryption Agent version, enter the version of McAfee Endpoint Encryption Agent 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, 7.* or 7.2.*.

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

  2. Under McAfee Drive Encryption version, enter the version of McAfee Drive Encryption 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, 7.* or 7.2.*.

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

  3. [Optional] If you want to monitor the health of McAfee Drive Encryption Go, select the Select this option to monitor McAfee Drive Encryption Go checkbox.

  4. [Optional] Under McAfee Drive Encryption Go version, enter the version of McAfee Drive Encryption Go you expect to be running on your devices if you selected the Select this option to monitor McAfee Drive Encryption Go checkbox.

    • 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, 7.* or 7.2.*.

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