Problem with command line uninstalls
I'm having issues uninstalling applications using Managed Installations. I have a feeling I'm doing something wrong and I've been unable to figure it out from reading the administrator's guide for Kace, or searching this website (and the Internet in general).
Prior to setting up the Managed Installation for an uninstall, I make sure it works by doing it from my command line on my machine. I also want to verify that it is silent. I have successfully gotten these uninstalls to work on my computer this way but it doesn't not work from Kace. Only once has it actually said that the "install" was pushed out to the selected computer - all other times it says it's still waiting to be deployed even though the computers are idle and I keep forcing inventory updates trying to trigger the uninstall.
The one time it worked, the event viewer on the targeted machine showed the MSI Installer ran and completed successfully, but the application was still there. I'm not sure what I'm doing wrong.
I've also tried using the uninstaller Wizard under scripting, but these two applications are not listed there even though they are listed in our Software Inventory.
The uploaded screenshots are hard to see so here are links to the images:
http://i.imgur.com/TPjmh.png
http://i.imgur.com/cDGsH.png
Answers (3)
The 1st thing I see is you are using both Run command only and Uninstall using Full...
You should only use one or the other
Uninstall using Full.. - this means that you are telling the KBOX you need to download the file attached to the software title and use the command I am giving you to remove the product. This softare needs the original file
Run command only - this tells the KBOX, I don't need you to download the file that is attached to this software title. The command I have given you is all you need to run.
So this comes down to that software. Does it need the MSI to uninstall? When you look at the title under Inventory > Software, has the agent picked up a uninstall string?
Are the OS's you selected the ones you are targeting?
If you are going to explictly write our msiexec.exe then make sure you check mark "Do not prepend msiexec.exe"
I would also test your command on a system using the cmd prompt to see if it actually works manually.
Comments:
-
The command definitely works - I tested that first.
Thanks for the explanation on the difference between those two options.
The support section for that software is blank in software inventory.
What I don't understand is even when I have the full command string typed in and have it set to "configure manually" and the "do not prepend msiexec.exe" box is checked, it still has the wrong command at the top of the page where it says
"The windows client will try to un-install this via:
msiexec.exe /i "bold software v7.10.msi" "
Nothing I do changes that unless I do "run command only" but I need the msi.
We have Kace Jump Start training today so I'm going to ask the trainer as well. - ashlea 12 years ago
Also, enable logging by using /l*v <LogFile> msiexec option. It would give you an idea of why the command is not able to un-install the software.
Updating the agent on the client machines allowed it to pull the un-install string for the software. I was then able to use the un-installer wizard in scripting to successfully remove the software.