Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Agent switches to set Hostname

Agent switches to set Hostname

Table of contents
Created by James Nielsen, last modified by Erica Gill on Jul 24, 2017

Views: 1,437 Votes: 3 Revisions: 9


Agents sometimes consume more licenses because they contain multiple nic cards. Often, this is because they are choosing the wrong nic/hostname to use. This article provides information on switches to help choose the correct hostname.


LEM with Agent



  1. Connect to a machine reporting duplicate entries.
  2. Navigate to C:\Windows\SysWOW64\ContegoSPOP
  3. Edit the spop.conf file.
  4. Add the switch you would like to use (either the first, or third option below, typically) to the end of the file or as a new line.
    note:  only use one of the following three options. remove the one attempted, if trying another.
  5. Save the file.
  6. Restart the Solarwinds Log and Event Manager Agent service.
  7. Delete the duplicated node from the Nodes view on the LEM.


For a 32 bit system the switches below need to be added to the spop.conf file located in:



It is recomended to not use Notepad as it may not correctly read the carriage returns.


  1. This is typically the better option. You will want to go to those specific agents and have them use the switch to report their name by not using the hosts file.  First, have them type "hostname" (or "computername" on some OS's) on those boxes.  If this is the desired hostname to use then use this switch in the spop.conf:
    And look for this log line in the agent log:
    "Overriding local hostname to computername/hostname environment variable for local hostname: " + local_name
    or this if we could not get a valid hostname:
    "Overriding local hostname to computername/hostname environment variable failed to get a value, sticking with original local hostname value: " + local_name
  2. Otherwise, if option 1 does not yield the desired hostname to use, see if the manager can detect it for them.  Use this switch and it will prevent the agent from sending its host name.  The manager will then detect it.  FYI: If they are connecting through a firewall than it will detect the name of the firewall instead.
    And look for this log line in the agent log:
    "Overriding local hostname to empty string to trigger manager detection of local hostname"
    NOTE: if you set UseManagerDetectionOfLocalHost (option 2) it will override whatever value is set for UseLocalEnvironmentVariableForLocalHost (option 1).
  3. One additional property that was added as of 6.1.0 agents is a way to bind to a specific ip address or hostname by using "ForcedLocalAddress".
    This could be especially helpful if laptops are mobile within an office environment, using the wireless and/or wired ethernet connection as the computer is moved.
    ForcedLocalAddress=     (fill in the IP address of the laptop/server)
    ForcedLocalAddress=laptop-1     (fill in the hostname of the laptop/server)



Last modified