Discover More, Manage Less: PRTG 26.3.122 Introduces Auto-Discovery Tasks

 Published by Michael Becker
Last updated on August 10, 2026 โ€ข 6 minute read

We just released PRTG version 26.3.122 to the stable release channel, and it brings a full package: a new Auto-Discovery Task system, seven brand new sensors, ten sensors that graduate from BETA, three experimental additions, and a range of security and server improvements.

discover more manage less prtg 26.3.122 introduces auto discovery tasks

Here are the highlights:

๐Ÿ” New: Auto-Discovery Tasks

The biggest change in this release is the new Auto-Discovery Task system. It gives you one central place to create, edit, and review all your Auto-Discoveries, right from the overview menu. A new Create Task button lets you set up a task under any probe you have write access to, with validation for required fields and a redirect to the overview once the task is created. Existing legacy Auto-Discoveries still show up in the new section, so nothing gets lost in the switch. For now, this feature works only when you log in with an administrative account.

๐Ÿงฉ New sensors

  • IP Reputation Score: checks whether the IP address of a device appears on DNS based blacklist servers, and replaces the older IP on DNS Blacklist sensor.
  • Ping Jitter v2: measures jitter and response times on a network connection, now also on the Multi-Platform Probe.
  • RDP Client-Side Check: checks the availability and response time of the RDP service on a Windows system, and succeeds the classic RDP (Remote Desktop) sensor.
  • Traceroute Hop Count v2: reports the number of hops to a device and shows the full route, now with Multi-Platform Probe support.
  • WMI Microsoft SQL Server: tracks the performance of a Microsoft SQL Server instance, with support for versions 2005 to 2025.
  • WMI Volume v2: keeps an eye on free disk space on a Windows volume, drive, or mount point.
  • VMware Datastore (REST): reports the disk usage and availability of a VMware datastore via the vSphere REST API.

โœ… Sensors that leave BETA behind

Ten sensors move from experimental to fully supported status with this release:

๐Ÿงช Lab: Three experimental sensors

๐Ÿ”’ Security and server

We hardened PRTG against Cross-Site Scripting attacks around channel names and lookup values, and EXE/Script sensors no longer print error messages directly in the sensor message.
On the server side, the installer for the NatsManager now keeps your existing configuration in place during an update instead of a full reinstall. New installations use WSMAN as the default protocol instead of DCOM, while existing setups keep working with DCOM and can switch at any time.

โš™๏ธ Other notable changes

The Database Health (Autonomous) sensor, which used to watch over the PRTG Database service, disappears from your installation with this update, together with the database components it belonged to. Custom device templates for the SNMP System Uptime, SSH Disk Free, and SNMP Memory sensors get migrated automatically to their v2 successors, with a backup of the originals stored on disk.

๐Ÿ—’๏ธ Check our PRTG release notes

In summary, PRTG 26.3.122 includes 203 resolved issues, with 6 implemented features, 28 stories, 47 bug fixes, 80 completed tasks and sub-tasks, and 35 finished documentation tickets. For all the details, take a look at our release notes page.

We also offer a public roadmap of PRTG, updated regularly, where you can read what we plan to build next.

Summary

PRTG 26.3.122 introduces a new Auto-Discovery Task system that gathers all your discovery jobs in one central place, and adds seven new sensors, among them IP Reputation Score, RDP Client-Side Check, and WMI Microsoft SQL Server. Ten more sensors, including the whole Proxmox VE family, REST JSON Data, and the SSL/TLS sensors, move from BETA to full support, while three experimental sensors such as HTTP Webpage and WMI Service v2 let you try what is coming next.

On the security and server side, we hardened PRTG against Cross-Site Scripting attacks, smoothed out the NatsManager update process, and switched new installations to WSMAN as the default protocol instead of DCOM. Custom device templates now migrate automatically to their v2 successors, the Database Health (Autonomous) sensor disappears along with the PRTG Database components it belonged to, and a range of further fixes rounds out this release across sensors, the New UI, and the API.