MER for ePO allows an earlier version to be installed when a later version exists on the system

Technical Articles ID: KB94579
Last Modified: 2023-08-09 08:37:25 Etc/GMT

Environment

ePolicy Orchestrator (ePO) 5.10.x
Minimum Escalation Requirement (MER) tool
ePO-MER

Problem

You've already checked in MER for ePO 4.1 to the current branch. Then, you check in the MER for ePO 4.2 to a different branch (the Evaluation branch, for example). You schedule a task to install MER for ePO 4.2, and have a task to install MER for ePO 4.1. The following occurs:

Both versions are unexpectedly installed successfully.
Both versions show up in the ePO Product tab from the system tree.

Solution

Don't create a task to install two different ePO-MER versions. Delete the earlier version from the Primary Repository.

NOTE: After you've deployed both versions, a manual removal is needed on the systems that report both ePO-MER versions. If you need assistance, contact Technical Support.

To contact Technical Support, go to the Create a Service Request page and log on to the ServicePortal.

If you are a registered user, type your User ID and Password, and then click Log In.
If you are not a registered user, click Register and complete the fields to have your password and instructions emailed to you.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

MER for ePO allows an earlier version to be installed when a later version exists on the system

Environment

Problem

Solution

Affected Products

Languages:

Title

Title

Knowledge Center

MER for ePO allows an earlier version to be installed when a later version exists on the system

Environment

Problem

Solution

Affected Products

Languages:

Choose your region

Title

Title