Want this feature implemented, too? Please upvote by clicking Thumbs up!
(Posts as a reply won't be published in this feature request thread. Read Me!)
User Story
As a PRTG Administrator, I want to be able to start an upgrade of a remote probe manualy.
Details of User Story
At the moment we have a PoC of CheckPoint Sandblast Agend (AV) and we do test it on serveral servers, clients, etc. On the PRTG servers, the AV reacts somehow very sensible. So in case of a remote probe, the PRTG remote probe installer and upgrade process from the core is blocked because the AV is grabbing the .tmp files from the PRTG upgrade process. So in our case, if you upgrade the PRTG Core server, the upgrade of the remote probe is failing because of the AV. So now i need to completely uninstall the remote probe, move the Devices, sensors, etc. to another probe or to the core, delete the remote probe out of the core, reinstall the probe, and do a ne approve of the probe and move all things back. Sure, i will whitelist such things in the AV, but i think it can happen again if some patterns of the AV gets upgraded or the bahvior of PRTG will change in the future. So a manual trigger of an upgrade would be nice.
Acceptance criteria
- a button "Upgrade" in the probe Object or in the Administration settings, if the core version is newer then the probe would be great
Status
Open