How to Set Up SolarWinds Monitoring Agent on Windows Server 2016

SolarWinds offers a suite of monitoring products, and its agent-based monitoring approach is central to platforms such as SolarWinds Server and Application Monitor (SAM) and the N-able N-central and N-sight Remote Monitoring and Management products. Installing the SolarWinds agent on a Windows Server 2016 host allows the platform to collect performance metrics, monitor services and processes, track event log entries, execute automated remediation scripts, and report on hardware health without requiring network-level polling for every check. This guide walks through deploying and configuring the SolarWinds Windows agent on a Windows Server 2016 system.

Before beginning, confirm that your SolarWinds platform version supports Windows Server 2016 as an agent target. You will need the agent installer package from your SolarWinds portal, the hostname or IP address of your SolarWinds management server, and a valid activation key or pre-shared key depending on your product version. Outbound TCP port 443 or the product-specific port must be open from the monitored server to the management server.

Step 1: Download the Agent Installer

Log in to your SolarWinds customer portal at my.solarwinds.com and download the Windows agent installer (MSI or EXE package) that matches your SolarWinds platform version. For N-central or N-sight, agents are downloaded directly from the management portal under the Devices or Agents section. Save the installer to a local path such as C:Installers on the target server.

Step 2: Verify Firewall Prerequisites

The agent communicates with the management server over specific ports. Verify that the Windows Firewall and any network-level firewalls permit outbound connections on the required ports. For SolarWinds SAM, the agent communicates on TCP 17778 by default. Use the Test-NetConnection PowerShell cmdlet to verify connectivity:

Test-NetConnection -ComputerName solarwinds.yourdomain.com -Port 17778

If TcpTestSucceeded returns False, open the required port in Windows Firewall:

New-NetFirewallRule -DisplayName "SolarWinds Agent Outbound" `
    -Direction Outbound `
    -Protocol TCP `
    -RemotePort 17778 `
    -Action Allow

Step 3: Install the Agent via Silent Installation

For large-scale deployments, use the silent installation command to install the agent without user interaction. The exact parameters vary by product version; the following example demonstrates a typical N-sight agent silent installation:

msiexec.exe /i "C:InstallersAgentInstaller.msi" /quiet /norestart `
    SERVERADDRESS=solarwinds.yourdomain.com `
    SERVERPORT=443 `
    ACTIVATIONKEY=YOUR-ACTIVATION-KEY-HERE

For a SAM agent, the installer is typically an EXE with its own silent switch:

SolarWinds-Agent-Installer.exe /S /v"/qn SERVER=solarwinds.yourdomain.com"

Consult the specific installation documentation for your product version to confirm the correct parameter syntax.

Step 4: Verify Agent Service Status

After installation, verify that the agent Windows service is running:

Get-Service -Name "SolarWinds Agent" | Select-Object Name, Status, StartType

The service name varies by product. It may appear as SolarWinds Agent, N-able Windows Agent, or a similar name. If the service is not running, start it and set it to automatic startup:

Set-Service -Name "SolarWinds Agent" -StartupType Automatic
Start-Service -Name "SolarWinds Agent"

Step 5: Confirm Registration in the Management Console

Log in to your SolarWinds management console and navigate to the device list or Discovered Devices section. The newly installed agent should appear within a few minutes as a pending or active device. Accept the device registration and assign it to the appropriate site, customer, or monitoring group. Once accepted, the management server pushes down the monitoring policy, which defines which checks will run on this server.

Step 6: Configure Monitoring Checks

From the management console, assign monitoring checks to the server. Common checks for a Windows Server 2016 host include CPU utilization threshold alerts, memory usage monitoring, disk space warnings on all NTFS volumes, Windows service availability monitoring for critical services such as Active Directory, DNS, DHCP, IIS, and SQL Server, and event log monitoring for critical and error-level events. For agent-based platforms, these checks run locally on the agent rather than polling the server over the network, which reduces latency and eliminates the need for open inbound ports from the monitoring server.

Step 7: Set Up Automated Remediation Scripts

One of the key advantages of agent-based monitoring is the ability to run automated remediation scripts when an alert fires. In the management console, create an automation policy that runs a PowerShell script on the monitored server when a specific check enters a failed state. For example, if a critical Windows service stops, the automation policy can attempt to restart it and log the action before escalating to a human technician:

$serviceName = "W32Time"
$svc = Get-Service -Name $serviceName
if ($svc.Status -ne "Running") {
    Start-Service -Name $serviceName
    Write-Output "Restarted $serviceName at $(Get-Date)"
}

Step 8: Update and Maintain the Agent

Keep the agent software current to benefit from bug fixes, security patches, and new monitoring capabilities. Most SolarWinds agent platforms support automatic agent updates pushed from the management console. Enable automatic agent updates in the management console settings to ensure all monitored servers remain on the latest supported agent version. Periodically review the agent version report in the console to identify any servers that failed to receive automatic updates and require manual intervention.

A properly configured SolarWinds agent transforms Windows Server 2016 monitoring from a reactive to a proactive discipline, giving your team visibility into performance degradation and service failures before they impact end users.