This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- windows 7 and integrity level
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 16, 2010
08:32 AM
windows 7 and integrity level
at the end of the install i am running the exe of our product
the problem is that it is not running with the integrity level token set to medium
so not all the features works well.
how can i set the application to run in medium integrity level from setup
In code i'm using
LaunchApp (TARGETDIR ^ "xxx.exe", "")
the problem is that it is not running with the integrity level token set to medium
so not all the features works well.
how can i set the application to run in medium integrity level from setup
In code i'm using
LaunchApp (TARGETDIR ^ "xxx.exe", "")
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 16, 2010
11:13 AM
I'm a little unclear what you're asking. By mentioning integrity levels, it sounds like you might want to do something similar to described on Designing Applications to Run at a Low Integrity Level. But reading between the lines, I think what you're really asking is how to launch your application as the original non-elevated user.
There's no great way to do this in an InstallScript project (which I'm assuming you're using, due to the reference to TARGETDIR). A Basic MSI project leverages Windows Installer's multiple process architecture, and runs the UI non-elevated so long as the bootstrap doesn't elevate it; in this scenario the UI can then launch the program at the end as the original user because the context hasn't been lost. The only approach I could imagine for InstallScript would be to try to match this architecture, creating an external limited-user UI project which then installs or removes an internal elevated project silently. This is not likely to be trivial.
There's no great way to do this in an InstallScript project (which I'm assuming you're using, due to the reference to TARGETDIR). A Basic MSI project leverages Windows Installer's multiple process architecture, and runs the UI non-elevated so long as the bootstrap doesn't elevate it; in this scenario the UI can then launch the program at the end as the original user because the context hasn't been lost. The only approach I could imagine for InstallScript would be to try to match this architecture, creating an external limited-user UI project which then installs or removes an internal elevated project silently. This is not likely to be trivial.