Install packege perMachine and run program perUser
Hello.
Let me introduced my problem:
I have an application which needs to be installed to folder that everyone on installed computer can use it. An application consists from one windows service and one regular .exe file. I want that both binaries must be run under account of user who is logged in and uses user's privileges.
I tried to put binaries in a registry under [font="courier new"]HKLM\Software\Microsoft\Windows\CurrentVersion\Run but this way binaries are running under System account. Than I put it under [font="courier new"]HKCU\Software\...\Run key. That's ok. But this way I need to put those keys under all user's registry hives, which is not possible on Windows Vista and newer system, Also, I have a problem when a new user account is created.
Shutcuts in [font="courier new"]Allusers->StarMenu->Startup should not be an option because I want to hide binaries from user view.
I'm asking if there's a possibility to configure my .msi package so, that installation put shortcuts to run my binaries in somekind of shared place, from which my binaries than be run under user account when user login.
Thanks in advance.
Best regards,
Let me introduced my problem:
I have an application which needs to be installed to folder that everyone on installed computer can use it. An application consists from one windows service and one regular .exe file. I want that both binaries must be run under account of user who is logged in and uses user's privileges.
I tried to put binaries in a registry under [font="courier new"]HKLM\Software\Microsoft\Windows\CurrentVersion\Run but this way binaries are running under System account. Than I put it under [font="courier new"]HKCU\Software\...\Run key. That's ok. But this way I need to put those keys under all user's registry hives, which is not possible on Windows Vista and newer system, Also, I have a problem when a new user account is created.
Shutcuts in [font="courier new"]Allusers->StarMenu->Startup should not be an option because I want to hide binaries from user view.
I'm asking if there's a possibility to configure my .msi package so, that installation put shortcuts to run my binaries in somekind of shared place, from which my binaries than be run under user account when user login.
Thanks in advance.
Best regards,
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
If you want the EXE to run literally as the user logs in, why not use Active Setup? Or call the EXE from a start-up/log-in script?
Posted by:
jamsek19
13 years ago
Thanks VBScrab for answer
Nice hint. I forget that also this option exists. I will try his way.
Thanks for replay
Nice hint. I forget that also this option exists. I will try his way.
Thanks for replay
Posted by:
mazessj
13 years ago
Am I missing something? Anything run from [font="courier new"]HKLM\Software\Microsoft\Windows\CurrentVersion\Run runs as the current user, not as System. It would be a major security issue if Run key items ran as System. Your original solution should work. No need for Active Setup, Startup group, or login script.
Vendors commonly add entries to the HKLM Run key when they want something to run on startup for every user instead of putting a shortcut in the Startup group.
Vendors commonly add entries to the HKLM Run key when they want something to run on startup for every user instead of putting a shortcut in the Startup group.
Posted by:
jamsek19
13 years ago
Hello.
No mazessj, I missied something, not you [8|]!
Thank you very much for right answer.
I was supposed that all applications under HKLM/.../Run registry tree are started before user's login. I was wrong.
Thank you again.
Have a nice day.
No mazessj, I missied something, not you [8|]!
Thank you very much for right answer.
I was supposed that all applications under HKLM/.../Run registry tree are started before user's login. I was wrong.
Thank you again.
Have a nice day.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.