References > References > Agents > Use a group policy to migrate agents

Use a group policy to migrate agents on Windows

You can use a group policy to change the connection settings of the agents to the new instance of your Orion server. Use this method if you have one or a few agents deployed.

It can take up to 15 minutes for an agent to successfully connect to the new Orion server.

  1. After you migrate your server, create a domain-based Group Policy Object (GPO). You can use this Administrative Template (.admx) file on THWACK.
  2. Copy the Administrative Template to the appropriate directory in the Central Store, and create the GPO within the Group Policy Management Console. For more information, search for "Editing Domain-Based GPOs Using ADMX Files" at http://technet.microsoft.com.
  3. Ensure the group policy will apply to the computer objects where the agent is installed. This can be done by linking to the appropriate Organizational Unit (OU) or filtering to specific computer objects or groups.
  4. Ensure the policy is updated on the target computers.
    1. Open a command prompt in the Administrator context. (Right-click cmd.exe and select, Run as Administrator.)
    2. Enter gpupdate /force and then press Enter.

The following registry key is created when the GPO is applied:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\SolarWinds\Agent

You can create your own Group Policy Object by editing the following registry key and providing the correct values: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\SolarWinds\Agent.

 

Registry Value Name

Registry Type

Value

Default

TargetHost

REG_SZ

Enter the name of the Orion server to which the agent reports

 

TargetIp

REG_SZ

Enter the IP address of the Orion server to which the agent reports

 

TargetPort

REG_DWORD

The port used for agent communication

17778