Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.4 Administrator Guide > Monitor with Orion agents in SAM > Migrate agents from one Orion instance to another for SAM

Migrate agents from one Orion instance to another for SAM

Table of contents
No headers

Updated: 3-9-2017

When you migrate your SolarWinds Orion server to a different computer, you may need to modify your agents so they communicate with the new server.

If any of the following have changed, you must modify your agents:

  • IP address
  • DNS
  • Database

Modify agents to point to the new server in one of the following ways:

  • Re-deploy the agents from the Orion server.
  • Manually change the Orion server IP address the agent uses using the Control Panel.
  • Use the Group Policy Administrative template to redirect existing agents to the new Orion server. This requires endpoints be joined to an active directory domain.

If you have not cloned your certificates, you must migrate them to the new server.

Last modified
13:48, 10 Mar 2017