Use > Server Automation > Manage the Server Agent > Install the SA Agent

Install the SA Agent

This section describes how to install the SA agent on servers to bring under SA management.

The SA Client shows agentless servers with the server icon . See Server status icons.

Agentless servers may be physical servers that are not running the agent, or they may be virtual machines (VMs) not running the agent, but managed by a virtualization service. For more information, see "Virtualization management" in the SA 10.51 Use section.

  1. In the SA Client, under Devices > SA Agent Installation, select the servers on which you want to install the SA agent. See Discover agentless servers.

    Or under Devices > All Managed Servers, select the servers on which you want to install the SA agent.

    Or under the Virtualization tab, select the VMs on which you want to install the agent. All VMs are managed under a virtualization service.

    The server icon indicates agentless servers. See Server status icons.
    The servers must be powered on. Otherwise the Install SA Agent menu item will be disabled.
  2. From the Actions menu, select Install SA Agent. This displays the Install SA Agent dialog box as shown in the following figure.

    Install SA Agent dialog

  3. Select a network protocol to use for connecting to the server from the drop-down list.

    In most cases, choosing Select Automatically to allow SA to select an appropriate protocol for each server is recommended.
  4. Enter a user name and password to use for logging into the managed server.

    For Windows-based systems, specify the Windows administrator user name and password.

    For UNIX systems, specify a root user and password. If logging in as root is not permitted, select the checkbox Become root (UNIX). Select Supply root password and enter the password, or select Use sudo if sudo access is enabled for that account.

    If you log in using sudo, the sudo user’s configuration file (typically /etc/sudoers) must allow the account to run any command with root privileges. This is typically accomplished by using the “ALL” alias in the sudoers file.

    If you are unable to deploy the agent to a UNIX server by logging in as root, the system you are deploying to may be configured to disallow direct root logins. In such cases SA allows you to log in as a non-root user and then escalates your privileges via either the “su” command or the “sudo” command.

    Perform the following steps to deploy agents as a non-root user:
    1. Enter the unprivileged user name in the Username field to log into the server.
    2. Enter the unprivileged password in the Password field.
    3. Select the Become root (UNIX) checkbox. Select “Supply root password” and enter the password or select “Use sudo”. If you use sudo, the unprivileged account must be able to run any command as root.
  5. Select one of the following deployment actions:
    • Verify installation prerequisites.
    • Verify prerequisites and copy agent installer to servers.
    • Verify prerequisites, copy installer, and install agent.

    See Setting agent installation actions for each server for more information.

  6. Specify the agent installer options to control the way the agent is installed on a server. See Agent Installer options for more information.
  7. Select OK to perform your selected actions.
  8. After the agent installation is complete, the SA Client displays the results and updates the status icons for the servers. You can view information on an unmanaged server and generate reports on agent installation status. See Reports on Agent installation for more information.
  9. You will see a checkbox for enabling the --r option. Resets the Agent configuration file to the default settings.Specifies the path to the RPM handler to use for RPM operations. Use this option, when an RPM handler is already installed on the server.If an RPM handler is not already installed on the server, use the --withrpm option instead to install one.It is not necessary to use this option with the --withrpm option.