Agent tasks modify or restore Agents in various ways. The operations of Update Agent Configuration, Reinstall Agent, and Reset Agent Aliases are accessible through context menus for individual Agents, Monitoring Categories, or multiple Agents as illustrated below. Not all operations are relevant for Virtual Agents.
Reinstall Agent
This operation will reinstall Agent binaries. It will attempt to use the Agent listening port to transfer files, but if unavailable, the operation will then try to use RPC to authenticate and connect to the default: ADMIN$ share like an initial Service Agent install. Reinstall Agent will create an update log, and will stop and start the Agent service.
This operation applies only to Service Agents.
Restart Agent
This operation will restart the ELM Agent service.
This operation applies only to Service Agents. It will fail if the Service Agent is not running.
Update Agent Configuration
There are 2 copies of a Service Agent's configuration, one in the ELM Server and one in the Agent. If the two do not match, the copy in the ELM Server is considered the authority. During normal operation, the ELM Server will automatically send configuration updates to Service Agents within about 5 minutes, depending on system activity, network latency, number of Agents needing updates, etc. The Update Agent Configuration operation allows an ELM administrator to manually refresh the configuration without waiting the default 5 minutes.
This operation applies only to Service Agents.
Replace All Agent Configurations
Similar to the Update Agent Configuration, the Replace Agent Configurations operation allows an ELM administrator to manually refresh the configuration without waiting the default 5 minutes however using this option will delete the old configuration (tntagent.dat) and replace it with a new copy.
This operation applies only to Service Agents.
Add to Maintenance Category
This options allows you to assign All or selected agents to a Maintenance category.
Reset Agent Aliases (Right click an Agent in the results pain)
This operation will refresh the SV_Aliases property for an Agent using the name resolution mechanism of the OS hosting the ELM Server. The SV_Aliases list is the primary source of Agent identity for the ELM Server and includes the IP address(es), and the fully qualified domain name (FQDN) for an Agent. A reset is occasionally needed when an ip address or FQDN is assigned to the wrong agent. This does not affect the NetBIOS name of the agent.
Resolution for an agent is based on the following order:
The ELM Server first checks to see what was last successful, this could be the agent name or the ip address.
If resolution fails, it then checks the agent name.
If that fails, it then checks the FQDN in the aliases list.
If that fails, it then checks the IP address in the aliases list.
This operation applies to Service Agents, Virtual Agents, and IP Virtual Agents.