Introduction to SolarWinds Monitoring Agent on Windows Server 2019

SolarWinds is a leading provider of IT infrastructure monitoring software. SolarWinds N-central and SolarWinds Orion are the two primary platforms used in enterprise and managed service provider environments. N-central uses a lightweight agent installed on Windows Server 2019 endpoints to collect performance metrics, health checks, patch compliance data, and support remote management tasks. SolarWinds Orion uses an agentless WMI/SNMP polling model by default but can use the SolarWinds Agent for improved reliability in firewall-restricted or high-latency environments. This guide covers deploying the SolarWinds N-central agent on Windows Server 2019, configuring monitoring policies, and using the agent for patching and remote management.

SolarWinds Agent Architecture Overview

The SolarWinds N-central agent (also called the Windows Probe or N-central Agent) is a service installed on Windows Server 2019 that maintains a persistent connection to the N-central server. Unlike poll-based monitoring, the agent pushes data to the N-central server at configurable intervals and supports bidirectional communication for remote commands, script execution, and automated remediation. The agent communicates over TCP port 443 (HTTPS) to the N-central server, making it firewall-friendly for monitoring servers across the internet or in remote branch offices without VPN.

For SolarWinds Orion environments, the Orion agent runs as a Windows service and communicates with the Orion server over TCP port 17778 (HTTPS REST API). The agent supplements WMI polling by providing push-based metrics collection for scenarios where WMI polling is unreliable or the server is not domain-joined.

Downloading the SolarWinds N-central Agent

The N-central agent installer is downloaded directly from your N-central server. Log into the N-central web console. Navigate to Configuration > Customers/Sites and select the customer or site you are adding the server to. Under Add/Import > Import Windows Devices, click Download Agent. The downloaded installer (Agent_Setup.exe) is pre-configured with the N-central server address and the selected customer/site assignment, so no additional configuration is required during installation.

Alternatively, download the generic agent installer and configure it manually during deployment for mass rollout scenarios. The generic installer accepts command-line parameters for automated deployment:

Agent_Setup.exe /S /v"NCENTRAL_SERVER=ncentral.company.com CUSTOMER_ID=12345 SITE_ID=67890 JWT=eyJhbGciOiJSUzI1NiJ9..."

Installing the N-central Agent via PowerShell for Mass Deployment

For deploying the agent to multiple Windows Server 2019 machines, use PowerShell remoting or Group Policy. The following PowerShell script copies the agent installer to a remote server and installs it silently:

$servers = @("WEB01", "WEB02", "DB01", "FILE01")
$installerSource = "\deployservershareAgent_Setup.exe"
$installerDest = "C:TempAgent_Setup.exe"

foreach ($server in $servers) {
    Write-Host "Installing SolarWinds agent on $server..."
    try {
        $session = New-PSSession -ComputerName $server -ErrorAction Stop
        Copy-Item -Path $installerSource -Destination $installerDest -ToSession $session
        Invoke-Command -Session $session -ScriptBlock {
            Start-Process -FilePath "C:TempAgent_Setup.exe" -ArgumentList "/S" -Wait
            Get-Service -Name "Windows Agent Service" | Select-Object Status
        }
        Remove-PSSession $session
        Write-Host "Agent installed successfully on $server."
    } catch {
        Write-Host "Failed on $server: $($_.Exception.Message)"
    }
}

Verifying Agent Installation and Connectivity

After installation, verify the N-central agent service is running on the Windows Server 2019 machine:

Get-Service -Name "Windows Agent Service"
Get-Service -Name "Windows Agent Maintenance Service"

Both services should be in Running status. Check the agent log for connectivity status:

Get-Content "C:Program Files (x86)N-able TechnologiesWindows Agentlogagent.log" -Tail 50

Look for entries indicating successful connection to the N-central server. In the N-central web console, the server should appear in the Assets view within 5–10 minutes of agent installation. If it does not appear, check outbound HTTPS access from the server to the N-central server FQDN on port 443.

Configuring Windows Firewall for the Agent

The N-central agent requires outbound HTTPS (TCP 443) to the N-central server. If Windows Firewall blocks outbound traffic by default, add an outbound allow rule:

New-NetFirewallRule -DisplayName "SolarWinds N-central Agent Outbound" -Direction Outbound -Protocol TCP -RemotePort 443 -RemoteAddress "203.0.113.50" -Action Allow -Profile Any

Replace 203.0.113.50 with your N-central server’s IP address. For N-central Cloud (SaaS) deployments, the server communicates with cloud endpoints — consult the SolarWinds documentation for the current list of IP ranges and FQDNs to whitelist.

Applying Monitoring Templates and Policies

In the N-central console, navigate to the server in Assets view and click Configuration. Assign a Service Template — a pre-configured collection of monitoring checks appropriate for the server type. For a Windows Server 2019 file server, assign a template that includes: CPU utilization (threshold: warning at 80%, critical at 95%), Memory Available (warning at 15%, critical at 5%), Disk Space per volume (warning at 85%, critical at 90%), Disk I/O performance, Windows Services (monitor specific services for Running state), Event Log monitoring for critical system events, and Antivirus definition age check.

Customize thresholds for individual servers by clicking on a specific service check in the server’s monitoring view and adjusting the warning and critical thresholds to match the server’s expected load profile. This per-server customization overrides the template defaults.

Using the Agent for Remote Management Tasks

The N-central agent enables remote management capabilities from the N-central console including: Take Control (remote desktop via the N-central built-in viewer or integration with your RMM tool’s remote session client), Run Script (execute PowerShell or batch scripts on the remote server from the console), File Transfer (upload or download files from the managed server), and Restart/Shutdown (reboot or shut down the server from the console).

For automated remediation, N-central supports Automation Policies — scripted responses that trigger automatically when a monitoring check enters a failed state. For example, create an automation policy that restarts a specific Windows service when N-central detects it has stopped. This reduces mean time to recovery for common service failures without requiring human intervention for well-understood failure modes.

Patch Management via SolarWinds N-central

N-central integrates a patch management engine that uses the agent to inventory installed Windows updates, apply missing patches on a schedule, and report patch compliance. Navigate to Configuration > Patch Management > Patch Management Profiles to create a patching profile. Configure approval rules (auto-approve security updates, manually approve feature updates), patching schedule (typically second Tuesday-Friday each month, the week after Patch Tuesday), reboot behavior (reboot automatically after midnight if required, or queue reboots for manual approval), and maximum install retries.

Assign the patch profile to your Windows Server 2019 asset. N-central will begin inventorying installed updates using the Windows Update Agent API via the installed agent, calculate missing approved patches, and install them on the configured schedule with full logging and compliance reporting in the N-central console.