MSI installs successfully on a client computer, but the installed program does not work for all users

Article:TECH109758  |  Created: 2007-01-10  |  Updated: 2007-01-17  |  Article URL
Article Type
Technical Solution


You created a LiveState Delivery or iCommand package for which an MSI installs successfully on a client computer, but the installed program does not work for all users on that client computer.

When logged on as the same user who ran a MSI installation, such as smeclnt, the program appears in Add/Remove programs and it runs as expected.  However, if logged on to the same computer as a different user, the same program does not run at all or behaves unexpectedly, and it may not appear in Add/Remove Programs.

You have a LiveState Delivery or iCommand package that runs msiexec.exe directly, or was built using LiveState MSI Packager.


MSI is a standardized file format for installers, and it offers many options.  For example, MSI-based applications can be published to a computer or to users.  There are many utilities to create MSI files, and due to the many options available, it is possible to create an MSI file that is not automatically published to all users on a LiveState Delivery client computer.


There are a few options available to resolve this problem.
If you created the MSI file, rebuild the MSI file with the correct properties such that it publishes to all users.
If using msiexec from the Pre-Install or Post-Install section of your LiveState Delivery package, add the ALLUSERS=2 option on the msiexec command line.
For example:
    cmd.exe /c msiexec.exe /i <yourapp>.msi ALLUSERS=2 REBOOT=ReallySuppress /qb- /L*v <yourapp>.log

          (replace <yourapp> with the name of your MSI file)
If using the Symantec LiveState Delivery 6 MSI Packager, add the property ALLUSERS with a value of 2 as follows:
            Click Create a new package, then click Next
            In MSI field, click Browse and browse to the .msi file, click once to select it, click Open, click Next
            Type a Name (long name), 8.3 Package ID, and optionally a Comment, click Next
            At the Basic Package Properties dialog, click Advanced Properties
            Click Add Property
            Type ALLUSERS in the Name field, and 2 in the Value field, and click OK
            Click OK to return to the Basic Package Properties dialog
            Click Next
            At the Deployment Options dialog, leave the defaults and click Next
            At the Package Features dialog, click Next
            At the Vendor Files dialog, if necessary click Browse and select the folder containing the Vendor files and click OK, then click Next
            At the Save Package dialog, if necessary click Browse and select the destination path and file name and click OK, then click Next
            Click Finish

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices