Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it possible to install into Program Files with limited privileges?
    primarykey
    data
    text
    <p>I have an application that will be deployed as MSI package (authored in WiX).</p> <p>I am deciding whether to specify <code>elevated</code> or <code>limited</code> privileges as required for the installer.</p> <p>The application does not include anything requiring elevated privileges besides the default install location, which is under Program Files.</p> <p>Now the problem:</p> <ul> <li><p>If I specify <b>elevated privileges</b>, then the user is prompted by UAC for administrator password during the installation. This is not required and prevents non-admin users from installing.</p></li> <li><p>If I specify <b>limited privileges</b>, then the user is presented with a dialog to select install location with <code>Program Files</code> being default. In case they do not change the install location (95 % of end users probably won't), then the installer will fail with a message that they should contact the Administrator or run the application as administrator. If they launch the installer as Administrator then they can install into Program Files without problem - but most of the users won't probably know how to launch an installer as administrator.</p></li> </ul> <p>I can potentially set the default install location to e.g. C:\Company name\Program\, but this seems nonstandard to me and majority of users will not probably like this (they are probably used to installing into Program Files).</p> <p><b>How do you solve this problem with installing applications under limited user accounts?</b></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload