Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Server Automation10.60

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

Install the SA Agent using ADT

This section describes how to install the SA Agent on servers using the Agent Deployment Tool (ADT).

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

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 Client, select the servers on which you want to install the SA agent:

under Devices > Servers > SA Agent Installation
under Devices > Servers > All Managed Servers
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. The servers must be powered on. Otherwise the Install SA Agent menu item will be disabled. See Server status icons.

From the Actions menu, select Install SA Agent. This displays the Install SA Agent wizard:
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.
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 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, allows you to log in as a non-root user and escalates your privileges using either the su or sudo command.
  
  To deploy agents as non-root users:
Select one of the following deployment actions:
- Verify installation prerequisites
- Verify prerequisites and copy agent installer to servers
  
  Enable the Download Agent Bootstrap Certificate option to make the bootstrap certificate available in the same location as the Agent installer.
- Verify prerequisites, copy installer, and install agent
Optionally, specify the agent installer options and advanced options to control the way the agent is installed on a server. For more information, see SA Agent installation - Installer options and SA Agent installation - Advanced options.
Click Start Job to perform your selected actions.
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 a managed server and generate reports on agent installation status. See View SA Agent information.
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.

Send Help Center feedback