In either case you can also pass /qn or similar to suppress the UI, but I would suggest avoiding that until you have things working. If you cannot acquire administrative privileges, and the package is authored appropriately, you may be able to install it with msiexec /i package.msi ALLUSERS=2 MSIINSTALLPERUSER=1. Your best bet is to acquire administrative privileges, in which case a simple msiexec /i package.msi will do the job. (Of course, per the first bullet it doesn't matter yet as you're not performing a normal installation.) While the documentation does say that setting it to 1 will prevent the application from being listed in ARP, the implementation likely checks for any non-empty string value. empty string) definition for truth rather than a 1/0 definition. Windows Installer works primarily on a defined/undefined (that is non-empty string vs. ARPSYSTEMCOMPONENT=0 might do the opposite of what you likely expect.Note that MSIINSTALLPERUSER may not work correctly unless the package was authored with this so-called dual purpose in mind. You are probably looking for ALLUSERS=2 MSIINSTALLPERUSER=1 to invoke the Windows Installer 5 / Windows 7 or later per-user redirection. The correct property name would be ALLUSERS. ALLUSER=2 is meaningless as the property ALLUSER is not defined. /a still does not "install" the software.Your second command line has several errors: This is typically intended for a company to use in order to avoid having to physically share the installation disc (back when there were installation discs). This is not an installation of the software, but instead the creation of an uncompressed installation source. As you briefly allude to, /a performs what is called an administrative install. The steps you are taking are not supposed to have the outcome you expect.
0 Comments
Leave a Reply. |