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

Account Permissions for Installing SolarWinds Agent on Windows/Linux Servers

I understand this is basic knowledge, but I wanted to ask about the account permissions required to install the SolarWinds agent on Windows and Linux servers.

While I know the agent can be installed using the SolarWinds local admin account, I am attempting to install it using a Windows domain account. Could you clarify what specific rights are needed for this account on the Windows server to successfully install the agent?

Additionally, if a domain account or local aaccount is created for this purpose, what permissions should be assigned to it? Also, what impact, if any, would occur on agent monitoring if the domain account's password expires?

Find more posts tagged with

Accepted answers

All comments

vinay.by

You have the details required on the below mentioned link (Please note: But then it doesn't provide the details to the extent that you are looking for with respect to bare minimum account privileges - its best to raise a vendor support case)

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-requirements-sw476.htm#Faq-AuthMethod

__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT

mesverrum

I can answer your question about the domain account expiring, it wont impact anything.

The account used to deploy the software initially is simply used to install the software the one time, so it has to be an admin. Maybe there is some combination of permissions for a less than admin account to install software in Windows, but I've never heard of such a thing. Same on Linux, if you can't install software then you can't deploy the agent.

After the agent install is complete it will run under a different account, it does not store the creds that were used to set it up, it creates it's own account on Linux and for Windows it runs under Local System.

yer

I went through that. My team had to create a local account for me because we weren't successful with the domain account, even after following the steps provided by SolarWinds. What we did was create a local account and give me admin access.

We follow these step

Tips for creating a non-administrator user for SAM application monitor polling to aid in troubleshooting by SolarWinds Support

This is when we where trying to use a domain user account with local admin access per workstation
Local Admin Account (not users)
RUN lusrmgr.msc
Add user in Groups: Performance Monitor Users and Distributed COM Users
RUN compmgmt.msc
Add the user to the Authenticated Users off of Root (compmgmt.msc > WMI Control>Properties>Security tab > Root > Security > add user here).
Allow Enable Account and Remote Enable permissions
From the 'Applies to' drop-down list, select 'This namespace and subnamespaces'
5. RUN dcomcnfg (DCOM configuration console)
6. Right-click My Computer, and select Properties. Switch to the COM Security tab and grant the following permissions: Under Launch and Activate Permissions, select the account and grant Remote Launch and Remote Activation permissions. (If the account is missing, add the user.) Under Access Permissions, select the account and grant Remote Access permissions. (If the account is missing, add the user.)

But at the end we ended with a local admin account even though the workstations are in a domain. I also contacted SolarWinds, and at that time they will not have a solution for me. I hope this help you

brscott

There might be something else interfering with your install. I install the agent using a domain account on servers all the time and have done so on every version from 10.something to 2024.1. The domain account is in the local admins group. I just copy the MSI to the server and double click it.

In versions before 2023.x I was able to run the agent as a limited (non-admin) user instead of local system, but that changed somewhere around version 2023.x and now I can only get it to run as local system.