Introduction

OpsRamp provides support for running the MSI agent with a non-admin user account, and there are two options available to achieve this.

• Default User
• Custom User

Refer the Document to install the Agent using command line Arguments.

Default User

Include the following flag as part of the agent installation configuration parameters.

/isnonadmin=YES

msiexec.exe /i {.msi file path in quotes} /quiet WRAPPED_ARGUMENTS=“/silent /apiserver=uatsp.api.uat-app.opsramp.net /key=xxxxxxxxx /secret=xxxxxxxxxxxx /clientid=xxxxxxxxxxxx /installedappid={installedappid} /logmonitorable=true /isnonadmin=YES”

Permissions

With default ‘opsrampuser’ account we are providing only the following two local group permissions.

• Performance Monitor Users
• Event Log Readers

Functionalities not supported for default user (opsrampuser)

We provide only two local group permissions to the default user as mentioned above. Therefore, the following functionalities will not work with the default user.

Administrative Permissions

Below functionalities require administrative privileges, if users desire access to them, ‘opsrampuser’ needs to be added to the administrative group.

• Windows OS Patching
• Antivirus scan and update
• Application Dashboard (few attributes may not appear which requires admin privilege)
• Below Remote Commands
  • Restart Remote Agent
  • Remote System Info
  • Execute a Command (remote device)

File Read Permissions

Below types of monitors require ‘opsrampuser’ to have read permissions to the configured folder/files.

• LogFile Monitoring
• File Check monitor
• File Size monitor

Scripts

Scripts (RBA, Task Execution, G2 monitoring RSE Scripts).
Depends on the command used inside the script and it requires right user permission to execute it.

Remote Consoles – RDP

RDP required “Remote desktop user” local group policy to make it work.

Log Management

Log Management requires ‘osprampuser’ to have read permissions to the configured folder/files.

Custom User

To install the agent as a custom user, follow these steps:

1. Add the credentials of an existing user account to the agent installation parameters, using the following flags:

   /isnonadmin=YES /domain=<Domain Name> /username=<user name> /password=<user password>

   Example

msiexec.exe /i {.msi file path in quotes} /quiet WRAPPED_ARGUMENTS="/silent /apiserver=uatsp.api.uat-app.opsramp.net /key=xxxxxxxxx /secret=xxxxxxxxxxxx /clientid=xxxxxxxxxxx /installedappid={installedappid} /logmonitorable=true /isnonadmin=YES /domain=<Domain Name> /username=<user name> /password=<user password>"

2. Specify either a local system user account or an Active Directory (AD) user account as the custom user.
3. If the device is not part of a domain, enter the device’s hostname as the domain name.