New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

150.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Can we remotely and silently UNinstall a Remote Probe?

Votes:

0

Your Vote:

Up

Down

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 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. Ideally, we'd like to be able to "remove" the Remote Probe directly from within the PRTG Admin interface, 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 by  Network Services (0) 1



Best Answer

Accepted Answer

Votes:

1

Your Vote:

Up

Down

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

The filename 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 calling the uninstaller program.

/SILENT, /VERYSILENT

When specified, the uninstaller will not ask the user for startup confirmation or display a message stating that uninstall is complete. Shared files that are no longer in use are deleted automatically without prompting. Any critical error messages will still be shown on the screen. When '/VERYSILENT' is specified, the uninstallation progress window is not displayed.

If a restart is necessary and the '/NORESTART' command isn't used (see below) and '/VERYSILENT' is specified, the uninstaller will reboot without asking.

/SUPPRESSMSGBOXES

Instructs the uninstaller to suppress message boxes. Only has an effect when combined with '/SILENT' and '/VERYSILENT'. See '/SUPPRESSMSGBOXES' under Setup Command Line Parameters for more details.

/LOG

Causes Uninstall to create a log file in the user's TEMP directory detailing file uninstallation and [UninstallRun] actions 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 will not overwrite or append to existing files.)

The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parseable; the format of the file is subject to change without notice. /LOG="filename"

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

/NORESTART

Instructs the uninstaller not to reboot even if it's necessary.

See Also

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

Created on Nov 7, 2011 8:48:44 AM by  Dirk Paessler [CEO Paessler AG]

Last change on Sep 17, 2012 8:37:29 AM by  Daniel Zobel [Paessler Support]



6 Replies

Votes:

0

Your Vote:

Up

Down

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 by  Network Services (0) 1



Accepted Answer

Votes:

1

Your Vote:

Up

Down

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

The filename 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 calling the uninstaller program.

/SILENT, /VERYSILENT

When specified, the uninstaller will not ask the user for startup confirmation or display a message stating that uninstall is complete. Shared files that are no longer in use are deleted automatically without prompting. Any critical error messages will still be shown on the screen. When '/VERYSILENT' is specified, the uninstallation progress window is not displayed.

If a restart is necessary and the '/NORESTART' command isn't used (see below) and '/VERYSILENT' is specified, the uninstaller will reboot without asking.

/SUPPRESSMSGBOXES

Instructs the uninstaller to suppress message boxes. Only has an effect when combined with '/SILENT' and '/VERYSILENT'. See '/SUPPRESSMSGBOXES' under Setup Command Line Parameters for more details.

/LOG

Causes Uninstall to create a log file in the user's TEMP directory detailing file uninstallation and [UninstallRun] actions 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 will not overwrite or append to existing files.)

The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parseable; the format of the file is subject to change without notice. /LOG="filename"

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

/NORESTART

Instructs the uninstaller not to reboot even if it's necessary.

See Also

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

Created on Nov 7, 2011 8:48:44 AM by  Dirk Paessler [CEO Paessler AG]

Last change on Sep 17, 2012 8:37:29 AM by  Daniel Zobel [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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 by  tongclub60 (0)



Votes:

0

Your Vote:

Up

Down

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

Your Vote:

Up

Down

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 by  Ken Wallewein (0)



Votes:

0

Your Vote:

Up

Down

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]



Please log in or register to enter your reply.


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.