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.
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.
Remote Silent Uninstall
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. 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.
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). 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.
With our WMIC prompt, we can ask many questions of a node (or nodes) and receive some nicely formatted replies. Though formatting the replies is beyond the scope of this 'How To', much more information can be found on the internet.
So let's find out if a particular node even has our target software (Spiceworks does attempt to list this information in its software scan) /node:COMPUTERNAME product get name,version,vendor This command asks WMI to reply with a list including the Name, Version, and Vendor of all compliant software installations. If you would like to filter for a specific product, you may do so. Here's an example scanning a networked machine for all installed applications from the vendor 'Apple, Inc' /node:ANOTHEREXAMPLE product where vendor='Apple Inc.' Get name,vendor (.Note from Anders4221: A small hint if you have special characters like '-' or '/' in the computer name you need to use ' ' characters in order to get information from client) (.Note from Joe3034: Here is how you use wildcards in your search: Surround the like phrase in double quotes and your search criteria in single quotes, and use% as the wildcard symbol. E.g.: /node:ComputerXYZ product where 'vendor like 'adobe%' get name,version,identifyingNumber ). Let's assume you just got word that Adobe Reader has a serious flaw in it's old version.
In a panic, you asked all your users to blindly install the new version of Adobe reader straight from Adobe's site. Thankfully, they all managed to do so. However you've received 3 tickets so far about an Acrobat.com icon on the desktop. You have a flat text file of all your computer's names stored in c: computers.txt.
You pop open a WMIC shell with appropriate permissions and enter the following command: /failfast:on /node:@'c: computers.txt' product where name='Acrobat.com' call uninstall /nointeractive Which iterates through your list, skipping nodes that are invalid (eg:machine is turned off) and those that don't meet the criteria. You'll need to confirm 'y' that you want to uninstall on every node unless you use the nointeractive flag. Updated Note from Bart2691. An easy way to automate answering 'Yes'. Examples for doing it by PC or a text file is to use the /nointeractive flag.
Additionally, if you don't wish to hang on failed nodes, use the /failfast:on flag to quickly skip a node that isn't responding. note from true911 (unconfirmed) The correct flag is failfast:on, not fastfail:on wmic /failfast:on /node:@'FILENAME.txt' product where 'name like 'microsoft office professional edition 2003' call uninstall /nointeractive.
OK, so this is a challenge. It looks like TV doesn't have an unattended uninstall setup. No luck finding anything on their website, either. The default 'uninstall string' runs a GUI uninstall program. Russellh wrote: I figured uninstalling and just reinstalling the thinner client would be better than trying to change passwords.
An outside consultant has saved our computers to his teamviewer account and I need to undo that and keep it from happening again in the future. That makes sense, the way i avoid that is by going into the settings and setting Incoming LAN requests to accept exclusivley, therefore only people within the lan can get access. But that still doesn't help with the password issue you are up against. OK, so this is a challenge. It looks like TV doesn't have an unattended uninstall setup.
No luck finding anything on their website, either. The default 'uninstall string' runs a GUI uninstall program.
A reddit dedicated to the profession of Computer System Administration. Community members shall conduct themselves with professionalism. Do not expressly advertise your product. More details on the may be found. For IT career related questions, please visit Please check out our, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should read! Checkout the Users are encouraged to contribute to and grow our Wiki.
The core game–and its various problems–is definitely starting to show its age, but if you’ve ever enjoyed The Sims at least a little, you’ll probably find Unleashed to be a worthwhile add-on. Full version of halo combat evolved. The latest of these is The Sims: Unleashed, which adds several major features to the original Sims game, including household pets, gardening, and new outdoor lots to explore, build, and furnish, plus new career paths and plenty of new objects with which to decorate your sims’ homes and the various lots they can visit.
So you want to be a sysadmin? Official IRC Channel - #reddit-sysadmin on Official Discord -. I have been told over and over by McAfee Support that there is no remote silent uninstall for McAfee SaaS Endpoint Security. They do provide a remote silent Install. So, yeah, just go ahead and install on 100's of machines. Need to uninstall?, Do it all manually they say with a sorry tone in their voice.
![Silent Silent](https://support.kaspersky.com/images/KSC10_10643_0113-219867.png)
How To Uninstall Remote Desktop
I refuse to let this go, I know there is a way. I can pull the uninstall msiexec string out of the registry per machine architecture but there is no compatability with a /qn /x switch. McAfee does also provide a utility called Vssetup that you can use with an /uninstall switch but requires an employee to choose 'Yes'. They also provide a ultimate McAfee clean up utility called MVSUninst.exe that has no silent uninstall capability as far as I know. My thoughts at this point is to turn to AutoIT or a comparable utility to create a virtual click on 'Yes' when prompted. Anyone have any advice or experience on this?
Our Enviroment is equipped with PSTools and PDQ Deploy. On the one hand, very annoying and not scalable to a large deployment situation.
On the other hand. How terrible would it be if something was able to hijack the silent uninstall process of your anti-virus?
Does their product have some sort of central management system that verifies if endpoints are properly protected or not? That should mitigate the risks of that possibility I would think. My guess is, like most AV companies, they can't imagine a scenario where anyone could possibly want to uninstall their product and therefore don't put any effort into that side of things. How terrible would it be if something was able to hijack the silent uninstall process of your anti-virus? Well, hopefully your users are not local admins and you would need to pass administrator credentials to the uninstall. Does their product have some sort of central management system that verifies if endpoints are properly protected or not? The offer what's called an EPO server but we have not gone down this route.
I wouldn't be surprised if the remote uninstall function is not supported with this server in place as well. There is a reporting dashboard offered at Mcafeeasap.com that will let you know the status of the machines protected. They can't imagine a scenario where anyone could possibly want to uninstall their product Haha, yup. This is probably their mindset. If you do have the gumption to uninstall, you will have to homebrew a solution or do so manually.
Remote Silent Monitoring
We accidentally deployed the SCCM 2012 client to some machines that are not allowed to have it due legal reasons. Now we removed it, but SCEP is still installed. I was so far unable to find a way to silently uninstall it. The uninstall command given in Registry is C: Program Files Microsoft Security Client Setup.exe /x but this brings up a user dialog.
![Cisco remote silent monitoring Cisco remote silent monitoring](/uploads/1/2/4/2/124220154/616480457.png)
I tried various other options like /q or /s but without success. When I start C: Windows ccmsetup scepinstall /x /q I don't get an error message but SCEP remains installed Is there any way how to silently remove SCEP?