Use a group policy to migrate agents on Windows
This topic applies only to the following SolarWinds Platform products:
SolarWinds Observability Self-Hosted
DPAIM — LA — NAM — NPM — SAM — SCM — SRM — VMAN*
You can use a group policy to change the connection settings of the agents to the new instance of your SolarWinds Platform 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 SolarWinds Platform server.
- After you migrate your server, create a domain-based Group Policy Object (GPO). You can use this Administrative Template (.admx) file on THWACK.
- 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.
- 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.
- Ensure the policy is updated on the target computers.
- Open a command prompt in the Administrator context. (Right-click
cmd.exe
and select, Run as Administrator.) - Enter
gpupdate /force
and then press Enter.
- Open a command prompt in the Administrator context. (Right-click
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 SolarWinds Platform server to which the agent reports |
|
TargetIp |
REG_SZ |
Enter the IP address of the SolarWinds Platform server to which the agent reports |
|
TargetPort |
REG_DWORD |
The port used for agent communication |
17778 |