Documentation forSolarWinds Observability SaaS

Reinstall the Agent

Reinstall the Agent used for adding hosts via a ready-made script

  1. On the server hosting the SolarWinds Observability Agent, uninstall the Agent. See Uninstall the Agent.

  2. Remove the SolarWinds Observability Agent from SolarWinds Observability SaaS.

    1. In SolarWinds Observability SaaS, click Settings > Agents.

    2. In Agents, locate the entity hosting the Agent.

    3. Click the vertical ellipsis at the end of the row, and then click Delete.

      See Remove the Agent from SolarWinds Observability SaaS.

  3. Install Agent. See Add a self-managed host.

Reinstall the Agent used by the Network Collector via a ready-made PowerShell script

  1. On the server hosting the SolarWinds Observability Agent, uninstall the Agent. See Uninstall the Agent.

  2. Remove the SolarWinds Observability Agent from SolarWinds Observability SaaS.

    1. In SolarWinds Observability SaaS, click Settings > Agents.

    2. In Agents, locate the entity hosting the Agent.

    3. Click the vertical ellipsis at the end of the row, and then click Delete.

      See Remove the Agent from SolarWinds Observability SaaS.

  3. Install the Agent:

    1. In SolarWinds Observability SaaS, click Add Data in the upper-right corner.

    2. Click Network Device.

    3. On Add Network Device, copy the PowerShell script.

    4. Run the script on the server hosting the Agent. Use PowerShell with administrator permissions.

Reinstall the Agent used by a host via the MSI file with parameters

If you prefer using the MSI file, add the additional parameter METADATA="role:host-monitoring". This parameter automatically adds the OTEL host monitoring plugin to this Agent.

  1. On the server hosting the SolarWinds Observability Agent, uninstall the Agent. See Uninstall the Agent.

  2. Remove the SolarWinds Observability Agent from SolarWinds Observability SaaS.

    1. In SolarWinds Observability SaaS, click Settings > Agents.

    2. In Agents, locate the entity hosting the Agent.

    3. Click the vertical ellipsis at the end of the row, and then click Delete.

      See Remove the Agent from SolarWinds Observability SaaS.

  3. Copy or create an API token (Ingestion type), found in the settings area of SolarWinds Observability SaaS. You will need it later. See API Tokens for details.

  4. Start PowerShell with administrator privileges.

  5. In the PowerShell console, go to the folder with uamsclient.msi.

  6. In the following command, replace ....... with the token copied previously, and then run the command. If you’re not using the default na-01 North American AWS data center, then add an additional SWO_URL parameter with root domain of your data center. See Data centers and endpoint URIs for more information.

    msiexec /i uamsclient.msi ACCESSTOKEN="........." METADATA="role:host-monitoring"

Reinstall the Agent used by Network Collector via the MSI file with parameters

If you prefer using the MSI file, add the additional parameter METADATA="role:SiteCollector".

The parameter role:SiteCollector is case sensitive and it should be typed or pasted exactly as it is in this document.

  1. On the server hosting the SolarWinds Observability Agent, uninstall the Agent. See Uninstall the Agent.

  2. Remove the SolarWinds Observability Agent from SolarWinds Observability SaaS.

    1. In SolarWinds Observability SaaS, click Settings > Agents.

    2. In Agents, locate the entity hosting the Agent.

    3. Click the vertical ellipsis at the end of the row, and then click Delete.

      See Remove the Agent from SolarWinds Observability SaaS.

  3. Copy or create an API token (Ingestion type), found in the settings area of SolarWinds Observability SaaS. You will need it later. See API Tokens for details.

  4. Start PowerShell with administrator privileges.

  5. In the PowerShell console, go to the folder with uamsclient.msi.

  6. In the following command, replace ....... with the token copied previously, and then run the command. If you’re not using the default na-01 North American AWS data center, then add an additional SWO_URL parameter with root domain of your data center. See Data centers and endpoint URIs for more information.

    msiexec /i uamsclient.msi ACCESSTOKEN="........." METADATA="role:SiteCollector"