How to migrate agents to another VSA instance

Question

How can I migrate agents from one VSA server to another?

Answer

If migrating to a new server which is a replica of the original server, agents can be re-directed using Agent > Check-in Control page. On both the new and old VSA servers, set Primary Kserverto the address of the new server.

If migrating to a brand new or separate VSA instance, it is necessary to deploy a new agent using an install package created from the instance you are migrating to. This can be done using an agent procedure from the original VSA instance.

7) Select the file "Procedure Deploy agent for new VSA.xml" which is attached to this KB article - this will create an agent procedure called "Deploy agent for new VSA"

8) Edit the agent procedure and replace the web page URL in step 2 with the link you copied to the clipboard in step 4:

9) Save the procedure and schedule it on agents that need to be migrated. Please note that each agent will download 36 MB from the VSA server. To avoid bandwidth issues, use Distribution window to prevent too many concurrent downloads. You may also consider deploying the installer to a LAN share on larger sites and modifying the procedure to run it from there instead of downloading from VSA.

10) Once the agents have checked into the new VSA, the "old" agent can be removed using Agent > Install Agents > Delete page

Maintaining org/group structure

By default, new agents check into "unnamed" organisation, unless specified when creating the agent install package. If you want to maintain the same org/group structure on the new VSA after migration, the organisations and groups must be re-created manually. Migrated agents can then be assigned to correct groups in one of the following ways:

- Create install package for each group, specifying the group to install the agent into

- Use System > System Preferences > Naming Policyfunction to specify group membership based on connection gateway or IP address range