Command line installing with the WinZip MSI file

Command Line Ing With The Win MSI File Zip Self Extracting

I believe the self extracting exe puts files into some specific folders as well as runs a VBS script.

The easiest method would be for me to just create a software delivery package with the appropriate switches to make the install silent and without any user intervention.

Command Line Ing With The Win MSI File Zip Self Extracting

For the life of me, I cannot find any unattend switches for WinZip self extracting file.

I have tried the auto switch however I still get a screen prompt when the package gets deployed.

I will give it a try however what I am trying to do is do a silent install of a software update that is in WinZip self extracting exe (not WinZip itself)..

I will try the following.

Im assuming when you say winzip.exe that is just in reference to the patch that I am trying to perform the silent install.

If you know how this can be done, please do let me know.

In the end we just performed the update manually on all the PCs at our Firehall.

Essentially it is either delivered as an MSI file or wrapped in an setup.exe file.

Make every effort to do an admin install which has many benefits.

While doing that it should extract the MSI to a specific location (b).

The parameters are documented at helpnet.installshield.cominstallshield18helplib.

However, as you mentioned also the x option has side effects, namely if the product is already installed.

There seems to be no way to simply extract the MSI file without side effects.

Typical Microsoft: It would have been too simple if they had added an extract option.

I prefer this because it doesnt potentially uninstall anything.

There are so many possible tools that can be used.

MSI, MSI, admin-tools, multi-platform, etc.).

The discussion below first presents the use of admin images for MSI files and how to extract MSI files from setup.exe files.

Then it provides some links to handle other types of setup.exe files.

Also see the comments section.

Most significantly a blurb about extracting WiX setup.exe bundles (new kid on the block).

Remember that a last resort to find extracted setup files, is to launch the installer and then look for extracted files in the temp folder (Hold down Windows Key, tap R, type temp or tmp and hit Enter ) - try the other options first though - for reliability reasons.

I do believe that you will find what you need if you dig enough in the links, but the content should really be cleaned up and organized better.

Burn is used to build setup.exe files that can install several embedded MSI or executables in a specified sequence.

For an MSI that would mean running an admin install - as described below.

It is basically intended as a way to create a network installation point from which the install can be run on many target computers.

This ensures that the source files are always available for any repair operations.

Always prefer to run the actual admin install over any hacky zip extractions.

As to compression, there are actually three different compression algorithms used for the cab files inside the MSI file format: MSZip, LZX, and Storing (uncompressed).

All of these are handled correctly by doing an admin install.

Starting with Windows 7 (MSI version 5) the MSI files are now cached full size to avoid breaking the file signature that prevents the UAC prompt on setup launch (a known Vista problem).

This may cause a tremendous increase in disk space consumption (several gigabytes for some systems).

To prevent caching a huge MSI file, you should run an admin-install of the package before installing.

This is how a company with proper deployment in a managed network would do things, and it will strip out the cab files and make a network install point with a small MSI file and files besides it.

Command Line Installing With The Winzip Msi File