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

Can we remotely and silently uninstall a classic remote probe?

Votes:

0

We know how to remotely and silently install and configure remote probes, we do it all the time, and it works great. However, so far we have been completely unable to find a way to remotely UNinstall the remote probe. This would be particularly useful for situations where a client is no longer working with us, and we would like to remove the remote probe from our monitoring infrastructure. We need to assume that we no longer have direct access to the computer where the remote probe is running. Ideally, we'd like to be able to "remove" the remote probe directly from within the PRTG Administration Tool, and then it should send a "kill" notification to the remote probe, which will cause the probe to immediately uninstall itself and delete any cached data and settings. Our customers have been asking us for this, and it will help us leave a "clean server" when we leave without having any of our own monitoring software still installed and/or running. A silent and complete uninstall of the remote probe, initiated from the master PRTG server, is what we need. Thanks!

prtg9 remote-probe uninstall

Created on Nov 2, 2011 4:51:01 PM

Last change on Apr 15, 2024 2:24:37 PM by  Jacqueline Conforti [Paessler Support]



Best Answer

Accepted Answer

Votes:

1

This article applies as of PRTG 22

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 (unins???.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

Created on Nov 7, 2011 8:48:44 AM by  Dirk Paessler [Founder Paessler AG] (11,025) 3 6

Last change on Apr 15, 2024 2:24:50 PM by  Jacqueline Conforti [Paessler Support]



6 Replies

Votes:

0

Could you please add this to the feature request wish list? This is a fairly important task, as it keeps systems clean without leaving abandoned/orphaned Remote Probes installed all over the place. It also makes central administration much simpler.

Finally, from a security standpoint, it is valid and secure, since the uninstall command would only be originating from the Core Server, and would only execute when the Remote Probe initiates its connection to that Core Server and retrieves the Uninstall order. It is a PULL by the Remote Probe, not a PUSH from the Core Server. Therefore, by inherent configuration, it would only be able to execute on Remote Probes that are already existing members of the Core Server's centralized configuration environment. This method could not be easily used for malicious purposes to cause other unassociated Remote Probes to be forced to uninstall.

Thanks!

Created on Nov 2, 2011 6:31:39 PM



Accepted Answer

Votes:

1

This article applies as of PRTG 22

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 (unins???.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

Created on Nov 7, 2011 8:48:44 AM by  Dirk Paessler [Founder Paessler AG] (11,025) 3 6

Last change on Apr 15, 2024 2:24:50 PM by  Jacqueline Conforti [Paessler Support]



Votes:

0

This would be especially useful for situations were a client is no longer working with us, and we would like to remove the remote probe from our monitoring infrastructure. We need to assume that we no longer have direct access to the computer where the Remote Probe is running.

Created on Feb 19, 2015 3:48:20 AM



Votes:

0

Hi,

You can right click the probe in your PRTG interface and select "delete": This will delete the server side of the connection. On the client side, you can use the above stated switches. If you do not have access to the servers anymore, I am afraid, there is no way to deinstall a remote probe, aside from deleting it.

You may however ask your customer to uninstall it or turn it off. To avoid unnecessary log entries and load on your PRTG server, you can create a rule on your firewall to drop all incoming TCP packets from your customers IP on the remote probe port (23560).

Created on Feb 23, 2015 9:40:08 AM by  Severin Glaeser [Paessler Support] (0) 1



Votes:

0

If I understand correctly, your CMD solution cannot be executed via PRTG. It requires other direct administrative access to the system from which PRTG is being removed.

There's no significant difference between that and logging on remotely or directly to the server in question. In other words, it's of no value, and a useless distinction.

You really should implement remote uninstall.

BTW, when I tried to vote here, I got a response saying I needed at least a "15 reputation". I've been a paying PRTG client for years. That's great.

-- Kenw

Created on Feb 2, 2016 2:55:48 PM



Votes:

0

Hi Ken,

As you already discusssed with Jochen, the remote uninstallation of Remote Probes won't be implemented simply due to the lack of demand and the feasability of the same.

About the reputation; in order to gain some, you´ll have to make some good posts, i.e. posts that are upvoted by other users or the support team. The reputation is in no way bound to your license, only to your knowledge and activity in our forums :)

You current reputation can be found in your profile.

Created on Feb 3, 2016 8:36:22 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.