Member_2_2862251
asked on
Methods of preventing prerequisite files from installing
Hello, just wondering how this may be done. With some installers it's easy enough to extract the contents, remove the specific prereq package, etc., but some installers don't open like that (nor do they extract themselves in a way that's easy for me to poke through). Therefore, what is a good method for preventing prerequisite software from installing?
For clarification purposes, this is for remediating vulnerabilities within current software packages which are to be installed manually/on-demand and not through WSUS. In this specific instance, MS Visual C++ 2005 Distributables. They're old/unsupported, therefore IA doesn't want them installed. (Whether the main software will work without it is another question, but...whatever.) The software packages are commercial/publicly available.
For clarification purposes, this is for remediating vulnerabilities within current software packages which are to be installed manually/on-demand and not through WSUS. In this specific instance, MS Visual C++ 2005 Distributables. They're old/unsupported, therefore IA doesn't want them installed. (Whether the main software will work without it is another question, but...whatever.) The software packages are commercial/publicly available.
ASKER
OK, further clarification.
The software will not be provided through WSUS, SCCM, etc.
This is software which is made available through an approval process. Either a tech or a client with the correct credentials will install the software.
So, I have to either A) block the prerequisite software from installing or B) remove it and then rewrap the installer. In the case of A) and B), what are good solutions?
The software will not be provided through WSUS, SCCM, etc.
This is software which is made available through an approval process. Either a tech or a client with the correct credentials will install the software.
So, I have to either A) block the prerequisite software from installing or B) remove it and then rewrap the installer. In the case of A) and B), what are good solutions?
You talking too abstract.
Dont package MSI with visual studio if you dont want visual studio runtime included
Dont package MSI with visual studio if you dont want visual studio runtime included
ASKER
A) I'm working with someone *else's* software package. It wasn't my choice, it isn't as simple as extracting the specific MSI file from, and I cannot just rebuild it from scratch.
B) The vendor built it a certain way, using Installshield, and I did not find a good way to tell the main installer to ignore the prerequisite. (If I had Installshield Pro/Premier I could go into the package, remove the prq that points to VS C++ 2005, and rewrap it, but I don't have the funding/OK to do so.)
With regard to a possible answer, I found the simplest way was to just create a batch file that would uninstall the offending prereq afterward. WMIC commands work wonders.
B) The vendor built it a certain way, using Installshield, and I did not find a good way to tell the main installer to ignore the prerequisite. (If I had Installshield Pro/Premier I could go into the package, remove the prq that points to VS C++ 2005, and rewrap it, but I don't have the funding/OK to do so.)
With regard to a possible answer, I found the simplest way was to just create a batch file that would uninstall the offending prereq afterward. WMIC commands work wonders.
Easiest is to ask vendor to skip the unneeded dependency (You paid money sort of)
Or tell you want to deploy with GPO and they could make MSI
Or tell you want to deploy with GPO and they could make MSI
ASKER
Going back to the vendor is off-the-table. I'm asking specifically what could be done on this end.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Problem is same redist in program directories, you can plainly rename those DLLs to get them out of the way.