Hi,
I am working on Image Onsite 8.2 package which is a Installshield setup.exe. I could not able to make the setup.exe as silent install. I have created the setup.iss response file also, still i am not able to make this application as silent. This installshield setup.exe is having Image Onsite.msi inside.
Please suggest...

Thanks,
Ramu
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
This installshield setup.exe is having Image Onsite.msi inside. Ssssssooo...extract the MSI and run that with the appropriate silent switch! :)
Answered 08/28/2009 by: VBScab
Red Belt

Please log in to comment
0
Hi,
MSI which was extracted from the temp location is not working on its own with silent switches. I tried with "ISSCRIPTDRIVEN=1" as a Public Property also.
Answered 08/28/2009 by: ramu_ch
Orange Belt

Please log in to comment
0
have a look in your InstallUISequence table for any actions that would prevent you from running the msi silently
Answered 08/28/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
Hi,
this the action i can relate to ISScript. can i delete this in my transform?
ISVerifyScriptingRuntime NOT AFTERREBOOT AND NOT ISSETUPDRIVEN 1
Answered 08/28/2009 by: ramu_ch
Orange Belt

Please log in to comment
0
read this look at the "advanced transform creation techniques"


http://www.altiris.com/upload/bldgtransforms_wp.pdf


but as always exercise caution
Answered 08/28/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
It may not be the only one. If you log the install, you should be able to identify which CA is causing the "noise" by looking at the log when whatever it is causes the noise pops up. The last line of the log should contain the name of the CA. If it doesn't, note down the line number where the log has reached then let the install continue. When it's complete, return to the line after the one you noted. That line should contain the CA's name.

- As a rule of thumb, I suggest installing ALL the IS runtimes on a build: it saves such a lot of hassle. They're designed to live side-by-side (kind of) and use hardly any resource.
- I never completely remove CAs from vendor MSIs in my MSTs. It's neater to condition them out using an impossible-to-meet condition, like 0=1.
Answered 08/28/2009 by: VBScab
Red Belt

Please log in to comment
0
Hi,
Thanks for the suggestions.
I am able to install the MSI with the transform. But the applicaiton is not installing the shortcuts and entry in Add-Remove programs. I think the ISScript is doing something in the backgroud and putting the shortcuts and ARP entry after the msi. I found the same behaviour while uninstalling the application using the MSI GUID.
Answered 08/28/2009 by: ramu_ch
Orange Belt

Please log in to comment
0
- Shortcuts
So add them.

- ARP
Check to see if the ARPSYSTEMCOMPONENT property exists. If it does, remove it.
Answered 08/28/2009 by: VBScab
Red Belt

Please log in to comment
0
There is a difference in INSTALLDIR size and No of Folders for Manual install with the vendor supplied setup.exe and extracted MSI with newly created transform.
Answered 08/28/2009 by: ramu_ch
Orange Belt

Please log in to comment
0
Then proceed as per a legacy (i.e. non-MSI) install:

- install your MSI/MST
- rename the 'Uninstall' registry key to fool the package into believing the software isn't installed
- using a lightweight snapshot tool (e.g. InstallWatch) take a 'Before' snapshot
- run the Setup.EXE
- make sure you choose exactly the same options as you did when creating your respons etransform
- take an 'After' snapshot
- incorporate any relevant changes into your MST
Answered 08/29/2009 by: VBScab
Red Belt

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