Release Notes
for PRTG 17

Software versions in this channel are not updated anymore.
Please consider upgrading to the latest "stable" version.

Please use the "Auto-Update" feature to update your PRTG installation with the latest stable version:
In the PRTG web interface, navigate to Setup | Auto Update.

Manual: "Software Auto-Update" · Other Release Channels

December 19th 2017 – Version 17.4.36.3670

Fixed

Sensors

Exchange (Powershell) Sensors

In certain cases, the Exchange (Powershell) sensors showed incorrect errors (for example PE233 and PE231) and duplicated existing channels. The sensors also erroneously required PowerShell 3.0 although PowerShell 2.0 is sufficient. We fixed the issues and implemented some stability improvements.

Affected sensor types are: Exchange Backup (Powershell), Exchange Database (Powershell), Exchange Database DAG (Powershell), Exchange Mail Queue (Powershell), Exchange Mailbox (Powershell), Exchange Public Folder (Powershell)

December 12th 2017 – Version 17.4.36.3595

Fixed

WebGUI

PRTG Web Interface

We already received a lot of feedback for the new PRTG web interface that we released with PRTG version 17.4.35. Your feedback has been quite helpful so far, so we can provide many fixes and improvements for it in PRTG version 17.4.36— the new web interface gets better and better, thanks to you! The fixes include, among others:

Device Tree: improved usage of available space in the M-view of the device tree (more sensors visible at a glance, sensor names are not abbreviated too early, better differentiation between devices, and more)
Input fields: disabled auto-complete for input fields (for example, username, password) in settings
Reports: fixed layout of header, footer, comments
Reports: General layout fixes and improvements, for example, tables now use the full paper width.
Maps: Connection lines in the Map Designer are visible again with Snap to Grid enabled.
Maps: fixed display in full-screen mode
Maps: improved visibility of text in map objects
Maps: fixed map object "Alarms Gauges"
Maps: PRTG for Android can open maps again.
Graphs: better visibility of the primary channel
General: layout fixes for certain screen resolutions
Libraries: several fixes for the Libraries page
Cluster: Failover nodes are read-only again.
Smart Setup: fixed several issues with the Smart Setup
Table Lists: We improved the behavior of mouse overs on table lists like device and sensor lists. Tables will not jump around anymore and the table width dynamically adjusts to your browser size.
Dialog windows: Dialog windows (for example, setting dialogs) automatically adjust to browser size and stay centered.

Fixed

Sensors

Common SaaS	The Common SaaS sensor now uses the Proxy Settings for HTTP Sensors from the parent device (or inherited from other objects higher in the hierarchy). In previous versions the sensor used the proxy configuration for Core & Probes as defined in the PRTG System Administration.
Exchange Database DAG (Powershell)	The Exchange Database DAG (Powershell) sensor is now compatible with the Cumulative Update 4 for Exchange Server 2016 (Exchange 2016 CU4).
Exchange Public Folder (Powershell)	The Exchange Public Folder (Powershell) sensors now supports Microsoft Exchange Server 2013 and Microsoft Exchange Server 2016.
Hyper-V Cluster Shared Volume Disk Free	The Hyper-V Cluster Shared Volume Disk Free sensor supports UTF-8 characters in volume names, including German umlauts. In previous versions, the sensor could not monitor volumes with umlauts in their name.
NetApp LUN	The Bytes free % channel now shows correct values.
NetApp Volume	The NetApp Volume sensor now properly handles more than 20 snapshots. In previous versions, the sensor showed a wrong number of snapshots and wrong values for the oldest and newest snapshot age channels if there were more than 20 snapshots.
Share Disk Free	The Share Disk Free sensor now correctly calculates free disk space on a share. In some cases, the sensor used the free disk space of a whole disk instead of only the share to calculate free space, which resulted in values greater than 100% free disk space, for example.
SNMP Traffic and SNMP RMON	When monitoring certain devices (for example, Fortinet FortiSwitch) with SNMP Traffic or SNMP RMON sensors, the automatic sensor name update (if set in the SNMP Compatibility Options) caused a sensor error in the last PRTG version. We fixed this issue.
SSL Certificate	Fix for the Certificate Name Validation of the SSL Certificate sensor: In certain cases, the sensor check failed although CN/SAN matched the SNI.
Windows Updates Status (Powershell)	Stability improvements for the Windows Updates Status (Powershell) sensor

Fixed

Server

PRTG Core Server Service	In rare cases when running a PRTG update, the PRTG Core Server service got removed and could not be installed again. We fixed this issue.
Reports	Double quotes in report names resulted in timeouts while PDF creation in some cases. We fixed this issue.
System Information	We fixed an exception that was caused when a vendor was not available for a Software table entry.
Tickets and Auto-Discovery	PRTG will now only create one ticket for a completed auto-discovery when at least one new device or sensor has been discovered.

Fixed

Security

Amazon SNS Notifications	The AWS Secret Access Key for Amazon Simple Notification Service notifications is not readable anymore in the PRTG web interface.
Maps	We added a check for the file format of background images that you can upload for maps. It is only possible to use the file formats .jpg, .png, and .gif for background images.

Fixed

Remote Probes

Cluster	Access keys for remote probes will be automatically synchronized on all cluster nodes for both newly installed remote probes and removed remote probes.
Installation	We fixed a small issue affecting the installation of a remote probe via the context menu in the device tree.

Fixed

Various

All Parts of PRTG

Various other fixes and improvements, as well as an updated user manual

December 2017—January 2018 – Version 17.4.36/18.1.36

Improved

WebGUI

PRTG Web Interface

Major improvements to the new PRTG web interface! We implemented a lot of your feedback to give you an even better experience with PRTG.

Improved

Sensors

NetApp LUN

The NetApp LUN sensor has a new channel Mapped that shows whether the LUN is mapped or not.

NetApp Volume

We added 8 new channels to the NetApp Volume sensor for a even more detailed view on your NetApp storage system:

Compression savings bytes
Compression savings bytes %
Deduplication savings bytes
Deduplication savings bytes %
Total savings bytes
Total savings bytes %
Files free
Files free %

Important: Because of required changes to the volume detection approach of this beta sensor, existing instances of the NetApp Volume sensor will stop working after updating to this PRTG version. Please add your NetApp Volume sensors anew. To keep monitoring data of existing NetApp Volume sensors, you can pause them. It is also not possible anymore to add sensors for volumes that are offline.

Changed

Sensors

REST Custom

The REST Custom sensor now uses JSONPath in the REST configuration file to map the retrieved JSON into sensor channels and values. To reflect this change, names of REST configuration files now have the ending .template instead of .json. Please consider this when adding new REST configuration files to PRTG. We also implemented some fixes and improvements for this beta sensor.

Note: Existing REST configuration files using the outdated JSON format (.json files) will continue to work after updating to this version, but please be aware that they will not be compatible with PRTG versions in the near future. We recommend that you convert existing REST configuration files to .template files using JSONPath as soon as possible.

November 2017 – Version 17.4.35

Note

PRTG in the Cloud

Cloud Rollout

We roll out this version on PRTG in the cloud in stages. PRTG 17.4.35 will be available on your own cloud instance soon!

New

WebGUI

Completely revised and updated look&feel of the PRTG web interface! The new, modern PRTG web interface comes with a cleaner look and many improvements to the usability. You will now find what you need more easily!

Add buttons in the device tree are now bundled into one central location, the + button.
The Edit function in table lists always works like the former Multi-Edit function. Select the object(s) you want to edit and the menu appears on the right.
Floating Save button: On forms, for example, settings pages, the Save button will always stay on the current page segment. Once you have changed something, it will turn blue and you can save at any time.
You have the option to use a dark theme for the PRTG web interface, see your account settings.
And we have tidied up everywhere in the PRTG web interface!
Note: If you have customized the PRTG web interface using one of the dedicated files, all your modifications will be lost after installing PRTG version 17.4.35. There is still an option to modify the appearance of PRTG, but please note that this is an unsupported and deprecated feature. For details, see the Knowledge Base.

New

Sensors

NetApp SnapMirror

We are further enhancing the NetApp monitoring capabilities of PRTG: You are now able to monitor SnapMirror relationships with PRTG and the new NetApp SnapMirror sensor!

The sensor accesses the NetApp API via SOAP and supports the latest NetApp ONTAP version 9.2, as well as previous versions ONTAP 9.1, ONTAP 9.0, and cDOT 8.3. Always see the health and relationship status of a SnapMirror, the relationship type (mirror and vault), the mirror state, and important parameters about SnapMirror transfers and failures. This is really great news for all NetApp customers!

Changed

Sensors

EXE-based Sensors

All sensor types that require the .NET framework will need .NET version 4.5, 4.6, or 4.7 on your PRTG server and on all computers running a probe after installing PRTG version 17.4.35. By default, required .NET versions are included in Windows 8 or later and Windows Server 2012 or later. For details, see the Knowledge Base.

Changed

Core/WebGUI

File Lists

We refined the change from the last PRTG version 17.3.33 and made the handling of file lists in the web interface more comfortable. File lists will now automatically refresh as soon as you open the according page in PRTG to immediately display newly added files like SNMP libraries, device icons, or report templates.

Manually reloading file lists will not be necessary anymore in most cases, but if you have to do so for some reason, you can use the (partly) new Load Lookups and File Lists option under Setup | System Administration | Administrative Tools.

Changed

Languages

Czech Language File

We removed the Czech language file from PRTG. Existing PRTG installations that use the Czech language file will switch to English after the update to this version.

Improved

Sensors

Adding Sensors	We improved the PRTG internal sensor creation process to speed up things. You will especially benefit from this improvement when adding many sensors at once. This is the case, for example, when sensor types scan for available monitoring items on the target device before the sensors are actually created (meta-scan). PRTG will now create the sensors in background tasks and show the progress to keep you informed—you don't have to wait anymore for the sensors and can continue your business.
HTTP XML/REST Value	We added TLS 1.2 support for the HTTP XML/REST Value sensor. Because this improvement makes the "SSLv3 Connection" setting obsolete, we removed it from the sensor settings. We also fixed a possible stack overflow caused by this sensor.
SNMP Dell PowerEdge Physical Disk	We added some new states to the Disk State channel of the SNMP Dell PowerEdge Physical Disk sensor to cover all states returned by the target device.
SNMP HP ProLiant Physical Disk	We added two new states to the Disk Status channel of the SNMP HP ProLiant Physical Disk sensor: SSD Wear Out and Not Authenticated
SNMP Library	We considerably improved the way PRTG creates SNMP Library sensors from an imported MIB (OIDLIB)! When you add the SNMP Library sensor, it will now automatically create SNMP Custom Advanced sensors with up to 10 channels for single values returned by OIDs, SNMP Custom Table sensors with up to 10 channels for returned table rows, and SNMP Custom String sensors for OIDs that return string values instead of creating a lot of single value SNMP Library sensors. This makes adding custom sensors much easier, because you do not have to enter the OIDs manually to start monitoring but just select desired items from an OIDLIB in the PRTG web interface. With the SNMP Library sensor switching to automatically create custom table and advanced sensors, we also eased the process of creating device templates that include custom SNMP sensors. And that's not all: The created sensors will also take the descriptions of used OIDs and add them to the according sensors' Comments tabs.

Improved

Security

This version includes general security enhancements for PRTG and the configuration file.

Improved

System Information

System Information via SNMP returns more data for the tables System, Processes, and Hardware from a wide variety of Linux machines and a lot of generic network devices.

November 27th 2017 – Version 17.4.35.3441

Fixed

Sensors

Folder	The Change Trigger for notifications of the Folder sensor is working again.
REST Custom	Several fixes and stability improvements for the REST Custom BETA sensor.
SNMP Cisco System Health	Custom tags for SNMP Cisco System Health sensors in device templates will now be added to the deployed sensors when running the auto-discovery. In previous versions, the tags have been overridden by default tags.
SNMP Library	In certain cases, using the SNMP Library sensor with an imported OID library that contained strings resulted in a huge PRTG configuration file. We have fixed this issue.
SNMP Printer	The SNMP Printer sensor will now correctly interpret negative values as well as 0 values returned by the printer. Such values resulted in unintended sensor warnings and errors in some cases.
SNMP Sensors	Stability improvements and major fixes for all SNMP sensors
SNMP SonicWALL VPN Traffic	When running an auto-discovery with a template that contains a SNMP SonicWALL VPN Traffic sensor, PRTG will now always use the identification method for connections defined in the sensor settings. In previous versions, the sensor erroneously used "By index" in certain cases, which resulted in multiple re-added sensors for the same connection.
SNMP Traffic	Some devices have a blank interface description in SNMP v1 (empty ifDescr and ifAlias), so the SNMP Traffic sensor was not able to use the description of such devices for the sensor name. The SNMP Traffic sensor will now take values from SNMP v2 ifXName in this case to avoid an empty name.
SSL Certificate	The SSL Certificate sensor comes with predefined limits for the Days of Expiration channel again. PRTG will warn you if your certificate expires in 28 days (keep in mind: it will not warn you about other, even worse "28 days later" scenarios) and show a down status if there are less than 7 days left.
Windows Updates Status	Passwords will not be logged in clear text anymore when using the Windows Updates Status (Powershell) sensor.
WMI Sensors	Values with data type UInt32 or UInt64 were not converted correctly when monitoring via WMI and resulted in an integer overflow in certain cases. We fixed this issue.

Fixed

Server

API	The API call /api/table.xml?content=sensortree now returns the correct lastvalue_raw. Raw data differed from the correct value by factor 10.
Device Templates	The device template Buffalo TeraStation NAS now also works in Spanish language versions of PRTG.
Email Delivery	We have removed an internal comment part in emails to prevent security software from classifying emails from PRTG as insecure (of course, PRTG will never send you insecure emails!).
License	Stability improvements for the PRTG licensing system
Monitoring Data	We fixed an issue that occasionally caused missing monitoring data in sensors and empty sensor messages after a PRTG server restart.
Schedules	We fixed an issue with schedules in timezones without daylight saving time. Schedules will now also correctly work in such timezones. Changing and assigning schedules works more reliably.
Security	We fixed two possible XSS vulnerabilities (CVE-2017-15008 and CVE-2017-15009). Thank you Edward Amaral Toledano, Ricardo Fajin, and Wen Bin Kong for reporting CVE-2017-15009!
Tickets and Auto-Discovery	When running an auto-discovery on group level, PRTG will now only create one ticket for the complete auto-discovery. In previous versions, PRTG was a bit chatty and created a ticket for each detected device.

Fixed

WebGUI

Device Tree	Deleting objects while the Auto-Discovery was running on the deleted object resulted in an inconsistent or empty device tree in some cases. We fixed this issue.
Graphs	You can download graphs as PNG again. The PNG button of graphs erroneously delivered an SVG in previous versions. Historic data graphs will now show a text label for the maximum value even when the primary channel is the only displayed channel (except for a maximum value of 100%).
Memory Leaks	We fixed two memory leaks, one caused by Geo Maps, one caused by data tables.

Fixed

Reports

Report Graphs

When adding a sensor to a report multiple times, the graphs in the report did not show any data. We fixed this issue.

Fixed

Various

All Parts of PRTG

Various other fixes and improvements, updated user manual, updated language files

Changed

Tree Version

Tree Version Update

The configuration file of this version is not downwards compatible with previous PRTG versions.

November 9th 2017 – Version 17.4.33.3283

Fixed

WEBGUI

Geo Maps

This version includes another fix for Geo Maps.

November 6th 2017 – Version 17.4.33.3251

Fixed

Sensors

REST Custom

The REST Custom BETA sensor now works properly on 32-bit builds and on cloud probes.

Fixed

Core

Reports

In certain cases, CSV report files could not be generated properly. We fixed this issue.

Fixed

WEBGUI

Geo Maps

We have fixed the issue with Geo Maps. PRTG now uses HERE Maps as provider so you are able to correctly view Geo Maps again.

September 11th 2017 – Version 17.3.33.2830

Changed

Sensors

Amazon CloudWatch Sensors

Amazon CloudWatch sensors now require .NET 4.5 or later to be installed on the computer running the PRTG probe you add the sensor to (local or remote probe system; on every node if on a cluster probe). This change affects the following sensor types:

Amazon CloudWatch Alarm Sensor
Amazon CloudWatch EBS Sensor
Amazon CloudWatch EC2 Sensor
Amazon CloudWatch ElastiCache Sensor
Amazon CloudWatch ELB Sensor
Amazon CloudWatch RDS Sensor
Amazon CloudWatch SNS Sensor
Amazon CloudWatch SQS Sensor

Fixed

Sensors

Windows Updates Status (Powershell)

Several fixes and stability improvements for the Windows Updates Status (Powershell) sensor.

Fixed

Maps

Public Maps

Public maps can display SVG map objects like data graphs again.

August 30th 2017 – Version 17.3.33.2753

Fixed

WebGUI

Fixed memory leak in the PRTG web interface

August 23rd 2017 – Version 17.3.33.2686

Fixed

Sensors

Amazon CloudWatch SNS	You can add Amazon CloudWatch SNS sensors again. Previously, when trying to add the sensor, it showed the error message "Could not create the sensor Amazon CloudWatch SNS BETA on device Amazon SNS (8.8.8.8). Operation (ListPlatformApplications) is not supported in this region".
Docker Container Status	If you have defined another port than the default port 2376 to connect to Docker, the Docker Container Status sensor will now really use this port. In previous versions, the port was erroneously reset to default.
Exchange PowerShell Sensors	We have fixed a bug in Exchange PowerShell sensors: they will now show a correct error message instead of a NullReferenceException.
Sensor Factory	We have fixed a bug that sometimes resulted in incorrect historic data graphs of the Sensor Factory sensor if you set the "use zero as source value" option for missing sensor data.
SIP Options Ping	The SIP Options Ping sensor now recognizes all returned status codes and shows the correct status.
SNMP Custom and SNMP Custom Advanced	We have fixed a bug that caused a lowercase conversion of strings in OIDs requested by SNMP Custom and SNMP Custom Advanced sensors. This bug resulted in broken OIDs and so prevented the sensors from finding instances (error message: "No such instance").
SNMP NetApp Sensors	We have fixed a bug in the NetApp device template that resulted in an interrupted auto-discovery.
SNMP Traffic	The auto-discovery now works when using a generic metascan with the SNMP Traffic sensor. Data graphs of SNMP Traffic sensors have an improved scaling when showing in and out traffic as positive and negative area chart.
SNMP Trap Receiver	Improved filtering for string bindings
Windows Updates Status (Powershell)	The Windows Updates Status (Powershell) supports the Windows 10 Creators update. It now requires at least .NET 4.5 on the probe system and PowerShell 3.0 on both the probe system and target system.
WMI Sensors	Stability improvements for WMI multi-query sensors, for example, the Windows Physical Disk I/O sensor

Fixed

Security

We have fixed a possible XSS vulnerability (CVE-2017-12879).

Fixed

WebGUI

Data Graphs	Improved chart rendering for data graphs in the PRTG web interface and in historic data reports. In particular, several PRTG language versions like Korean will benefit from this improvement.
Geo Maps	When you change geo locations for objects in the device tree, Geo Maps will accordingly update and show the defined location again.

Fixed

Server and Probes

Stability

In rare cases, the PRTG server performed an unexpected restart because of a deadlock event when scheduling reports. We have fixed this potential deadlock cause.
Stability improvements for the PRTG core server and probe system

Fixed

Auto-Discovery

Device Templates

When you create a device template, the object setting When a Sensor Reports an Error in the Scanning Interval section will now be stored in the new template.

Fixed

Notifications

Email Notifications	We have fixed some broken links in email notifications.
Notification Trigger	Changing the internal type of a sensor's down status (down due to limits or scan error) will not prevent PRTG from sending notifications anymore.The notification trigger was not provoked in rare cases because the internal status change (from down by scan error to down by limit to down by scan error) has reset the trigger timer.

Fixed

Various

Various minor fixes and improvements, updated user manual, updated language files

August—November 2017 – Version 17.3.33/17.4.33

New

Sensors

NetApp Sensors

We have added 8 brand new sensor types for your NetApp monitoring! Set up a complete monitoring of your NetApp cDOT or ONTAP storage system with these sensor types:

NetApp Aggregate
NetApp I/O
NetApp LIF
NetApp LUN
NetApp NIC
NetApp Physical Disk
NetApp System Health
NetApp Volume

The sensors monitor your NetApp accessing the API via SOAP and support the latest NetApp ONTAP version 9.2, as well as previous versions ONTAP 9.1, ONTAP 9.0, and cDOT 8.3.

Note: The sensor types NetApp cDOT Aggregate (SOAP), NetApp cDOT I/O (SOAP), NetApp cDOT Physical Disk (SOAP), and NetApp System Health (SOAP) are now deprecated. If you have running instances of these sensor types, they will be automatically replaced by according new NetApp sensors after updating PRTG. Usually, monitoring with affected sensors will seamlessly continue. If you run into any issues with the migration path for outdated NetApp sensors, please manually add desired NetApp sensors anew.

REST Custom

The new REST Custom sensor can monitor almost everything! This sensor is a really powerful tool and gives you the possibilities to go far beyond standard monitoring: you can now query any REST API that returns JSON or XML and map the results into sensor channels. Define your own mapping rules in a dedicated REST configuration file using JSON! It just has to follow the PRTG API specification for the JSON return format.

We deliver various REST configuration files for this sensor by default, so you can immediately see and try out what might be possible with your own REST Custom sensor. You can find the samples in the \Custom Sensors\rest folder in the PRTG program directory, including mappings for the REST APIs of KEMP load balancers, Weather Underground, Docker containers, and PRTG itself, ready-to-use for the sensor.

And the REST Custom sensor is also smart: you do not necessarily have to write a REST configuration file in JSON format to get sensor values when querying some REST endpoint. The sensor comes with an automatic detection feature for JSON or XML responses and creates suitable channels on its own! Choose channelDiscovery as REST Configuration setting of the sensor and it will parse the JSON or XML response of the REST query to automatically create channels for all available number and boolean values (including strings if convertible into numbers).

You have some cool idea for this sensor or have already implemented a REST configuration file? Great, let us know if you want to share it!

Changed

Core/WebGUI

File Lists

If you manually add files to the PRTG program directory on the core server while PRTG is running, you now have to manually reload the file lists to immediately show new files in the web interface. For this purpose, use the new Reload File Lists option under Setup | System Administration | Administrative Tools in the PRTG web interface.

This change affects these file lists:

Report templates
Device templates
Device icons
SNMP library (oidlib) files
Language files

Note: These lists will still be automatically updated after 1 hour and after a server restart. If you save new device templates via the web interface, the template list will be refreshed immediately.

Improved

Sensors

Amazon CloudWatch Sensors

We have added the region EU (London) to the Amazon CloudWatch Alarm, EBS, EC2, ElastiCache, ELB, RDS, SNS, and SQS sensors.

Improved

Notifications

Amazon SNS Messages	You can use new locations for the notification method Amazon Simple Notification Service Message: US West (Ohio), Canada (Central), EU (London), Asia Pacific (Seoul), Asia Pacific (Mumbai)
SMTP Delivery	SMTP delivery for email notifications now supports TLS V1.1 and TLS V1.2.

July 25th 2017 – Version 17.3.32.2478

Fixed

Russian Language File

Device Templates

Device templates in the Russian language version of PRTG will be shown again in the "Auto-Discovery with Template" window and device settings.

Fixed

Sensors

Sensors with Lookups

Sensors with lookups can now use the full 32-bit unsigned integer range. This will prevent affected sensors from returning the error 'Value is out of 32-bit integer bounds'.

July 10th 2017 – Version 17.3.32.2339

Fixed

Server

Core Service

We fixed an issue that caused a memory leak on explicit logon.

Fixed

PDF Reports

We fixed an issue with PDF reports showing the error "%1 is not a valid Win32 application. (0xC1)".

July 4th 2017 – Version 17.3.32.2309

Fixed

Sensors

Various

We fixed an issue that resulted in sensors going into a warning state due to an undefined lookup value.

June 27th 2017 – Version 17.2.32.2279

Fixed

Security

Generic Security Files

We have fixed a possible XSS vulnerability (CVE-2017-9816).

Fixed

Sensors

WMI Sensors

Major stability and performance improvements for WMI sensors.

June 27th 2017 – Version 17.2.32.2206

Fixed

Sensors

Common SaaS	The Common SaaS sensor can check Bing again. Microsoft has deprecated the used URL so you might have seen the sensor message Bing API not available. We have fixed this issue.
Dell PowerVault MDi Logical Disk	The Dell PowerVault MDi Logical Disk sensor will now show all available disks on a PowerVault system when adding the sensor. We have fixed a small bug that prevented the sensor from finding all disks during the metascan.
DHCP	We have fixed a bug where an overflow could prevent the DHCP sensor from showing the correct results.
Folder	We have improved the stability of the Folder sensor when monitoring folders that contain a large number of files and added a proper timeout handling for folder scans. For debugging purposes, the sensor now also provides the option to write the sensor result to disk.
HTTP Sensors	HTTPS POST requests with NTLM authentication work again.
NetFlow	We have fixed an issue that caused missing data for NetFlow sensors.
PostgreSQL	We have fixed an encoding issue to correctly display PostgreSQL sensor error messages.
Sensor Factory	If a Sensor Factory sensor included source sensors with delay (like xFlow and Packet Sniffer sensors) and the option use zero as source value was enabled for the setting If a Sensor Has No Data, the Sensor Factory only showed 0 values. We have fixed this behavior.
sFlow	Data graphs of the sFlow and sFlow (Custom) sensors showed gaps in certain cases because of wrong assignments to scanning intervals. This was caused by a workaround for buggy target devices that we have implemented in a previous PRTG version. We have fixed this behavior.
SMTP&IMAP and SMTP&POP3 Round Trip Sensors	We have fixed a small security issue: passwords in logfiles of SMTP&IMAP Round Trip and SMTP&POP3 Round Trip sensors are now masked when authentication is enabled.

Fixed

Sensors

SNMP Cisco UCS System Health	We have removed the 'failure predicted' channels from the SNMP Cisco UCS System Health sensor: Fan Failure Predicted Fan Module Failure Predicted Power Supply Failure Predicted These channels do not return the expected values from the target device. Note: Sensors of this type that have already existed before updating to this PRTG version will not show values in these channels anymore. Please add the sensor anew to avoid empty channels. For details, please see this Knowledge Base article: Why are some SNMP Cisco UCS System Health sensor channels not showing any information anymore?
SNMP HP ProLiant Network Interface	We have fixed an issue with 0 bytes that resulted in error The network adapter with mac address [mac] could not be found (code: PE157) when using the SNMP HP ProLiant Network Interface sensor.
SQLv2 Sensors	The setting "Use Data Table Value in Sensor Message" of SQLv2 sensors will now be saved when you create a device template with these sensors. Several fixes for processing block comments in SQL scripts. We have improved the handling of DECLARE statements for SQLv2 sensors. For example, you can now use DECLARE without semicolons (;). This allows you to copy&paste SQL queries directly from your SQL Server Management Studio, for example, into your .sql file that you use with your SQL sensor.
SSH Script and SSH Script Advanced Sensors	Security fix for SSH Script and SSH Script Advanced sensors: we have improved the parameter check for SSH script sensors.
Syslog Receiver	Summarized email notifications triggered by Syslog Receiver sensors showed a broken header. We have fixed this issue.
VMware (SOAP) Sensors	We have fixed a timeout bug that occurred in certain cases when adding a VMware (SOAP) sensor.
VMware Datastore (SOAP)	In PRTG language versions other than English, the VMware Datasore (SOAP) sensor created the Free Space channel twice while one of these channels (the one with the name in the selected language) did not show any data. We have fixed this issue. If you use another language version than English, please add running sensors of this type anew after updating to this version to benefit from the fix.
WMI Vital System Data (V2)	We have removed the option to add a WMI Vital System Data (V2) sensor for CLR Memory: % Time in GC because the returned value appeared to be meaningless.

Fixed

Notifications

SMS Notifications

PRTG will not log errors for custom SMS notifications anymore if the HTTP response of the provider is in the 200 range. This fix will also prevent PRTG from re-sending SMS notifications that already have been successfully delivered.

Fixed

Cluster

Failover Nodes

We have fixed a bug that caused objects on failover nodes to not synchronize and update in a timely manner in certain cases.

Fixed

Server

API

The API call /api/discovernow.htm will correctly return an error if a non-existing device template is passed with the call instead of just returning OK.
The columns "datetime" and "timeonly" will now return the same, correct time.
The API call /api/getsensordetails.json will now return a value (true or false) for the "favorite" property.

Fixed

Various

Various minor fixes and improvements, updated user manual, updated language files

June 2017 – Version 17.2.32

Changed

Login

Default Login

We have removed the Default Login button. If you use the default credentials of PRTG, the login fields are now pre-filled:

Login Name: prtgadmin
Password: prtgadmin

Use the Login button to proceed. If you have changed the default credentials (which we strongly recommend!), the login works as before: just enter your PRTG user account credentials and log in.

Improved

Device Templates

Create Device Template

PRTG will now show the names of the sensors that were added to a device template as result of the Create Device Template function.

Improved

Sensors

Amazon CloudWatch	We have added the region Canada (Central) to the Amazon CloudWatch Alarm, EBS, EC2, ElastiCache, ELB, RDS, SNS, and SQS sensors. You can now monitor all your instances in Canada (Central)!
HTTP Data Advanced	We have added advanced options to the HTTP Data Advanced sensor: you can now specify the protocol version (HTTP 1.0 or HTTP 1.1), define the user agent, and use custom HTTP headers.
HTTP Push	HTTP Push Count, HTTP Push Data, and HTTP Push Data Advanced sensors support TLS 1.2 encryption (lower TLS/SSL versions are not supported).

June 7th 2017 – Version 17.2.31.2153

Important

Server

Auto-Update

We have fixed a bug that prevented the PRTG server from notifying you about the availability of a new version and performing a full automatic update. This bug was introduced with PRTG version 16.4.28 (November 2016), so you might have missed all intermediate versions until now. You could still manually check for the latest update and download and install it on the auto-update page in the PRTG web interface.

Please install the new PRTG version 17.2.31.2153 now. PRTG will then again be able to perform unattended updates for future versions. You can use the Auto-Update function of your PRTG installation for the update. In the PRTG web interface, choose Setup | Auto-Update from the main menu bar and click Check for Latest Update and Download. As soon as the update is ready, click Install Update 17.2.31.2153.

See also PRTG Manual: PRTG Status—Auto-Update

May 15th 2017 – Version 17.2.31.2018

Fixed

PDF Reports

PDF reports work properly and show header, graphs, and tables correctly again.

May 10th 2017 – Version 17.2.31.1977

Fixed

Server

User Rights

On cluster installations, PRTG user accounts with read-only or read/write rights were not able to access sensor overview pages anymore. We have fixed this issue.

May 3rd 2017 – Version 17.2.31.1917

Fixed

Sensors

APC UPS Health Template	Several fixes to the APC UPS Health device template
Business Process	Searching by object ID when defining channels for the Business Process sensor works better now.
SSH Disk Free	The SSH Disk Free sensor can show up to 100 channels (99 partitions). Previously, the default limit for channels applied so the sensor only added up to 50 channels.

Fixed

Reports

PDF Reports

We have fixed a bug that caused empty graphs in PDF reports in certain cases.

Fixed

Server

Installer

When installing or updating PRTG, the installer will not start the PRTG core and probe services anymore if a reboot of the computer is required. This fix prevents inconsistent file states and according errors.

Fixed

Various

Various minor fixes and improvements, updated user manual, updated language files

April 24th 2017 – Version 17.2.30.1883

Fixed

Server

Core Server

In certain cases, the update of PRTG to one of the previous 17.x.30 versions caused an access violation if a Windows Updates Status (Powershell) sensor had more than 17 channels. This could prevent the PRTG server from starting. We have fixed this issue.

April 18th 2017 – Version 17.2.30.1825

Fixed

Sensors

SSH Sensors	su and sudo will correctly run commands with elevated rights if you set it in the "Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems" settings.
APC UPS Health	When running the auto-discovery with the APC UPS Health device template, the Run Time Remaining channel of the sensor that is added by the template will now show the correct value.

April 10th 2017 – Version 17.2.30.1767

Fixed

Probe

Security Token

We have fixed a bug that occurred with some sensor types where refresh tokens of the impersonation were acquired with the wrong session type. This could result in timeouts in scan threads.

Fixed

Server

Core Server

We have fixed a bug that caused toplist data files to be corrupted on PRTG core server shutdown.

April 4th 2017 – Version 17.1.30.1719

Fixed

Reports

PDF Reports

Fixed a bug that caused reports to be incomplete depending on the system's DPI settings where the core server is located.

Fixed

Sensors

HTTP Push Sensors

Fixed a regression that broke multiple HTTP Push based sensors running on the same listening port.

March 28th 2017 – Version 17.1.30.1681

Fixed

Reports

PDF Reports

Creating PDF reports works again.

Fixed

Auto-Discovery

Buffalo Device Template

The Buffalo device template works properly again and does not discover too much anymore.

Fixed

Sensors

SNMP Custom Table	You can add the SNMP Custom Table sensor again.
SQL Sensors	Comments with a # in the query do not cause an error anymore.

March 21st 2017 – Version 17.1.30.1618

Important

Server

Historic Data Reports

We have fixed a bug where short outages were not correctly recognized as downtime in historic data reports.

Changed

Sensors

Windows Sensors

Windows sensors on new PRTG installations will now use WMI only as Preferred Data Source by default (see the Windows Compatibility Options in the device settings) to query monitoring data instead of the hybrid approach (Windows Performance Counters as default, WMI as fallback). The latest major performance and stability improvements for WMI sensors with PRTG version 17.1.28.1341 have such a positive effect on your monitoring experience, so we recommend that you keep the new default setting!

Note: This update does not automatically migrate the setting on existing PRTG installations. If you encounter issues with Windows sensors that use Performance Counters by default, please manually change to WMI only as Preferred Data Source.

Fixed

Sensors

Active Directory Replication Errors	Adding the Active Directory Replications Errors sensor to device templates now works.
Event Log (Windows API) and WMI Event Log	The Event Log (Windows API) sensor and the WMI Event Log sensor support up to 2,000 characters in the message. Previously, the message was cut off after 1,024 characters.
HTTP Push Sensors	HTTP Push sensors now clear error PE206 if the set port is available again and show the correct status. In previous versions the HTTP Push sensors never came back if the port was blocked once.
SNMP Custom String	The SNMP Custom String sensor can now show backslashes (\) in the sensor message.
SNMP Custom Table	Creating a device template including several SNMP Custom Table sensors and running the auto-discovery with this template works more reliably. PRTG will now create sensors for all available entries in the SNMP table. We have also fixed a PE247 error that occurred in some cases in the previous PRTG version when auto-discovering SNMP Custom Table sensors.
SNMP HP ProLiant Network Interface	The SNMP HP ProLiant Network Interface sensor now also works if there are 0 bytes in the MAC address of the target interface. The error message in this case was: "The network adapter with mac address [mac] could not be found (code: PE157)"
VMware Datastore (SOAP)	The VMware Datastore (SOAP) sensor now has predefined channel limits to automatically warn you if your disk is running full. If this change does not apply to your scenario (because of thin provisioning, for example), please adjust the limits in the channel settings.
Windows Updates Status (Powershell)	Channel names of the Windows Updates Status (Powershell) sensor are now more appropriate and show the correct severity for updates. We have also added new sensor channels for hidden updates.

Fixed

Server

API	The API call for historic data provides correct raw values again.
PhantomJS	We have updated PhantomJS to the current version. PRTG uses PhantomJS to generate PDF reports and screenshots for the HTTP Full Web Page sensor and support bundles. This update will improve and fix some smaller issues regarding these functionalities.
Schedules	PRTG will now validate the syntax of period lists for schedules to prevent access violations and resulting failures when starting the PRTG server.
Security	We have fixed a small security issue that could result in an access violation showing passwords in clear text in certain cases.
Uptime Threshold	In certain cases, the uptime threshold in the Monitoring settings reverted to the default value after a PRTG server restart. PRTG will now keep your individually set desired minimum uptime.

Fixed

Cluster

"Check Now" on failover nodes works again. In previous versions, the action was only executed on the master node.

Fixed

Various

All Parts of PRTG	Various fixes and improvements to all parts of PRTG, including more performance improvements
Manual Update	Updated user manual

Changed

Tree Version

Tree Version Update

The configuration file of this version is not downwards compatible with previous PRTG versions.

March 13th 2017 – Version 17.1.29.1531

Fixed

Server

Update	In rare cases, the update installer invalidated the license. We have fixed this issue.
Core Server	We have fixed a core server crash due to probe connections being denied because of IP filter, access key, or incorrect security protocol.

February 27th 2017 – 17.1.29.1427

Fixed

Notifications

Push Notifications

Push notifications in PRTG freeware versions work again. PRTG did not send them out anymore after the trial period has expired.

February 15th 2017 – Version 17.1.28.1341

Fixed

Sensors

WMI Sensors	Major stability and performance improvements for WMI sensors! Special thanks to Colby for all the help with this!
WMI Microsoft SQL Server Sensors	You can add WMI Microsoft SQL Server 2008 - 2016 sensors again!

February 27th 2017 – 17.1.29.1427

Fixed

Sensors

Citrix XenServer Sensors	Citrix XenServer Host and Citrix XenServer Virtual Machine sensors now close their sessions on the target device to avoid potential instabilities on the XEN host.
Custom Script Sensors	For custom script sensors like the EXE/Script Advanced sensor, you can now provide special characters in custom unit and last message as escape sequences in the returned XML.
NetApp cDOT Sensors	The NetApp cDOT sensors support ONTAP 9.
Python Script Advanced	The Python Script Advanced sensor correctly replaces parameters again.
sFTP Secure File Transfer Protocol	The sFTP Secure File Transfer Protocol now supports the new SSH engine which we introduced with PRTG version 16.2.24 (May 2016). Note: You can still use the old SSH engine as legacy version by selecting the deprecated “Compatibility Mode” in the sensor or device settings, but we will remove this option soon.
SNMP Custom String	String search in SNMP Custom String sensor results also works for raw bytes (like MAC addresses).
SQL Sensors	The change trigger on the notifications tab of SQL sensors is now available. This means that you can actually use the Trigger 'change' notification setting of SQL sensors in combination with a change trigger to receive notifications if the sensor message changes.
SSH Sensors	We have implemented several important fixes and improvements for the default SSH engine that the SSH sensors use to retrieve monitoring data from target devices. SSH sensors will now run more stable and available options like SSH rights elevation will work more reliable. This fix also includes support for special characters (like North Germanic characters) in username and password. If an SSH sensor returns the error read_password_prompt timeout or read_paessh timeout after you have updated to PRTG 17.1.29, please check your SSH Rights Elevation settings in section Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems of the affected device. Ensure you use the setting that your target device requires and enter your password for 'sudo' or 'su' anew. See this Knowledge Base article for details: https://kb.paessler.com/en/topic/73353

Fixed

Licensing

License Activation

Stability improvements for the changed license activation system

Fixed

WebGUI

Find Duplicates	The Find Duplicates function for devices will not find false positives anymore when the last octet of the IP address has three digits.
Maps	Fixed a small security issue with inactive user accounts

Fixed

Notifications and Schedules

Tags	Tags of notifications and schedules work again, for example, if you use these tags to filter for notifications and schedules in tables. Important: You will lose existing tags (which did not work anyway) for notifications and schedules with this update so you will have to define them anew.

Fixed

Emails

Content-Type

Emails are now delivered with a correct Content-Type. This will help to prevent anti-spam software from blocking emails from PRTG that include PDF reports, for example.

Fixed

Various

All Parts of PRTG	Many other minor improvements and fixes to all parts of PRTG
User Manual	Updated user manual

February 2017 – 17.1.29

New

Sensors

SNMP Buffalo TS System Health

We are glad to present the first dedicated PRTG sensor for Buffalo storage systems with this version! The new SNMP Buffalo TS System Health sensor monitors your Buffalo TeraStation NAS and can show you important system health values like memory and CPU usage, uptime, number of errors and warnings, failover status, firmware update availability, and the RPSU status.

To monitor even more data of your Buffalo TeraStation, we also deliver the new device template Buffalo TeraStation NAS. Run an auto-discovery with this template to automatically create SNMP Custom Table sensors with additional useful information, for example, array status. disk smart status, and iSCSI status. Of course, this device template will also create sensors for traffic, memory and load average on your TeraStation.

Improved

Sensors

Docker Container Status	The Docker Container Status sensor provides the option to choose the container name as identification method instead of the container ID. In some cases, the ID of the target container changes regularly so that the name might be a better identification method to ensure seamless monitoring.
GitLab Build Status	Several improvements and fixes for the GitLab Build Status sensor: for example, you can identify projects and branches more easily.
SNMP SonicWALL VPN Traffic	The SNMP SonicWALL VPN Traffic sensors provides the option to use IP ranges as identification method for connections.
SSH Disk Free	When adding the SSH Disk Free sensor, you can now select up to 100 disks you want to monitor with one sensor. For the sake of stability and performance, this approach ensures that the sensor will not create too many channels.
SSL Certificate	The SSL Certificate sensors supports Elliptic Curve Cryptography (ECC) certificates in addition to RSA certificates. Depending on the used cryptosystem, the sensor will show suitable security ratings for the public key length.

January 10th 2017 – Version 17.1.28.1032

Fixed

Sensors

WMI Sensors

The connection to the target device now also works if you use the external IP address of the probe system as device address while defining Windows credentials.
Stability fixes for connection establishment for all WMI sensor types
WMI Event Log sensor will not cause probe restarts because of timeouts anymore.

Fixed

Licensing

License Activation

Stability improvements for cluster failover activation with the changed license activation system

Fixed

PRTG Administration Tool

Logs	Sending logs via FTP when using the PRTG Administration Tool works again.

December 19th 2016 – Version 16.4.28.7421

Fixed

Licensing

License Activation

Stability improvements for the changed license activation system

December 15th 2016 – Version 16.4.28.7403

Fixed

Licensing

License Activation

Stability improvements for the changed license activation system

December 8th 2016 – Version 16.4.28.7352

Fixed

Licensing

License Activation

Stability improvements for the changed license activation system

December 7th 2016 – Version 16.4.28.7339

Fixed

Sensors

WMI Sensors

Stability improvements for WMI sensors

Fixed

Licensing

License Activation

Stability improvements for the changed license activation system

December 1st 2016 – Version 16.4.28.7279

Fixed

Licensing

License Activation

Stability improvements for the changed license activation system

Previous Versions
and other Release Channels

Release Notes for PRTG 17

December 19th 2017 – Version 17.4.36.3670

Fixed

Sensors

Exchange (Powershell) Sensors

December 12th 2017 – Version 17.4.36.3595

Fixed

WebGUI

PRTG Web Interface

Fixed

Sensors

Common SaaS

Exchange Database DAG (Powershell)

Exchange Public Folder (Powershell)

Hyper-V Cluster Shared Volume Disk Free

NetApp LUN

NetApp Volume

Share Disk Free

SNMP Traffic and SNMP RMON

SSL Certificate

Windows Updates Status (Powershell)

Fixed

Server

PRTG Core Server Service

Reports

System Information

Tickets and Auto-Discovery

Fixed

Security

Amazon SNS Notifications

Maps

Fixed

Remote Probes

Cluster

Installation

Fixed

Various

All Parts of PRTG

December 2017—January 2018 – Version 17.4.36/18.1.36

Improved

WebGUI

PRTG Web Interface

Improved

Sensors

NetApp LUN

NetApp Volume

Changed

Sensors

REST Custom

November 2017 – Version 17.4.35

Note

PRTG in the Cloud

Cloud Rollout

New

WebGUI

WebGUI

New

Sensors

NetApp SnapMirror

Changed

Sensors

EXE-based Sensors

Changed

Core/WebGUI

File Lists

Changed

Languages

Czech Language File

Improved

Sensors

Adding Sensors

HTTP XML/REST Value

SNMP Dell PowerEdge Physical Disk

SNMP HP ProLiant Physical Disk

SNMP Library

Improved

Security

Security

Improved

System Information

Release Notes
for PRTG 17