Objects exported from ePolicy Orchestrator that reference tags don't reference the correct tag when imported to a different ePO server

Technical Articles ID: KB85814
Last Modified: 2023-07-25 08:59:36 Etc/GMT

Environment

ePolicy Orchestrator (ePO) 5.x

Problem

If you export objects from the ePO Server that reference a tag and try to import those objects to another ePO Server, either of the following issues might result:

The tag reference might be missing entirely
It might reference the wrong tag even if the correct tag name exists.

This issue might affect these exported objects:

Policy Assignment Rules
Reports and Queries
Server Tasks
Client Tasks
Automatic Responses

Cause

Objects exported from ePO that reference a tag do so based on the ID field in the ePO database table that holds the tag.

The objects aren't referenced using tag name. The ID field in the ePO database is iterated chronologically when the tags are created.

Objects exported from ePO Server A and imported to ePO Server B might not reference the same tag, unless the tags are created in the same order on both ePO servers.

Solution

The resolution for this issue requires an architectural change in ePO; so it isn't feasible to address it in a Proof of Concept (POC) build, hotfix, or update release.

In the interim, implement the Workaround below.

Workaround

After you import the object from ePO server A to ePO server B, examine it and verify that the tag reference is correct. If it isn't, edit the object and reassert the proper tag association.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Objects exported from ePolicy Orchestrator that reference tags don't reference the correct tag when imported to a different ePO server

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Title

Title

Knowledge Center

Objects exported from ePolicy Orchestrator that reference tags don't reference the correct tag when imported to a different ePO server

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Choose your region

Title

Title