When moving data from one ePolicy Orchestrator server to another there are some data objects that can be easily exported and imported and some that have limitations.
The export and import limitations depend on the ePolicy Orchestrator software version and if the data is imported back to the same McAfee ePO server, or to a different server. These tables list the data export and import functionality and limitation.
Table 7-2 Export comparison between McAfee ePO 4.5, 4.6, and 5.0 servers
Data object Available to export from McAfee ePO...
...version 4.5 ...version 4.6 ...version 5.0
Agent Handler Assignments Yes Yes Yes
Agent Handler Settings
This does not include Agent Handler Assignments.
No No No
Automatic Responses Yes Yes Yes
Client Task Assignments No Yes Yes
Client Task Objects No Yes Yes
Contacts No No No
Dashboards No Yes Yes
Detected Systems Exceptions Yes Yes Yes
Detected Systems Settings
Policy Assignment Rules Yes Yes Yes
Policy Assignments No Yes Yes
Table 7-2 Export comparison between McAfee ePO 4.5, 4.6, and 5.0 servers (continued)
Data object Available to export from McAfee ePO...
...version 4.5 ...version 4.6 ...version 5.0 Server Settings
Tree Active Directory Sync No No No
Tree Sorting No No No
User Configured Options No No No
Users No No No
Table 7-3 Export functionality from McAfee ePO 4.5 to different 5.0 server
Data object Can be exported... Notes
...from McAfee
ePO 4.5 server ...to different McAfee ePO 5.0 server
Agent Handler Assignments Yes No ID use causes tree‑based
assignment location loss.
Automatic Responses Yes No The import is rejected.
Client Task Assignments No N/A
Distributed Repositories Yes Yes (but with
limitations) Unless the repositories contain the same content, the exclusion list might cause unexpected package selections.
Log Information No (except for No (except for
Table 7-3 Export functionality from McAfee ePO 4.5 to different 5.0 server (continued)
Data object Can be exported... Notes
...from McAfee
Policy Assignment Rules Yes No Unique IDs contained in the
export information and import are rejected.
Policy Assignments No N/A
Policy Objects Yes No The McAfee Agent
Repository policy might not
limitations) The exported file needs 'My Organization\' removed from each line before importing.
Tag Catalog Yes No Server‑specific data in
specific tags causes those tags to be unavailable after importing.
Tree Active Directory Sync No N/A
Tree Sorting No N/A
User Configured Options No N/A
7
Registered serversSharing objects between servers
Table 7-4 Export functionality from McAfee ePO 4.6 to different 5.0 server
Data object Can be exported... Notes
...from McAfee
ePO 4.6 server ...to different McAfee ePO 5.0 server
Agent Handler Assignments Yes No ID use causes tree‑based
assignment location loss.
Automatic Responses Yes No The import is rejected.
Client Task Assignments No N/A
Distributed Repositories Yes Yes (but with
limitations) Unless the repositories
Policy Assignment Rules Yes No Unique IDs contained in
the export information and import are rejected.
Policy Assignments No N/A
Policy Objects Yes No The McAfee Agent
Repository policy might not
Table 7-4 Export functionality from McAfee ePO 4.6 to different 5.0 server (continued)
Data object Can be exported... Notes
...from McAfee
limitations) The exported file needs 'My Organization\' removed from each line before importing,
Tag Catalog Yes No Server‑ specific data in
tags causes those Tags to be unavailable after importing.
Tree Active Directory Sync No N/A
Tree Sorting No N/A
User Configured Options No N/A
Users No N/A
Table 7-5 Export functionality from McAfee ePO 5.0 versus import functionality to different 5.0 server
Agent Handler Assignments Yes No ID use causes tree‑based
assignment location loss.
Automatic Responses Yes No ID use for applicable System
Tree nodes causes an incorrect
7
Registered serversSharing objects between servers
Table 7-5 Export functionality from McAfee ePO 5.0 versus import functionality to different
Client Task Assignments Yes Yes (but with
limitations) Broken inheritance tasks are lost and duplicate task assignments are created if tasks are imported before or after breaking inheritance.
Client Task Objects Yes Yes (but with
limitations) Master repository content must
Distributed Repositories Yes No The package exclusion list is
lost after import.
Log Information No (except for
rollup) No (except for rollup)
Permission Sets Yes Yes (but with
limitations) Permission sets must have the same System Tree structure and repository content.
Personal Settings No N/A
Policy Assignment Rules Yes No IDs cause servers to use
incorrect tags and registered servers.
Policy Assignments Yes No Multiple assignments of
multi‑slot policies at one node are not imported correctly.
Policy Objects Yes No The McAfee Agent Repository
policy might not contain the same settings for McAfee ePO servers and Agent Handlers as the old servers, Agent Handlers might not be present, and the policy might fail.
Table 7-5 Export functionality from McAfee ePO 5.0 versus import functionality to different
Server Tasks Yes Yes (but with
limitations)
Source Sites Yes Yes
System Tree Yes Yes
Tag Catalog Yes No Server‑specific data in tags
causes the tags to be unavailable after import
Tree Active Directory Sync No N/A
Tree Sorting No N/A
User Configured Options No N/A
Users No N/A
Table 7-6 McAfee ePO 5.0 Server Task export and import functionality Server task object Exportable to
different server Notes Tasks that include
queries Yes (but with
limitations) Duplicate tasks are created for multi‑used queries between tasks if they are imported at different times.
Tasks that include file
paths Yes (but with
limitations) File paths must match on servers or files might not be written (for example Files written to the D drive by exporting the server fail if the imported server does not have a D drive).
System Search No IDs used for groups and tags lead to a mismatch.
Run Tag Criteria No IDs used for tags lead to a mismatch.
Run Report No IDs used for queries might lead to a mismatch;
queries can contain server‑specific info.
7
Registered serversSharing objects between servers
Table 7-6 McAfee ePO 5.0 Server Task export and import functionality (continued) Server task object Exportable to
different server Notes Run Query ‑ Move
Systems No The IDs used probably cause a mismatch.
Run Query ‑ Exclude Tag No The IDs used probably cause a mismatch.
Run Query ‑ Detected
System Exceptions Yes (but with
limitations) The ID used for category selection probably causes mismatch
Run Query ‑ Deploy
McAfee Agent No Agent Handler‑ specific data might not be available to the importing server; the password is not kept in the exported file.
Run Query ‑ Clear Tag No The IDs used probably cause a mismatch.
Run Query ‑ Assign
Policy No The IDs used probably cause a mismatch and task
failure, even though the policy was imported by task.
Run Query ‑ Apply Tag No The IDs used probably cause a mismatch.
Run Query ‑ Add to
System Tree No The IDs used probably cause a mismatch.
Rollup No If the registered servers are selective, IDs are used
and can be mismatched; filtering properties may be server‑specific (Applied Policies).
Repository Replication Yes (but with
limitations) The repositories must have the same content or the task loses settings.
Repository Pull No The ID used for the source site might cause an issue. The repositories must have the same content or the task loses settings.
Purge X Yes (but with
limitations) If using a query to purge, the ID used for the query probably causes a mismatch between servers.
Export Queries No Queries can contain server‑specific data which make the queries incorrect after import.
Change Branch for
Package Yes (but with
limitations) The packages must have the same content or the task loses settings.
Active Directory Sync No The ID used for location, even if the tree structure is imported, probably causes a mismatch.