Installation for a non-admin user

[JohnO]

Rather belatedly I am trying the installation of our app for a non-admin Windows 7 user, in order to discover any unintended consequences (aka gotchas). The user doing the installation has to be able to install in C:\Program Files - so the installer must be run using an admin id.

I would value any guidance as to where I could improve on this (esp items 5 and 8 ):
1. Log in a the user that will use the application
2. Download setup.exe
3. Run setup.exe as admin user
4. We have created a new dialog, based on the 'destination' dialog, that allows the user to choose when to put their application data. By default, this is in their home directory (C:\Users\<user-name>\rssdata).
5. However, the installer prefills the name of the (run-as) admin user. Is there any way to tell IA that this should be the logged-in user?
6. We have to instruct the person doing the installation to change this to the logged-in user's name.
7. The installation sets an env variable for the logged-in user. However, this is set for the run-as admin user, not the logged-in one.
8. Is there any way to direct IA to set this for the logged-in user?

Is there a way to install using the non-admin id, but somehow enable them to install in Program Files?

Regards, John

[FrancescoT]

Dear John,

when a process is elevated, the process will run under the elevated user context.
Consequently, any function that belongs to the user context, it will work under the elevated context only.

You could try to use the "Get System Setting" command to retrieve the logged User Name and then, to manipulate the target home directory via script.

For what concerns the "Set Env variable", unfortunately there isn't too much to do because it directly depends on the calling process ... and from its point of view, the current user context is the one who launched the package.

Hope this helps you.

Regards