Msiexec administrative install msp

This log will contain different information for each parameter you use:. The Windows Installer command line can apply or remove updates patches for example through these options:. If you have an installed package, you can use the Windows Installer command line for repairing it:.

Table of Contents. This tool gives you full control over the installation process, allowing you to set: install options install, uninstall, administrative install, advertise a product display options full, basic or no UI during the installation restart options if the machine will be restarted after the installation logging options update options apply or remove updates repair options only for an installed package public properties which are used by the installation The usual form of the msiexec command line is this: msiexec.

Install Options When launching an installation package, you can set the install type through these options: msiexec. Display Options The user interface level of the installation can be configured according to the target environment. This would happen to workstations too unless the sources were available online.

I should add that you can also put the unextracted MSI file in such a location without extracting it via an admin image, but using admin install allows any file to be downloaded separately no huge cab download. For huge MSI files this is important, and I prefer admin images as installation source to make patching more reliable - this is a subjective preference, but it is due to real-life experience.

Finally the creation of MSI patches typically requires an admin install to be run for the original setup and also for the new setup. The Windows Installer patch file is then created based on the differences between the new and old installer folders. As such admin installs are critical for the subsequent creation of patch files.

This is the case for Wise for Windows Installer - the only product I have found to create really reliable patches in real life experience this product is now off market, some details here: What installation product to use? Again a subjective observation based on extensive real-world testing.

The target folder will then contain a newer MSI and any new files provided the admin patch works, which it generally doesn't in my experience. Chris mentions "Run From Source", and this is indeed a rather useless and obsolete concept where some files in the install can be left on the network share and accessed straight from there. I honestly haven't tried this feature in years.

This feature is seldom used, but I guess it could be beneficial in scenarios where a common set of resource files should be accessed by all workstations and you want to avoid mass-duplication. Fixes to the resource files could then be deployed by an "admin install patch" as described above without reinstalling anything onto the workstations how well it works is unclear - the lack of use of this feature may be a clue. A large software suite with many and dissimilar modules where only a few are used by different people could speed up installation and usage significantly by only installing a few of the required features and leave the rest to run from source or install on first use.

It would speed up installation and subsequent patch installations and could leave potentially unsafe and unnecessary binaries off the system. This last point can be important in locked-down environments. However, in real-life I have seen patches change advertised features to be locally installed after patching which is very strange and undesired behavior, but very common to experience. In practice I find "run from source" or advertised features of very limited use. It is generally better to split a setup into two with one for client and one for server installation.

Here is a new summary of the same issue: admin install and its uses file extraction and beyond. Please also read the comment below on the " changed caching behavior of MSI in Windows 7 onwards ". In the real world, it doesn't have all that much value at all. MSI was designed back in a day when a computer typically had a gb hard drive. They came up with all these "run from source" advertisement scenarios which seemed really cool back then but never really caught on in the real world.

That's about it. Say that you need to install product X on some number of machines, and that you will need to apply some patches for X as well. Rather than applying a series of patches on each machine, you can do this:. It can save some time and effort, and you'll know that all your machines are certain to be at the same patch level. If you have a per-user setup and a system that disallows user installations through e. Its a way of authorising software to be installed.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Ask Question. Asked 10 years, 9 months ago. Active 1 year, 7 months ago. Viewed 41k times. Improve this question.

Anand Patel Anand Patel 5, 6 6 gold badges 38 38 silver badges 65 65 bronze badges. Provides the means to install, modify, and perform operations on Windows Installer from the command line. To install a package named example. You can configure what a user sees during the installation process, based on your target environment.

For example, if you're distributing a package to all clients for manual installation, there should be a full UI. However, if you're deploying a package using Group Policy, which requires no user interaction, there should be no UI involved.

If your installation package overwrites files or attempts to change files that are in use, a reboot might be required before the installation completes.

If you need to debug your installation package, you can set the parameters to create a log file with specific information. You can set public properties through this command. For information about the available properties and how to set them, see Public Properties.