Use > Server Automation > Manage the Server Agent > Server discovery and agent installation

About Server Discovery and Agent Installation

SA can install agents on a large number of servers through the SA Client. SA can identify servers on which to install an agent, specify the agent configurations for each server, select the login protocols to connect to each server, specify the agent installation options, install the agent and generate reports on agent installation status.

This section contains the following topics:

Discover agentless servers contains more information about how to install an agent.

Setting agent installation actions for each server

Once you have identified the servers, you can perform the following deployment actions:

  • Verify installation prerequisites including:
    • Checking for sufficient disk space for agent installation on the server.
    • Verifying that no other application is using port 1002.
    • Verifying if ports to the Gateway are accessible.
  • Copy the agent installer to servers.
  • Install the agent on the server.

Specifying login settings

When installing the SA agent, you can select the network protocols to connect to the server and specify the user name and password to log in to each server. Agent installation is performed as root on UNIX operating systems and as administrator on Windows operating systems so. SA attempts to log in to each of the selected servers with the specified user name and password and performs the specified deployment actions.

The agent requires administrator-level privileges (root on UNIX servers and administrator on Windows servers) to manage a server.

Agent installer command

You can use the agent installer command to manually install agents on servers. For more information, see Agent installation and upgrade utilities.

Reports on server status

After the SA agent is installed, the SA Client displays the results and updates the status icons for the servers as shown in the table Server status.

Server status

Icons

Server Status

The server is agentless, but reachable

The server is agentless and unreachable

The server is agent managed

The server failed prerequisite checks

The server passed prerequisite checks

The server passed prerequisite checks and the agent installer was copied to the server

The agent was successfully deployed

The agent was not successfully deployed

A server is considered to be managed when SA determines that the agent is listening for TCP connections on port 1002.

For a failed deployment action, you can view the errors on each server. You can also log in to the server and correct the errors.

You can also create the following reports:

  • All the servers in the current network scan
  • Selected servers in the current network scan
  • All the servers in the current network scan with successful deployments
  • Servers in the current network scan with failed deployments

You can save and export the reports to a CSV, HTML, or text format file.