Hi all
Ive just been given a bit of a curly one - for an amateur packager anyway i hope.
We need to deploy an ms hotfix across the network and it has to be in MSI format.
what we need to do is copy the hotfix exe to a new folder on the local drive, run the exe and after run, delete the new folder and hotfix exe.
i can create the new folder and copy the exe to the drive and make an msi of that, but how do i tell it to run after copying and then clean up after its done?
any suggestions? im using wise package studio 5.6
thanks in advance
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
when you say copy the exe, I'm guessing you mean the msi? does it need to be local as it drops the network while installing, otherwise I'd suggest you look into how it's deployed, are you using SMS etc..? Depending on what it is and how you deploy, I'd have thought there was a tidier way than dropping it locally and then trying to clean up..
Answered 10/25/2005 by: DuncanPaul
Orange Belt

Please log in to comment
0
no its an actual exe but looks like ill have to make it into an msi now
we want to copy it locally so that we dont have all of the pc's accessing an msi from the same distribution point, we can copy it over a wider area and have less network traffic if we do it this way but im wondering if its worth the trouble
Answered 10/25/2005 by: ictu packager
Orange Belt

Please log in to comment
0
you could do it that way I guess, add a Custom Action in execute deferred to "Execute Program from Installed Files", and then after that set a custom action to remove the file again, (in vbs maybe). Pretty ugly though, as your machines will then have this package "installed" on them, but not have the source files, have no way to repair it etc..

how do you deploy msi's, and how do you normally handle patching?
Answered 10/25/2005 by: DuncanPaul
Orange Belt

Please log in to comment
0
G'day.

Don't bother installing and deleting the hotfix executable. Just run it as a custom action embedded in the binary table. You may have to ignore the return code though.

Cheers
Answered 10/26/2005 by: greenmagnet
Senior Yellow Belt

Please log in to comment
0
The best you can do is imbed the .exe in the Binary table of an empty MSI and launch it via custom action, otherwise known as a "wrapped" exe. The reason is that Windows Installer is a tool strictly for the Application Layer, while HotFixes are modifications to the OS Layer. MSIs, by design, are not permitted to alter the OS.

I strongly suggest making yourself an "Empty MSI Template", which is an MSI with nothing in it, and keep a copy handy. With that, wrapping an .exe takes only a minute or so (dependant on the size of .exe). Make a copy of your Empty MSI Template, you've already remarked where the CA goes, and add a "Launch Application from Installation" custom action and point to your exe. Save the MSI and it will copy your exe into the Binary Table and launch the exe from within the MSI. (This is the Wise method, BTW)
Answered 10/26/2005 by: VikingLoki
Second Degree Brown Belt

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