How to handle outdated software in EPM macOS

Some outdated software presents limitations that prevent normal updates on macOS when EPM is active.
The most common issues include:

• Lack of request for administrative privileges during the update.
• Dependence on privileged local paths.
• Unsigned binaries, which may be quarantined by the operating system.

This guide explains how to handle these cases and guide the user with safe alternatives.

Requirements

• EPM macOS Client installed and active.
• Access to EPM policy settings.
• User permission to request support in case of incompatibility.

How to identify outdated software

1. Check if the software fails when attempting to update.
2. Observe if no administrative privilege request is made even when necessary.
3. Confirm the version in use and compare it with more recent releases from the vendor.

How to handle specific cases

1. IntelliJ

   • Issue: does not request administrative privileges when updating.
   • Solution: use IntelliJ Toolbox, which allows installing and updating versions in the user directory. This avoids dependency on administrative permissions.

2. Rancher (version 1.9.1)

   • Issue: relies on a privileged local path and lacks a digital signature, preventing integration with EPM.
   • Solution: update to a more recent version that does not depend on privileged paths.

3. Other outdated and unsigned software

   • Issue: execution blocked by macOS.
   • Solution: apply the quarantine removal procedure to allow controlled execution of the binary.