Runtime Environments

Back Next

Migrating a Secure Agent

You might want to migrate a Secure Agent from one machine to another, for example, when the Secure Agent runs on a virtual machine and you want to clone the machine. To migrate a Secure Agent, download and install the Secure Agent onto the new machine, and then add the new agent to the original Secure Agent group.

Don’t start and run an existing Secure Agent on a cloned machine. If you do this, the agent might not start after a product upgrade.

Verify that the original Secure Agent is up and running.

Download and install the Secure Agent onto the new machine.

Remove the new Secure Agent from its Secure Agent group.

When you do this, the agent is added to a group named “Unassigned Agents.” You can add any unassigned agent to a Secure Agent group.

Add the new Secure Agent to the original Secure Agent group.

This ensures that connections and jobs that use the original Secure Agent group as the runtime environment continue to run after migration.

For more information about adding and removing agents from a Secure Agent group, see Working with Secure Agent groups.

If you store connection properties on the original Secure Agent, update the connection credentials on the

Organization

page and select the new Secure Agent.

Optionally, remove the original Secure Agent from its Secure Agent group, and then stop the agent on the original machine and uninstall it.

Rename Saved Search

Table of Contents

Runtime Environments

Runtime Environments

Migrating a Secure Agent

Migrating a Secure Agent