Version Specific Application Policies

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Endpoint Privilege Manager (EPM) Articles
2 min read
L0 Member
No ratings

When functionality changes between EPM agent releases, you may need to apply different policy logic based on the agent version. This procedure ensures that version-specific behaviors are isolated and prioritized correctly.

This document defines an approach whereby release-specific application policies can be defined. In this example, the policies are shown to be specific to release 26.2.1. However, the actual “Agent Version” used can be changed depending on the specific upgrade being performed

 

Steps

Step 1: Create a Dynamic Endpoint Group

  1. Navigate to Endpoints > Endpoint Groups and click Create Endpoint Group.

  2. Name: Agents - Version 26.2.1 (Use a descriptive name).

  3. Type: Select Dynamic.

  4. Rule Definition:

    • Property: Agent Version

    • Operator: Starts With (Recommended over "Equals" to account for minor build variations).

    • Value: 26.2.1

Step 2: Duplicate and Adjust Impacted Policies

  1. Identify the policy requiring a version-specific change.

  2. Select Duplicate from the policy actions.

  3. Rename: Append the version to the name (e.g., Elevate Developer Tools - v26.2.1).

  4. Priority: Increase the priority so this policy is evaluated before the standard existing policy.

Step 3: Target the Policy

  1. In the new policy, scroll to the Targets section.

  2. Add the Dynamic Group created in Step 1.

  3. Important Logic Note:

    • Targets across different categories (e.g., AD Computer Groups AND Endpoint Groups) are combined using AND logic.

    • Targets within the same category are combined using OR logic.

    • Result: The policy will only apply if the computer is in the specified AD Group AND running the specified Agent Version

Note: If the "old" policy has a very broad target (like "All Computers"), it is recommended to add the new Version 26.2.1 Dynamic Group as an Exclusion in that old policy. This ensures a clear division and prevents an agent from potentially matching both sets of criteria.

Step 4: Validate and Roll Out

  1. Test: Upgrade a small "Pilot" group of agents to the new version.

  2. Verify: Use the Policy Audit on the endpoint to confirm the new version-specific policy is the one being applied.

  3. Cleanup: Once all agents are eventually upgraded to the new version, you can remove the version-specific policy and remain with the original policy definition.



Rate this article: