how to silent uninstall a msi with a different uninstallcode on each pc?
We want to silent uninstall a msi package on several hunderds of computers, but we have one big problem, it is installed with a setup.exe that created a msi package during the install. The msi installation has a different uninstallcode on each computer.
Is there another way to silent uninstall this msi?
Is there another way to silent uninstall this msi?
0 Comments
[ + ] Show comments
Answers (14)
Please log in to answer
Posted by:
naveen.packager
13 years ago
Could you please expalin it a bit clear? Have you installed trough exe or msi?
What does this mean?
If it is intsalled trough the same msi in all computers then the below command line should work.
Msiexec /x {PRODUCTCODE} /qn
ORIGINAL: theicewarrior
but we have one big problem, it is installed with a setup.exe that created a msi package during the install.
What does this mean?
If it is intsalled trough the same msi in all computers then the below command line should work.
Msiexec /x {PRODUCTCODE} /qn
Posted by:
murali.bhat
13 years ago
Posted by:
theicewarrior
13 years ago
Posted by:
pjbaars
13 years ago
I think that you have to create a generic vbscript that reads the neccesary Windows Installer information from the registry and deploy the script to all your target pc's. You can collect information such as ProductCode, Version and ProductName. After extracting the productcode out of the registry you can start an uninstall from your script with the correct ProductCode.
Posted by:
naveen.packager
13 years ago
Check if you can try this.
Check whether you have any unintstall.exe in the INSTALLDIR of this app. If you have it then you can try the following command line or something similar to this..
Path of uninstall.exe /s. (thinking that each systems uninstall.exe will handle the uninstall of its own app)
Not confidant but hope it will work.
Check whether you have any unintstall.exe in the INSTALLDIR of this app. If you have it then you can try the following command line or something similar to this..
Path of uninstall.exe /s. (thinking that each systems uninstall.exe will handle the uninstall of its own app)
Not confidant but hope it will work.
Posted by:
dbloomfield
13 years ago
We have also experienced this problem before where the product code is randomly generated on each computer. Previously we have created a script with the following logic to un-install the software (xp, vbscript deployed through SCCM)
Get key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
For each sub key in above reg
get value: "displayname"
if displayname = "software you want to un-install" then
get value "uninstallstring"
run contents of "uninstallstring"
end if
next
This way it will find the product key of the software that you are looking for and run the msi un-installer with the correct code for that computer. You will need to log into a computer with the software installed to find the exact display name used by the software.
hope that helps
Get key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
For each sub key in above reg
get value: "displayname"
if displayname = "software you want to un-install" then
get value "uninstallstring"
run contents of "uninstallstring"
end if
next
This way it will find the product key of the software that you are looking for and run the msi un-installer with the correct code for that computer. You will need to log into a computer with the software installed to find the exact display name used by the software.
hope that helps
Posted by:
anonymous_9363
13 years ago
We have also experienced this problem before where the product code is randomly generated on each computer.Really?!? I've never seen that in all the time I've been doing this nonsense. How on God's green earth does the vendor do updates or patches?!?
Anyway, in my view, this is a pointer to poor packaging. The MSI should have been extracted and used from the outset as the "master". If it turned out that the set-up stub was performing other functions, they should have been added via a transform.
Posted by:
pjbaars
13 years ago
Posted by:
anonymous_9363
13 years ago
Posted by:
pjbaars
13 years ago
Posted by:
dbloomfield
13 years ago
I cant find the application that did this to confirm, however something in the back of my mind "labview version 6" springs to mind as the culprit.
Completely agree, extracting the MSI when repackaging the installer would likely prevent this issue. the question was how to silently un-install after his has happened. Mistakes happen, just got to find a way to deal with it.
I work for a university, sadly we get a lot of really random applications to package. Sometimes made by fred bloggs in his shed in the back garden and they love do completely random illogical things especially when they try to make up their own little "security" measures to counter piracy. On one package this month i've even been asked to provide details back to the developer so that they could HARD CODE keys and file paths into their app!
Anyway, in my view, this is a pointer to poor packaging. The MSI should have been extracted and used from the outset as the "master". If it turned out that the set-up stub was performing other functions, they should have been added via a transform.
Completely agree, extracting the MSI when repackaging the installer would likely prevent this issue. the question was how to silently un-install after his has happened. Mistakes happen, just got to find a way to deal with it.
Really?!? I've never seen that in all the time I've been doing this nonsense. How on God's green earth does the vendor do updates or patches?!?
I work for a university, sadly we get a lot of really random applications to package. Sometimes made by fred bloggs in his shed in the back garden and they love do completely random illogical things especially when they try to make up their own little "security" measures to counter piracy. On one package this month i've even been asked to provide details back to the developer so that they could HARD CODE keys and file paths into their app!
Posted by:
pjgeutjens
13 years ago
On one package this month i've even been asked to provide details back to the developer so that they could HARD CODE keys and file paths into their app!
I hope you immediately sent along an 'Educational Baseball Bat™' and instructions on how to use it on one self...
EDIT: Sorry Ian, forgot the ™ [:)]
Posted by:
dbloomfield
13 years ago
Posted by:
jmcfadyen
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.