How to Configure Windows Server 2016 with PRTG

PRTG Network Monitor is a commercial monitoring platform from Paessler that provides comprehensive monitoring of networks, servers, applications, and cloud services through a unified web interface. PRTG is particularly popular for its ease of setup, auto-discovery capabilities, and wide range of built-in sensors for monitoring Windows Server environments. The platform uses an agent-based model for deep Windows monitoring using WMI, SNMP, or the PRTG Windows Sensor. This guide covers the complete process of integrating Windows Server 2016 into a PRTG monitoring environment, from initial device addition through configuring sensors and alerts.

PRTG Architecture and Windows Monitoring Methods

PRTG monitors Windows Server 2016 using several methods. WMI (Windows Management Instrumentation) provides the richest data for Windows servers without requiring any agent installation. SNMP can be used for basic availability and performance monitoring. The PRTG Windows Sensor (Mini Probe or Remote Probe) can be installed on Windows Server 2016 to monitor resources in isolated network segments. For most environments, WMI is the preferred method as it provides comprehensive Windows-specific metrics.

The PRTG core server must have network access to the Windows Server 2016 systems it monitors, and appropriate credentials with permissions to query WMI must be provided.

Preparing Windows Server 2016 for PRTG WMI Monitoring

Before adding Windows Server 2016 to PRTG, ensure the PRTG server can access WMI on the monitored server. Create a dedicated service account for PRTG monitoring with the minimum required permissions. The account needs to be a member of the “Performance Monitor Users” group and have WMI access permissions.

Create the PRTG monitoring service account and configure WMI permissions using PowerShell:

# Create the service account (run on domain controller or locally)
New-LocalUser -Name "prtg_monitor" -Password (ConvertTo-SecureString "SecurePassword123!" -AsPlainText -Force) -Description "PRTG Monitoring Account" -PasswordNeverExpires

# Add to Performance Monitor Users group
Add-LocalGroupMember -Group "Performance Monitor Users" -Member "prtg_monitor"

# Add to Distributed COM Users for WMI access
Add-LocalGroupMember -Group "Distributed COM Users" -Member "prtg_monitor"

Configure DCOM permissions for the PRTG account to allow remote WMI access. Open Component Services (dcomcnfg), navigate to Component Services > Computers > My Computer, right-click, select Properties, go to the COM Security tab, and add the PRTG account with Launch and Activation permissions.

Configuring Windows Firewall for PRTG

WMI uses dynamic ports and requires several firewall rules to function correctly. Enable WMI traffic in Windows Firewall using PowerShell:

# Enable Windows Management Instrumentation firewall rules
Enable-NetFirewallRule -DisplayGroup "Windows Management Instrumentation (WMI)"

# Enable Remote Event Log Management for PRTG event log sensors
Enable-NetFirewallRule -DisplayGroup "Remote Event Log Management"

# Enable Remote Service Management for service sensors
Enable-NetFirewallRule -DisplayGroup "Remote Service Management"

Adding Windows Server 2016 to PRTG

Log into the PRTG web interface and navigate to the device group where you want to add the Windows Server 2016 system. Click “Add Device” in the PRTG web interface. Enter the device IP address or hostname, provide a descriptive device name, and configure the credentials. Under Windows Credentials, enter the PRTG monitoring account username and password.

After adding the device, use PRTG’s auto-discovery feature to automatically detect and add relevant sensors. Click on the device, then click “Run Auto-Discovery.” PRTG will probe the server using WMI, SNMP, and other methods and suggest sensors to add based on what it detects running on the server.

Configuring Key WMI Sensors for Windows Server 2016

After auto-discovery, review the suggested sensors and add the most important ones for Windows Server 2016 monitoring. The following sensors are essential for comprehensive Windows Server monitoring:

WMI CPU Load Sensor: Monitors total and per-core CPU utilization. Add with a warning limit of 80% and critical limit of 95%.

WMI Memory Available Sensor: Monitors available physical memory. Configure alerts when available memory drops below 500 MB.

WMI Disk Free Space Sensor: Add one for each volume. Configure warning at 20% free and critical at 10% free.

WMI Network Adapter Sensor: Monitors bandwidth utilization on each network interface.

Windows Services Sensor: Monitors the status of critical Windows services. Configure to alert when any specified service stops running.

To add a specific sensor via the PRTG API using PowerShell for automation, use the PRTG REST API:

$prtgServer = "http://prtg.yourdomain.com"
$apiToken = "YourAPIToken"
$deviceId = "1234"

$addSensorUrl = "$prtgServer/api/addmonitor.htm?id=$deviceId&sensortype=wmifreespace&name=C+Drive+Free+Space&apitoken=$apiToken"
Invoke-RestMethod -Uri $addSensorUrl -Method Get

Configuring PRTG Alerts for Windows Server 2016

PRTG alerts are configured through notification triggers on sensors, devices, or groups. Navigate to a sensor, click the Notifications tab, and add triggers. Common trigger types include threshold triggers (alert when a value exceeds a limit), status triggers (alert when status changes to Warning or Down), and change triggers (alert when a value changes).

Configure notification recipients and methods in Setup > Account Settings > Notifications. PRTG supports email, SMS, push notifications, and webhooks for integration with tools like PagerDuty, Slack, or Microsoft Teams. For Windows Server 2016 monitoring, at minimum configure email notifications for Down status on all sensors and threshold alerts for CPU, memory, and disk sensors.

Setting Up PRTG Remote Probe for Isolated Networks

If your Windows Server 2016 systems are in a network segment that the PRTG core server cannot reach directly, install a PRTG Remote Probe on a Windows Server 2016 system in that segment. The probe connects outbound to the PRTG core server, eliminating the need to open inbound firewall rules from the PRTG core to the remote segment.

Download the PRTG Remote Probe installer from the PRTG web interface under Setup > System Administration > Probes. Install it on the Windows Server 2016 system in the remote segment:

.PRTGRemoteProbeInstaller.exe /S /D="C:Program Files (x86)PRTG Network Monitor"

Configure the probe to connect to your PRTG core server address, then approve the probe connection in the PRTG web interface under Setup > System Administration > Probes. Once connected, you can use the remote probe to monitor all servers in the isolated network segment through the PRTG core interface.