Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Orion Platform > Network Automation Manager > Network Automation Manager Installation Guide > Requirements > Optional requirements > Agent requirements

Agent requirements

Created by Caroline Juszczak, last modified by Caroline Juszczak on Mar 12, 2018

Views: 5,411 Votes: 4 Revisions: 7
  • Windows agents run as a service.
  • Linux agents run as a service daemon.

Before you deploy agents to a target computer, review the following system requirements for the remote computer.

  • Approximately 100 MB of hard drive space on the target computer, for installation only
Type Windows Requirements Linux
Operating System
  • Windows Server 2016
  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2008 R2 SP1
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows 7, Windows 7 SP1
  • Windows 8, Windows 8.1
  • Windows 10

Only Pro, Enterprise, and Ultimate workstation operating systems editions are supported.

  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 7
  • CentOS 5
  • CentOS 6
  • CentOS 7
  • SUSE Linux Enterprise Server 10
  • SUSE Linux Enterprise Server 11
  • SUSE Linux Enterprise Server 12
  • Ubuntu 14, 64-bit only
  • Amazon AMI, 64-bit only
Other Windows software

The following software packages are installed by the agent installer if necessary:

  • Microsoft Visual C++ 2013 Redistributable Package for 32-bit or 64-bit
  • .NET Framework 4.0 (You must install this manually if you are installing an agent on Windows Server 2008 R2 or earlier or Windows Core)
  • .NET Framework 4.5 (Required for Windows Server 2008 R2 SP1 and later)

You may need to install the following manually:

  • Python 2, versions 2.4.3 and later

Python 3 is not supported


The VeriSign Root Certificate Authority (CA) must be current. This is required because the agent software is signed using a VeriSign certificate. To install a certificate, see Certificates and the agent.

After the agent is installed, it runs as a Local System account and does not require administrative permissions to function.

Account permissions

If you want to deploy agents from the Orion server, the following requirements must be met:

  • The account used for remote deployment must have access to the administrative share on the target computer: \\<hostname_or_ip>\admin$\temp.
  • User Account Control (UAC) must either be disabled on the target computer, or the built-in Administrator account must be used.
  • You may need to disable UAC remote restrictions.
  • Other remote or mass deployment methods do not have the same requirements.
  • An account that can connect remotely through SSH.
  • An account that can install software and create a user and group.
  • The Orion Web Console must be accessible from the target Linux machine.



Agent resource consumption

Resource Consumption
CPU Less than 1% on average under normal operating conditions (0.24% on average)
Memory 10 - 100 MB, depending on the number and types of jobs

Roughly 20% (on average) of the bandwidth consumed by the WMI protocol for transmission of the same information

For example, Agent: 1.3 kB/s versus WMI at 5.3 kB/s

Storage 100 MB when installed

A single polling engine can support up to 1,000 agents.

Some Linux distributions, such as CentOS, log all cron jobs, including jobs that ensure the agent service is still up and responding. The log file can become large quickly. If your distribution logs all cron jobs, ensure that you use a tool such as logrotate to keep your log files to a manageable size.

Agent port requirements on the remote computer

Port Communication
OS Description
17778 Agent-initiated



Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent.
17791 Agent-initiated Windows 2008 R2 Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent. This must be opened if the remote computers you monitor run Windows 2008 R2.


Server-initiated All Used to communicate with the Orion server. This must be open on the remote computer.
135 (inbound) Either Windows (DCE/RPC Locator service) Microsoft EPMAP. This port must be open on the client computer for remote deployment.
445 (inbound) Either Windows Microsoft-DS SMB file sharing. This port must be open on the client computer (inbound) for remote deployment.
22 Either Linux (TCP) Used to install the agent on Linux computers through SSH and SFTP or SCP. TCP port 22 (outbound) must be open on the Orion server or additional polling engine and open (inbound) on the computer you want to monitor.
Last modified