Esper Agent Policy

Esper Agent Lifecycle and Deprecation Policy

At Esper, we are committed to providing a seamless Mobile Device Management (MDM) experience through continuous innovation and regular updates to our Esper Android/iOS Agent (sometimes referred to as a DPC). To ensure the highest security, best performance, and access to new features, we have established a lifecycle and deprecation policy for Esper Agent versions.

This policy outlines how long each agent version is supported, our approach to encouraging updates, and the implications of using outdated versions.

1. Policy Objectives

• Ensure customers benefit from the latest security patches, features, and improvements.
• Maintain an optimal level of support by focusing on actively used agent versions.
• Reduce operational overhead caused by supporting significantly outdated versions.

2. Agent Version Lifecycle

1. Release & Active Support
   • Each Esper Agent version will be actively maintained for one year from its release date. During this period, the version will receive compatibility updates, new feature enhancements, bug fixes, and security fixes via newer versions of the agent to ensure optimal performance and reliability for customers.
2. End of Support
   • Additional charges for older versions: If a device has an Esper Agent version older than 1 year, a per-device charge of 30% of the standard per-device payment may be applicable.

3. Encouraging Regular Updates

• To minimize disruption and ensure optimal performance, customers are encouraged to enable automatic updates for the Esper Agent. You can find instructions to do that here.
• Regular updates help avoid compatibility issues, ensure alignment with the latest Esper platform capabilities, and enhance security. They also allow you to automate your update process and can be done without any human intervention.

4. Impact of Using Legacy Versions

• Customers using legacy agent versions may face security vulnerabilities, compatibility issues with the Esper platform, or degraded performance.
• Esper will not be able to guarantee the resolution of issues for legacy versions. Continued use of older versions will be charged at an additional cost. If a device has an Esper Agent version older than 1 year, a per-device charge of 30% of the standard per-device payment may be applicable.

6. Policy Enforcement

• Starting Feb 12, 2025, this policy will be enforced for all customers using the Esper Agents.
• Esper agents that have already reached their end of life as of the policy’s effective date will be granted a six-month transition period for upgrading. We recognize that customers require sufficient time for change management, and as a result, Esper is providing this grace period to facilitate a smooth transition

7. Next Steps for Customers

• Check Your Current Esper Agent Version
  • If your Esper Agent version is v7.14.1284 or below (released on Feb 12, 2024), it is outside the lifecycle policy. Here’s how you can check:
    a) If you have access to Esper Software Updates in your console, you can view the agent version along with its release date and the number of devices running that version.
    b) If you don’t have access to Esper Software Updates, go to the Devices & Groups table, ensure the Esper Agent Version column is added, and download the report to check which devices are on v7.14.1284 or below.
    c) If you need assistance, reach out to Esper—we’ll be happy to help.
• Grace Period for Migration
  • We understand that transitioning to a new version takes time, so we are providing a 6-month grace period for deprecated agent versions.
  • However, we strongly recommend updating as soon as possible to benefit from new features, stability improvements, and security enhancements. Esper can assist you throughout this transition.
• Test Before You Deploy
  • If you have access to Esper Software Updates, you can test the latest Esper Agent versions before rolling them out to all devices.
  • Use the Pipeline feature in Esper Software Updates to test updates on a subset of devices before deploying them fleet-wide.
  • We recommend updating to the latest available version unless you have a specific requirement for a different version.
• Deploy the Update
  • Once you have validated and tested the new version, use Pipelines to roll it out in a staged manner across your fleet.
  • If you prefer, simply enable automatic updates to ensure your devices always stay on the latest version.
  • If you don’t have access to Esper Software Updates, contact Esper, and we will help you test and deploy the latest versions.
• Need Help? Reach Out!
  • If you encounter any issues or need guidance on the update process, reach out to Esper. We’ll work with you to provide a clear upgrade path and ensure a smooth rollout.

8. FAQs

Q: What happens if I don’t update the agent version after the end of the transition period?
A: You may encounter compatibility issues and reduced performance. Esper will no longer provide maintenance or assistance with legacy versions, and a 30% charge on the per-device cost will be applied for continued use beyond the transition period.

Q: How will I know when my agent version is approaching the end of its lifecycle?
A: You can see the release date of the Esper agent on the console.

Q: Can I opt out of automatic updates but still stay compliant with the policy?
A: Yes, but it is your responsibility to manually update agent versions within the active support period to ensure compliance.

Q: I am not able to update the Esper Agent version through Esper Software Updates. What should I do?
A: Contact your administrator to access Esper Software Updates. In certain cases, a lock may have been applied to the tenant. In that case, reach out to Esper Support or your account manager. 

We value your cooperation in adhering to this policy, which enables us to deliver a high-quality, secure, and innovative experience for all Esper customers. If you have questions or need assistance, please contact Esper Support.

Effective Date: [Feb 12, 2025]

Updated Date: Feb 12, 2025