2 replies to this topic

[IWGT]

We have an installshield Dev 8 install. At the end of the install we start our application. The application automatically logs in to our application server using the windows login it is logged in with.

This is our problem: Customers roll out our application via GPO. They run the client installs under the administrator context. So when we start our client application at the end of the install, our application attempts to login using administrator which is the user running the install rather than logging in using the windows user that is currently logged in.

I have tried to find a way to get the Windows currently logged in user as opposed to getting the windows user that is actually running the install.

Does anybody have any ideas to either 1) get the currently logged in windows user as opposed to getting the windows user running the install program, or 2) somehow start the application after the install is completed and control has been passed back to the logged in user.
Some of our customers are requiring that there the app be started on the client machine without any reboot or logoff/logon required.

Any ideas would be appreciated.

[Stefan Krueger]

Maybe use a slightly different approach:
Don't run the setup in the administartor account but in the user account. Using GPO you can run it with elevated privileges so your setup will have access rights to all relevant locations, but only between InstallInitialze and InstallFinalize. Thereafter it will return to normal user rights and the LogonUser property will be the currently logged on user.

[digitalfootprint]

We had a similar situation rolling out an enterprise application via Novell's Zenworks.

1. The application required elevated privileges
2. No reboot was mandatory
3. The MSI installation launched an application that passed the logged in credentials for authentication.

A. The Application grabs the system user name and the application failed.

We used a tool called Authenti-key for NT by DigitalFootprint Software Corporation to execute the installation as the user in an elevated state. The elevated state is only valid for the installation package. When the package is finished, the rights are removed.

Check it out.

www.digitalfootprint.net
or on zdnet
http://downloads-zdn...4-10153448.html