Software Deployment Question

How do I run a demoshield wizard unattended?

10/16/2012 4569 views


I´m on the task to push out an installation using SCCM. The application is being delivered to us already packaged with demoshield so the question is how do I configure the settings and push them out unattended via command prompt?

I googled the problem and only came up with running "setup.exe /r" to record a .iss file (answerfile). But no such file is being generated (in windowsfolder or anywhere), actually the installation then skips a couple of dialog that demands input from the user (servername, databasenames etc).

I should also mention that several applications are being installed through this setup.exe. Not just one.

Help is needed, thanks!

0 Comments   [ + ] Show comments


All Answers


First of all make there is no underlying (MSI) installer(s) extracted in the TEMP folder of the installing user during installation.

Answered 10/16/2012 by: pjgeutjens
Red Belt

  • There were MSI:s already extracted. I tried to run the "main" MSI but then a lot of files weren´t installed. I figured out how to run the setup.exe with cmd line parameters, without recording a .iss file. Now my problem is how to distribute the package with SCCM. Since the setup.exe calls for an msi and that msi kicks off more msi:s using CA:s SCCM thinks the installation is over way before it´s over. Failning as a result because I have more packages to run afterwards.
  • I "solved" it by running a vbscript that looked for the shortcut for the application. So that SCCM wouldn´t continue to run the next MSI to soon. Not the best solution but I think I´ll work.
  • Actually the installer didn´t work as expected. Files were missing all over the place leading to self healing and error messages. I´m throwing this question out to you:
    If you have an installer that works by running a setup.exe and then using the GUI choose an express installation followed up by entering a few values (database name, servername etc). How do you go by packaging it? As I stated earlier it seems to be packages with "demoshield". I can see the msi:s that are called upon/executed but I´m unable to run them directly. Shouldn´t I be able to run this installation in a sinble commandline using "demoshield" syntax or similar?
  • we're getting to the point where repackaging might be a better option, would this be viable?
  • I just think it´s a shame since all installers are MSI:s which are just called upon from this wrapper/demoshield. I´m having a dialogue with the vendor now so hopefully I´ll get some answers from them also.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ