I am following the instructions for a silent install of Articulate Studio 09 which is to record an iss file and use to manage the install but I am having a problem with the desktop shortcuts. http://www.articulate.com/support/kb_article.php?product=ap9&id=c26b33it7r8p The standard InstallShield setup.exe stuff...

The setup.exe extract 2 msi's both named Articulate Studio '09 Pro.msi but neither put shortcuts on the desktop. Are there any options I can use with the setup.exe or in the iss file to hide the desktop shortcuts?

Answer Summary:
Turns out the EXE and the 2 MSI's all put GUIDs in the registry so I guess the MSI's do something, but I can't figure out what or how to manipulate them with an MST or through the EXE command line. So I gave up and made a secondary MSI that managed the required changes and included it with a CMD to handle the install. A setup.iss and uninstall.iss are required and one of the MSI's doesn't uninstall using the setup.exe so you need to uninstall it separately.
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0

>The setup.exe extract 2 msi's both named Articulate Studio '09 Pro.msi



Why not simply create a transform for one of them and add the required shortcut(s) to it?

Answered 05/10/2012 by: VBScab
Red Belt

  • Normally I would just remove the shortcut creation from the MSI's with an MST, but they are not what is creating the shrotcuts. I am not sure how I could create a transform to do this?
    Also, I am not sure if/when the MSI's are run whether its before/during/after the shortcuts are created.
Please log in to comment
0

if you try using 'msiexec /a "c:\source folder\AS09.msi" targetdir="c:\1\"', that should create an admin version of the software. If you then check that for the shortcuts or create a transform file on that msi.

Answered 05/10/2012 by: alphabeta
Third Degree Brown Belt

  • Huh, I don't know what to say other than I don't think you read the entire question or the following responses.
Please log in to comment
0

Turns out the EXE and the 2 MSI's all put GUIDs in the registry so I guess the MSI's do something, but I can't figure out what or how to manipulate them with an MST or through the EXE command line. So I gave up and made a secondary MSI that managed the required changes and included it with a CMD to handle the install.

A setup.iss and uninstall.iss are required and one of the MSI's doesn't uninstall using the setup.exe so you need to uninstall it separately.

Answered 05/11/2012 by: jmaclaurin
Third Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share