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
Store

Solarwinds Agent - Account requirements during Automatic Agent upgrade

Dear Solarwinds Experts,

In our environment we have unix and windows servers and so we are planning to monitor them using SAM , through solarwinds agent.

For installation in Windows and unix , It is clear that the requirement is to have a Admin privilege account .

Once after installation, Windows agent will run under system local account (NT AUTHORITY\SYSTEM)

Linux agent, during its installation it will create a local user swiagent, and further it runs on same account.

So for future agent upgrades, Do i still need any account with Admin privilege, or it will go thorough the accounts agents currently using?

@aLTeReGo

Find more posts tagged with

Accepted answers

aLTeReGo

@dhinagar_j wrote:
Dear Solarwinds Experts,
In our environment we have unix and windows servers and so we are planning to monitor them using SAM , through solarwinds agent.
For installation in Windows and unix , It is clear that the requirement is to have a Admin privilege account .
Once after installation, Windows agent will run under system local account (NT AUTHORITY\SYSTEM)
Linux agent, during its installation it will create a local user swiagent, and further it runs on same account.
So for future agent upgrades, Do i still need any account with Admin privilege, or it will go thorough the accounts agents currently using?
@aLTeReGo

Once the Agent is deployed, the privileged credentials are no longer used. In fact, that is why they aren't saved. You can delete that account, change its password, etc. and the Agent will remain completely unaffected, even through upgrades.

All comments

HerrDoktor

From my experience the Agent is Updated without the further need of entering admin credentials. I would agree with your assumption that the agent-update is using the credentials under which the agent itself is currently running.

I never had to enter any further credentials when performing the agent update with my clients.

be aware that the latest agent is installing .Net 4.8 which might not be compatible with some of your applications, check that before automatically updating the agents

dhinagar_j

@HerrDoktor Thanks for your response,

In agent initiated setup, i will open firewall port 17778 for inbound traffic at Polling engine .

Specific to these Agent update scenarios, Do we need to open port 17790 at target system,

HerrDoktor

From my understanding you also need port 135 and 445 on the Agent Machine Open to Update (Windows) . I am not sure about Linux, but I guess you need SSH (22) open on Linux Boxes.

aLTeReGo

@dhinagar_j wrote:
Dear Solarwinds Experts,
In our environment we have unix and windows servers and so we are planning to monitor them using SAM , through solarwinds agent.
For installation in Windows and unix , It is clear that the requirement is to have a Admin privilege account .
Once after installation, Windows agent will run under system local account (NT AUTHORITY\SYSTEM)
Linux agent, during its installation it will create a local user swiagent, and further it runs on same account.
So for future agent upgrades, Do i still need any account with Admin privilege, or it will go thorough the accounts agents currently using?
@aLTeReGo