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
- :
- Win Vista blocks an other msi package
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
Feb 18, 2008
03:40 AM
Win Vista blocks an other msi package
Hi all !
please help me resolving the following problem:
my setup starts another msi package, this works fine on win xp. On win Vista i have to make a mouse right click and start the Setup.exe as Administrator, otherwise the setup interuppts. Strange is: I log on as an user with admin priviliges. Wehn a user with admin priviliges starts the setup by doppel clicking it, this problem occurs.
Can anyone tell me why win vista blocks the msi package (as a customer action) to start ?
Any helps will be appreciated !
please help me resolving the following problem:
my setup starts another msi package, this works fine on win xp. On win Vista i have to make a mouse right click and start the Setup.exe as Administrator, otherwise the setup interuppts. Strange is: I log on as an user with admin priviliges. Wehn a user with admin priviliges starts the setup by doppel clicking it, this problem occurs.
Can anyone tell me why win vista blocks the msi package (as a customer action) to start ?
Any helps will be appreciated !
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 19, 2008
09:24 AM
Any helps please !
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 19, 2008
02:05 PM
The CA which starts MSI should have “In-Script Execution” set to “Deferred Execution in System Context” if you MSI require administrative privileges. You may read more information on deferred execution in manual.
Hope this helps.
Hope this helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 20, 2008
03:16 AM
The CA which starts MSI should have “In-Script Execution” set to “Deferred Execution in System Context”
While this is true in general, it won't work if your custom action is caling msiexec.exe to install another msi. ut that's not recommended anyway. You'd better install the other MSI as a prerequisite.
Stefan Krueger
InstallSite.org
InstallSite.org