Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Best practice in configuring and installing Linux agent with always changing root password?

When installing a new Linux agent on the newly deployed Linux host using this method:

How can I ensure that I check and verify the Agent is correctly polling the Linux node?

Because the company's security policy requires the root user account password to be rotated every 24 hours.

Find more posts tagged with

Alert

orion

Accepted answers

All comments

jose.barbosareis

This option is only to deploy the agent, after installed it runs under swiagent account.

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-linux-agent-credential-privileges.htm

"Service account privileges

When the agent software is installed, we create a service account (SWIAgent), and add it to its own group.

This account does not have remote access privileges and cannot be used to log in to the computer.

The service account is used to run the swiagentd service. When updating the agent, a second service runs (swiagentd.update) for the duration of the update.

The service account and group are removed when the agent is deleted from the node.

For SAM users, if you do not enter credentials or select Inherit from node, the monitor executes the script under the agent credentials (swiagent). These credentials may not have the elevated permissions required for executing scripts."

After installed, you can check the charts if they are being populated with datapoints so the data is being polled and stored in the database.