Getting started with Application Persistence policies

Your organization depends on a multitude of software applications to complete the critical business processes required in your day-to-day operations. Many of these applications are deployed to your fleet of devices with limited access to tools that ensure that the devices are secure and comply with your organization's defined policies. Over time, these critical applications may become non-functional or non-compliant without your knowledge, potentially exposing your organization to data breaches, regulatory non-compliance, and a loss of employee productivity.

In Absolute, administrators can activate Application Persistence policies to help validate and maintain the resiliency of critical third party applications in the following ways:

  • Report on the functional status of the application's essential components
  • Determine if the device is compliant by comparing the current state of the application with the desired state (as defined in the Application Persistence policy configurations)
  • Repair components that are non-functional or non-compliant (for most applications, requires Absolute Resilience license)
  • Reinstall the application if it can't be repaired or is no longer installed (for most applications, requires Absolute Resilience license)

NOTE  For more information about Application Persistence, review the training videos and interactions in the Learning Hub.