What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

PRTG Incremental Updates



Product suggestion: Please provide incremental (difference) updates between minor releases.

We have PRTG installed in our main site, with EIGHT remote probes. The remote offices are connected via 1Mb or 2Mb leased lines. I've just installed a new release of PRTG on the main server and PRTG is now showing "sending update" status for all eight remote probes. They are all saturating the lines and I'm expecting it to take 2-3 hours before they are all updated. That's 2-3 hours where PRTG probes are not responding and 2-3 hours where our leased lines are strugging.

Surely there's a better way to install updated versions of PRTG?


incremental prtg updates

Created on Jun 19, 2015 10:50:21 AM

Last change on Jun 19, 2015 12:30:33 PM by  Torsten Lindner [Paessler Support]

4 Replies



And to add insult to injury, after a whole hour of sending updates, each site reported back and said "update must be installed manually". Grrrrrrrrrrrrrrrrrrrrr

In the end I downloaded the Probe locally, FTPd it to an AWS server, stopped PRTG on the main server, then manually downloaded the new probe file from the AWS address via Remote Desktop to all the probe sites.

Not exactly smooth, that's for sure, but much quicker!


Created on Jun 19, 2015 12:21:31 PM



You can decrease the number of concurrent probe updates. Create a new DWORD key ProbeUpdateMaxNew under the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor\Server\Core\

Set it to the number of probes you want to update simultaneously. No other option to decrease the line usage here :/

Created on Jun 22, 2015 8:37:18 AM by  Stephan Linke [Paessler Support]



Perfect, many thanks. The DWORD was already there but was set to 14; I've changed it to 1.

Created on Jun 22, 2015 8:42:58 AM



You're very welcome :)

Created on Jun 22, 2015 8:59:51 AM by  Stephan Linke [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.