Importing Policies

[User80967331]

For troubleshooting purpose, I would like to import an ENS policy from one system to another. Is there a way to import a policy into another system without overwriting the policy that is already there? I tried changing the name of the new policy - which makes it different in name to the existing policy but I still get that message that the existing one will be overwritten. Thanks

[cdinet · Accepted solution]

Are you exporting and importing just that one specific policy or all the policies for that category?  What I would suggest is duplicate your original policy that you want to export and when you duplicate it, then give it a different name, rather than renaming any existing policy (which might affect where it is assigned).  Then export just that policy and import it.  That should import successfully.

[User80967331]

That would work too. I actually did it the opposite. I duplicated and renamed the policy that I wanted to change then imported the new one. That way there was no conflicts.

Thanks for your response.

[User37568778]

in regard to this topic.

I have reinstall a fresh copy of epo into another server.

I've exported the Assigned client task policy on the current production server and tried importing into the new server. But this pops out.

Is there something wrong with my step?

[rackroyd]

The message "client task assignments could not be imported" is not a common one but is likely to be accurate in that either the xml is corrupted or has some read-only elements that prevent this function operating.

You would need to inspect the xml file directly, or also perhaps look for more detail in the ePO orion log at the time this was displayed.

Failing that, you might then need to bring it up as a McAfee support case.

[cdinet]

You might need to make sure you have the same extensions and software checked in that matches system you are importing from.