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
- :
- Application started after install always seems to run with administrator privileges
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
Apr 07, 2015
02:49 PM
Application started after install always seems to run with administrator privileges
I am having a problem with IS 2009 running an application after a Basic MSI install. It always seems to be run with administrator privileges It doesn't matter if I implement it using InstallScript or CA EXE.
My installer requests administrator privileges, via UAC, during start-up but everything I have read says that an Immediate Execution CA placed after ExecuteAction should run in the user context and not the administrator context.
I tested this using a CA to start ‘CMD.exe /K’.
At the end of the install it starts a command window and using ‘whoami /privs’ it shows elevated credentials compared to a standard command window.
I then tested this using a CA to start regedit.exe which requires UAC authentication to view correctly.
At the end of the install it always displays without a UAC request.
Has anyone seen this behavior before?
Can anyone reproduce it?
Can anyone give me any insights into how to get the application to start in the user context?
Thanks,
Michael
My installer requests administrator privileges, via UAC, during start-up but everything I have read says that an Immediate Execution CA placed after ExecuteAction should run in the user context and not the administrator context.
I tested this using a CA to start ‘CMD.exe /K’.
At the end of the install it starts a command window and using ‘whoami /privs’ it shows elevated credentials compared to a standard command window.
I then tested this using a CA to start regedit.exe which requires UAC authentication to view correctly.
At the end of the install it always displays without a UAC request.
Has anyone seen this behavior before?
Can anyone reproduce it?
Can anyone give me any insights into how to get the application to start in the user context?
Thanks,
Michael
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 10, 2015
11:43 AM
I found out why this was happening...
...I had set the Release 'Require Execution Level' to 'Administrator' so it was promoting at setup.exe start.
When I changed the setting to 'Invoker' all was as expected!
...I had set the Release 'Require Execution Level' to 'Administrator' so it was promoting at setup.exe start.
When I changed the setting to 'Invoker' all was as expected!