Hi all, I've been lurking on this forum for some time now, but finally need to post because a question I have I can't find the answer to.

I've been attempting to modify a vendor's msi package (CA AllFusion Harvest Change Client to be persise) for unattented silent install via SMS on our corporate network.

In order to pass inspection, our policy says the package MUST NOT prompt the user, and MUST NOT look back to the source when you uninstall it.

I've contacted CA on numours occasions and they are of no help and are not willing to recreate the package, as their explanation is "performing a network package install will always look back to the source, that is the way it works".

I've managed to edit the msi and enable silent installation, (supressing the request to restart, and setting allusers=1 and limitui=1) but I simply cannot figure out how to get it to NOT look for the source at uninstall.

Can someone please help??? [8|]
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If this is a single MSI (not patched) then it should be a customaction and/or a component run from source making this happend during uninstall.
Can you find out which component(s) that is requiring the source location during uninstall?
Which application & version are you trying to uninstall and have you modified the installation in some how?
Answered 09/20/2006 by: AngelD
Red Belt

Please log in to comment
0
Hi Angel thanks for the reply. It's the Computer Associates AllFusion Harvest Change Client - version 7.1. What we did was take the vendor's software version 7, extract the MSI from it using their command line they gave us, patch it with the 7.1 update (.1) -again provided from them- then edit the MSI to add a couple custom paths and the silent install.

(sorry for my ignorance) but how do I find out which component is seeking its source at uninstall?

thx:)
Andrew
Answered 09/20/2006 by: SutherlandAndrew
Senior Yellow Belt

Please log in to comment
0
Look in the Component table and see if the msidbComponentAttributesSourceOnly or msidbComponentAttributesOptional attribute bits is set in the Attribute column. For the msidbComponentAttributesOptional bit; if the Media/files is not external files that is, cab:d inside or external then local source would be impossible.
Patch as in MSP or Update as in MSI? If it's a patch and the patch does not contain the whole files but the delta, if I recall correct the MSI from source will be required.
Answered 09/20/2006 by: AngelD
Red Belt

Please log in to comment
0
Both msidbComponentAttributesSourceOnly or msidbComponentAttributesOptional don't exist under
Additional Tools > Direct Editor > Tables > Component.

I did however notice NETWORK_INSTALL="Yes" was in there.

By patching I meant we had the vendor's msi, and we ran it with a command line option from the vendor that was supposed to update the msi and it's files. Theres the .msi file, and a few folders & cabs & other files.
Answered 09/20/2006 by: SutherlandAndrew
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity