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
- :
- msi in add remove program
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
‎Dec 20, 2007
01:19 PM
msi in add remove program
hi
When i install my msi in the VM i am able to view that in Add/Remove program. If the other users logins to the same VM they are not able to view the same in Add/Remvoe Program. Any idea which property makes it visible to all .
Thanks
When i install my msi in the VM i am able to view that in Add/Remove program. If the other users logins to the same VM they are not able to view the same in Add/Remvoe Program. Any idea which property makes it visible to all .
Thanks
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 21, 2007
07:57 AM
If you are installing it "per user" that is the way it should work. To have it visible to all, you must install it for all users (per machine.) Do you set the ALLUSERS property or display the CustomerInformation dialog and choose "for all users"?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 25, 2007
10:13 PM
hi Kathy..
thanks for replying .. i am setting the property ALLUSERS=1 and performing a silent installation. this is the command which i am using...
msiexec /i "MSI Name" TRANSFORMS="MST name " /norestart /passive /lv "log file name"
Thanks
Ram
thanks for replying .. i am setting the property ALLUSERS=1 and performing a silent installation. this is the command which i am using...
msiexec /i "MSI Name" TRANSFORMS="MST name " /norestart /passive /lv "log file name"
Thanks
Ram
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 27, 2007
08:00 AM
I would try using /lv* and then examining the log file for clues.
![](/skins/images/19F9C6DC056868BD0EEB3511534AB4E7/responsive_peak/images/icon_anonymous_message.png)