Use > Server Automation > Agent installation and upgrade utilities > Overview of Agent installation using the CLI

Overview of Agent installation using the CLI

When you install Agents on existing servers, you should synchronize the local time on the servers with an external time-server that uses a network time protocol (NTP).

The Agent Installer can be invoked from the command line or within a script and can be operated unattended because user interaction is not required. The Agent Installer also retrieves cryptographic material, retrieves configuration information, and writes a configuration file and a log file.

The Agent installer installs the SA agent on your servers and makes them known to Server Automation so that they can be managed.

Installing an Agent on a server with a pre-built OS into Server Automation enables:

  • Baseline discovery of the operating system on the server.
  • Managing the baseline operating system, including patch management, when the operating system is defined in Server Automation with the Prepare Operating System Wizard.
  • Full provisioning and management capabilities for any new applications deployed on the server.

When installed, the Agent registers the server with the Model Repository. Server Automation assigns the server to a generic operating system that corresponds to the operating system that the Agent discovered during the installation. The server is assigned to a placeholder OS node.

Note
The Agent Installer can install Agents when a core is not available to a server. If a newly-installed Agent cannot contact a core, the Agent runs in a dormant mode. While dormant, it periodically attempts to contact the core. When the core becomes available, the Agent performs the initialization tasks, such as hardware and software registration, that usually take place when the Agent is first installed.

The server is tracked in the SA Client. However, the server operating system cannot be managed while the server is assigned to the generic operating system node. You must reassign the server to the operating system that was defined with the OS Provisioning feature.

The server is associated with the default facility for the local instance of Server Automation.

If the managed server’s IP address does not fall within a specified IP range, the server is associated with the default IP range group (Default). The default group is associated with the customer Not Assigned.

See Assigning a server to a customer for information about how servers are associated with customers.