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

Installing a Orion AGENT in Windows infrastructure ..

When installing the agent on a Windows Core Server, you must install .NET Framework 4.5 or later, the latest Windows service pack, and critical updates.

Prerequisites to installing an agent on Windows Core

Start WoW64.
Start the .NET 2.0 layer.
Start the .NET 2.0 layer for WoW64.
Download and install the .NET framework from www.microsoft.com.

By default, no web browser is installed with Windows Core. Consider transferring the necessary files with FTP or a flash drive.

After the .NET Framework is installed, you may need to reboot the host server. The agent can then be deployed to the host server and operate normally.

Requirements for manual agent deployment

Agent-initiated communication:

The poller must have a public IP address which is visible from the node with the agent installed. Ports 17778 (outbound) on the agent machine and 17778 (inbound) on your Orion Platform polling engine must both be open.

Server-initiated communication:

The node with the agent installed must have a public IP address. Port 17790 must be open. You must also connect the agent to the Orion server by clicking Settings > All Settings in the menu bar. Under Node & Group Management go to Manage Agents > Add Agent > Connect to a previously installed agent > Next. Enter the name, IP address, and port number for the agent and click Server-initiated communication.

Install through the command prompt

Click Settings > All Settings in the menu bar.
Under Product Specific Settings, click Agent & Remote Collector. Then, on the Agent Management view, click Download Agent Software.

In Orion Platform 2020.2 and earlier, click Agent Settings to get to the Agent Management view with the Download Agent Software link.

Click Windows, and click Next.
Click Mass Deploy to Multiple Machines, and click Next.
Download the MSI and MST files.
Run a command prompt as administrator from the context menu.
Enter the following command:

msiexec /i "SolarWinds-Agent.msi" TRANSFORMS="SolarWinds-Agent.mst"

When the installation is successful and communication between the agent and the Orion server is successful, the agent is listed on the Manage Agents page.

Find more posts tagged with

Comments

KMSigma.SWI

I want to clarify a few points from the above post.

Your monitored servers do NOT need a public IP address. They just need a way to communicate with the Orion server. Depending on the communication method chosen (agent- vs. server-initiated), they will need a few firewall ports opened up. All of this is detailed in SolarWinds Orion agent requirements.

If you have a large, domain-based infrastructure, the way I would recommend to handle multiple agent installations is via Group Policy. You can put whatever filters you want on the Group Policy definition (only servers running core and running at least Windows Server 2016 is one such example). Then you use the same MSI and MST files as listed above for the installation. The Group Policy mechanism handles the install and transform for you.