Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Manage the Server Agent
- Permissions required for server discovery and agent installation
- Install the SA Agent
- Connect to WSUS at Agent install/upgrade
- Discove agentless servers
- Upgrade the SA Agent
- Set agent installation defaults
- Start and stop the SA Agent
- View SA Agent information
- Server discovery and agent installation
- Troubleshoot agent installation errors
- Communication between the server and SA Core
- Run server communication tests
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:
- Setting agent installation actions for each server
- Specifying login settings
- Agent installer command
- Reports on server status
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.
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.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to hpe_sa_docs@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: