This article applies as of PRTG 22

Is there a way to remotely and silently uninstall remote probes from our PRTG monitoring infrastructure, especially when we no longer have direct access to the client’s computer where the probe is running. Is there a way to remove the remote probe directly from the PRTG Administration Tool, which would send a "kill" notification to the remote probe, causing it to immediately uninstall itself and delete any cached data and settings. How can we achieve this?

How to remotely and silently uninstall a classic remote probe

You can run the uninstaller of PRTG with the -silent parameter just like running the installer remotely.

The file name of the uninstaller is:

unins000.exe

The uninstaller program (unins000.exe) accepts optional command-line parameters. These can be useful to system administrators and to other programs that call the uninstaller program.

/SILENT, /VERYSILENT

When specified, the uninstaller neither asks the user for a startup confirmation nor does it display a message that states that the uninstallation is complete. The uninstaller automatically deletes shared files that are no longer in use without prompting. Any critical error messages are still shown on the screen. When /VERYSILENT is specified, the uninstall progress window is not displayed.

If a restart is necessary and the /NORESTART command is not used (see below), and /VERYSILENT is specified, the uninstaller restarts without asking.

/SUPPRESSMSGBOXES

With this command, the uninstaller is instructed to suppress message boxes. This only has an effect when it is combined with /SILENT and /VERYSILENT. See /SUPPRESSMSGBOXES under What command line codes and exit codes can I use with Paessler setups? for more details.

/LOG

This command causes Uninstall to create a log file in the user's temp directory that details file uninstallation and the [UninstallRun] actions that are taken during the uninstallation process. This can be a helpful debugging aid.

The log file is created with a unique name based on the current date. It neither overwrites nor is it added to existing files.

The information contained in the log file is technical in nature and therefore not intended to be understood by end users. It is also not designed to be machine parseable; the format of the file is subject to change without notice.

/LOG="filename"

Same as /LOG, except that it allows you to specify a fixed path/file name to use for the log file. If a file with the specified name already exists, it is overwritten. If the file cannot be created, Uninstall aborts with an error message.

/NORESTART

This command instructs the uninstaller not to reboot even if it is necessary.

More

• What command line codes and exit codes can I use with Paessler setups?