When updating my PRTG core server, all connected remote probes are updated subsequently. I have a lot of remote probes and would like to limit the number of updates performed at once (to reduce peaks in bandwidth usage). How can I achieve this?
Article Comments
This is not working for me, when ever i reboot the server or restart the "PRTG Core Server" service the value reverts back to 10000.
May, 2012 - Permalink
Please try stopping the services first and change the value in the registry, while the services are not running. After restarting the services, the value should bring the exspected effect.
Jun, 2012 - Permalink
This proved to be very useful for our setup. It would be even more useful to be able to configure this setting in the web interface.
Could Paessler consider adding this to the wishlist?
Apr, 2013 - Permalink
@mbrennan: The setting is in the registry by intention as this should only be changed if really necessary and if there are issues with the default value. So moving this feature to the web interface is not planned. Sorry.
Apr, 2013 - Permalink
This article applies to PRTG Network Monitor 9.2 or later
Simultaneous Update of Remote Probes
Since version 9.2, after a core server update, PRTG updates all connected remote probes at once, deploying the new executables. Depending on the number of remote probes and available bandwidth, this might cause bandwidth issues. In order to limit the number of remote probes updated at a time, you can set a registry value.
Set Registry Value
Caution: Please backup your system before manipulating the Windows registry!
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor\Server\Core\HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor\Server\Core\Apr, 2012 - Permalink