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
- :
- Re: Silent install on Vista!!!
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
‎Mar 24, 2009
08:34 AM
Silent install on Vista!!!
Hello,
I created a MSI using IS2008 and tested the same in the Vista OS with the following command line
msiexec -i -qn
But it fails that I need admin privileges (infact I am an administrator but not the built in administrator). How to perfom a complete silent installation in Vista OS???
Can anybody help me please??? Its red...
I created a MSI using IS2008 and tested the same in the Vista OS with the following command line
msiexec -i
But it fails that I need admin privileges (infact I am an administrator but not the built in administrator). How to perfom a complete silent installation in Vista OS???
Can anybody help me please??? Its red...
(8) Replies
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 24, 2009
09:31 AM
Elevate your token prior to launching the installation. For example, you could launch from an administrator command prompt.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 24, 2009
11:09 PM
Hello Bryan,
Thank you for the prompt reply. Yes I do agree that the permission level can be elevated by running the cmd.exe as built in Administrator and then pass this MSI to it to install without any problem.
But for a end user we think, the suggested alternative should be automatically triggered once the user runs the MSI with /qn command. When the user calls "msiexec /qn" from the Start->Run, the token should be automatically elevated instead running the cmd.exe as an Administrator and then launching the MSI..... Is there any change of value in the registry I can make to get this job done??? (or) any other customization will make it?
Thanks for your support....
Thank you for the prompt reply. Yes I do agree that the permission level can be elevated by running the cmd.exe as built in Administrator and then pass this MSI to it to install without any problem.
But for a end user we think, the suggested alternative should be automatically triggered once the user runs the MSI with /qn command. When the user calls "msiexec
Thanks for your support....
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2009
08:45 AM
If you create an exe called setup.exe that calls this msi then vista should realise that you want elevation and will ask the user if it is ok to run the application. A process called from an elevated app should also be elevated.
Russell
Russell
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2009
08:54 AM
Thanks Russell I will give it a shot....
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2009
09:00 AM
Silent installations do not elevate by design to disallow the possibility of silently installing an application with elevated privileges using the current user's permissions by default. While not an explicit security risk, it could possibly provide a confusing UAC prompt that the user wouldn't necessarily know how to answer.
If you want to silently install your product, you could use an InstallShield Setup.exe and manifest it to run As Administrator. This would accomplish what you want and you could use something like:
setup.exe /s /v"/qn"
for a completely silent installation.
If you want to silently install your product, you could use an InstallShield Setup.exe and manifest it to run As Administrator. This would accomplish what you want and you could use something like:
setup.exe /s /v"/qn"
for a completely silent installation.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2009
09:14 AM
Yes Bryan, I agree with the suggested alternative.
But the prompt "An unidentified program wants to access....." is appearing when I passed the parameter /s /v" /qn" along with the setup.exe. This is ironical to the /qn command.... (although the prompt is from the OS and not by InstallShield)
The problem is when I deploy this Setup.exe along with other third party applications in Vista SILENLTLY... each time I need to respond to this Vista security prompt which is lil bit annoying....
Thanks for your time...
But the prompt "An unidentified program wants to access....." is appearing when I passed the parameter /s /v" /qn" along with the setup.exe. This is ironical to the /qn command.... (although the prompt is from the OS and not by InstallShield)
The problem is when I deploy this Setup.exe along with other third party applications in Vista SILENLTLY... each time I need to respond to this Vista security prompt which is lil bit annoying....
Thanks for your time...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2009
11:10 AM
If you signed the executable then it should come up with your company name and details and not say that the program is unidentified.
Also if you know which 3rd party apps you are going to install you could call them all from the same launcher exe and will only have to give permission once.
Also if you know which 3rd party apps you are going to install you could call them all from the same launcher exe and will only have to give permission once.
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 01, 2009
09:21 AM
Either Russell Jones' suggestion would work or you could have a "suite" setup.exe that launches all the other subinstalls. The latter option can be more difficult to service in the future and makes for maintenance challenges that have to be accounted for.
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)