InstallAnywhere Silent Installations

<h1>InstallAnywhere Silent Installation</h1>

According to Wikipedia InstallAnywhere is a Java-based software used to create software packages.

On Windows, InstallAnywhere packages come as executables.

In order to install such a package silently, we need to follow these steps:

1. Create a configuration replay file ( by starting the setup in replay mode.
<setup.exe> -r
2. Complete the installation by selecting the desired options.
3. Edit the newly file. Add this line before the install directory definition.
4. Save
5. Run the following command:
<setup.exe> -i silent -f “<pathto>\”

ATTENTION: Try to keep the path to the .properties file short (no spaces). Otherwise, the setup might fail (Problem opening install properties file). Try something like c:\tmp or c:\temp…

By default, log files (or something close) can be found in c:\tmp.

<h1>InstallAnywhere Silent Uninstall</h1>

In order to uninstall the software silently, look for an Uninstall*.exe in the installation directory. Run it with the -i silent parameter.

Office Installation

Microsoft provides an uniform way of silent customizing Office products’ installations: OCT (Office Customization Tool).

In order to start it, run the setup executable of the office installation you want to start (32 or 64-bit) with /admin parameter. (setup.exe /admin)

This will start a wizard where you can configure many options, from feature selection, to the smallest details one can imagine.

Once you’re done with the configuration, save the changes. This will create an MSP file that you can use for the silent installation.

In order to install it, run the following command line:

setup.exe /adminfile <pathToMsp>

However, there’s also the possibility of using a configuration xml file for the silent installation, based on the template config.xml that can be found in the core_product_folder_name.WW folder.

Also, an XML file can be created for a silent uninstall.



OCT is available for Office (2007 or later) but other related software such as Microsoft Lync, Visio, Project, OneNote etc.

Internet Explorer Silent Installation and Uninstall

This article applies to Internet Explorer 9, Internet Explorer 10 and Internet Explorer 11.

Internet Explorer Silent Installation


IE 9 can be downloaded here. SourceFile = IE9-Windows7-x64-enu.exe
I’ve downloaded the English 64bit version, for Windows 7. It’s not really relevant, the command line will be the same.

IE 10 can be downloaded here. SourceFile = IE10-Windows6.1-x64-en-us.exe
IE 11 can be downloaded here. SourceFile = IE11-Windows6.1-x64-en-us.exe

Silent Install

PathtoSourceFile\SourceFile /quiet /update-no /norestart /log:LogFolder

Attention: the log parameter refers to the folder in which a log file will be created.

With this command line, you can safely upgrade an existing installation; no extra actions are required.

Internet Explorer Silent Uninstall (Rollback)

Uninstalling is the trickier part.

Create a batch file with the following content:

FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*~XXX.?.????.?????.mum /c “cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /norestart /quiet”

where XXX is “9”, “10” or “11”, depending on which version you need to remove.
This command line will remove the mum files belonging to the corresponding version of IE, from Windows\servicing\Packages.

The end result will be a rollback to the previous version of IE. If you’re uninstalling “11” and you had 9, then that’s what you’ll obtain. If you apply the same removal procedure for “9”, then you’ll rollback to 8 or whatever was present on the machine initially.

A reboot will be needed after each installation OR uninstall.

Error 40007

If, during the installation of IE, you get an error code of 40007, it means that some prerequisites (hotfixes) are missing. It can also be that they’ve just been installed, but the PC hasn’t rebooted. Reboot the machine and try the installation again.

Silent Installations using Inno Setup

Inno Setup is a free installer for Windows software. It is not as popular as Windows Installer (MSI), but still widely used.

Applications distributed using Inno Setup can usually be installed silently, unless there are custom actions that didn’t take into consideration the scenario of a silent install.

The most used parameters of an Inno Setup are:

/SILENT – Runs the setup silently. The wizard and the background window are not displayed. However, the installation progress will be shown. In case of a necessary reboot, if the /NOREBOOT parameter is NOT mentioned, there will be a prompt asking for reboot.
/VERYSILENT – Same as /SILENT, but it doesn’t show the progress. If the /NOREBOOT switch is not used and a reboot is needed, the setup will automatically restart the machine.
/LOG=”filename” – logs the installation to a file. Quotes are important.
/NORESTART – suppresses the reboot messages and instructs setup not to restart when the installation is done, even if it’s needed.
/SAVEINF=”filename” – saves the installation configuration to the specified file. Quotes are important.
/LOADINF=”filename” – loads a previously saved installation configuration.

Other switches:
/SUPPRESSMSGBOXES – only when combined with the /SILENT and /VERYSILENT switches, it suppresses most of the dialog boxes. When there’s a choice, it uses the default option (No for overwriting files, Abort when there’s an Abort/Retry option, Yes when asked about keeping a newer file, Yes for restart).
/SP- – disables the “This will install…” prompt at the beginning.
/CLOSEAPPLICATIONS – Closes applications that hold files needing to be updated.
/NOCLOSEAPPLICATIONS – Prevents the setup from closing applications that hold files needing to be updated.
/RESTARTAPPLICATIONS – Applications closed by the setup will restart.
/NORESTARTAPPLICATIONS – Closed applications will not restart.
/DIR=”path” – Sets the installation directory. It overrides whatever the user has mentioned in the Select Destination Path wizard page. Full path.
/GROUP=”folder name” – Provides the name of the shortcut folder.
/NOICONS – No shortcuts created.
/TYPE=typeName – Overrides the default setup type (Complete, Custom, Minimal)
/COMPONENTS=”component1,component2,etc” – selects a list of components to be installed
/TASKS=”task1,task2,etc” – selects a number of tasks (such as desktopicon, fileassoc)
/MERGETASKS=”task3,task4″ – adds additional tasks to the default ones.
Both task params can also negate (!) a task: !desktopicon
/PASSWORD=password – specifies a password to use

For Uninstall, the unins000.exe (or higher index) from the installation directory must be called, with one of the following parameters:

Adobe Flash Player 12 Silent Installation

For the deployment of Adobe Flash Player 12, one needs to apply for a distribution license (link here). Afterwards, you’ll receive a link where you can download the two MSIs:



Install them silently, using the following command lines:

msiexec /i “sourceFolder\install_flash_player_12_active_x.msi” REBOOT=ReallySuppress ALLUSERS=1 /qn /L*v C:\WINDOWS\Temp\flash_player_12_active_x.log

msiexec /i “sourceFolder\install_flash_player_12_plugin.msi” ” REBOOT=ReallySuppress ALLUSERS=1 /qn /L*v C:\WINDOWS\Temp\flash_player_12_plugin.log

Most probably, you`ll also want to disable the Auto Update feature. You can do that by creating/copying a file called mms.cfg in Windows\System32\macromed\flash\ (Or Windows\syswow64\macromed\flash for 64bit installations). The file must contain the following 3 lines:




To do a silent uninstall, run msiexec /x productCodeHere /qn /l*v logFileName for each msi, using its product code.

SAP Visual Enterprise Client Silent Installation

Assuming that you have the installer from SAP, called VisualEnterpriseViewer_7.0.1.178_Complete.exe, this is how to install SAP Visual Enterprise Viewer silently.

There is an easy way to install it with default options:

VisualEnterpriseViewer_7.0.1.178_Complete.exe /Silent

But that’s not the way we would recommend. There’s a more elegant way of doing it.

  1.  First, unzip the executable to a folder of your choice.
  2. Run Setup\NwSapSetupAdmin.exe
  3. Create New Package. Give it a relevant name, for example: “SAPVisualEnterpriseViewer_7.0.1.178_Complete”
  4. Customize your installation by selecting the desired options
  5. Close it.

Your SAP “package” info will be stored in Setup\SapPackageSetup.xml

In order to install it silently, run the following command line:

Setup\NwSapSetup.exe /Silent /Package=”SAPVisualEnterpriseViewer_7.0.1.178_Complete”

Log files will be created under %ProgramFiles%\SAP\SapSetup\LOGs (or ProgramFiles(x86) ).


For a silent removal of the package, run the following command line:

%ProgramFiles%\SAP\SapSetup\NWSapSetup.exe /uninstall /Product=”DVM+DVC” /Silent

(Or %ProgramFiles(x86)% )




Adobe Shockwave Player 12

In order to deploy Adobe Shockwave Player, you must first apply for a distribution license here.

Download the MSI file.

For a silent installation with no extra configuration, run the following command line:

 msiexec /i sw_lic_full_installer.msi /qb

That’s it.


IF you want to disable the AutoUpdates and/or CollectStatistics (or other options), you can do that easily by editing the corresponding registry values, in an MST:

SOFTWARE\Macromedia\Shockwave 10\collectstats

SOFTWARE\Adobe\Shockwave 12\collectstats

SOFTWARE\Macromedia\Shockwave 10\AutoUpdate

SOFTWARE\Adobe\Shockwave 12\AutoUpdate

SOFTWARE\Adobe\Shockwave 12\AutoUpdate

SOFTWARE\Macromedia\Shockwave 10\CollectStatistics

SOFTWARE\Macromedia\Shockwave 10\CollectStatistics

SOFTWARE\Adobe\Shockwave 12\collectstats

Set them all to n.

Other options can be found in SOFTWARE\Adobe\Shockwave 12\


SAP BusinessObjects BI platform 4.0 SP4 Client Tools

The product has two installations, one for the product itself (4.0 Client Tools) and a second one for the SP4 update.

The same principles can be applied to the installation of Crystal Reports 2011 + update.

The best practice in this case turned out to be a silent installation with response files. The reason? The installation is very large. Tens of subproducts are installed by the two setups. You don’t want to capture in an MSI.
Let’s suppose we have two folders, one for each of the installers. We’re going to create the response files for each setup.

The command line for that is setup.exe -w C:\PathToFile\InstallResponseFileName.ini
The installation wizard starts. Feel free to change the options according to your needs. When the dialogs end, the response file is created.

In order to use the response file, the command line is: setup.exe -r c:\PathToFile\InstallResponseFile.ini

For the main installation (4.0 Client Tools), you need to do this routine 3 times:
– once for the installation (I0) – when the product is not installed yet
– once for the repair (make sure you install the product first) (R0) – when the product is already installed
– once for the uninstall (U0) – when the product is already installed

Another set of response files will be made for SP4 update (4.0 SP4 Client Tools). This time we’ll only do it twice:
– once for the installation (I1) – when the update is not installed
– once for the uninstall (U1) – when the update is already installed.
The SP4 doesn’t provide a repair functionality, it’s done by the main product. The updated components will be repaird, it has been checked.

If everything went smooth, we should have now 5 response files: 3 for the main installation, 2 for the update. Make sure you give them suggestive names, such as: response_uninstall_sp4.ini.
Now, if you have an install and an uninstall wrapper, here’s what you need to do:


Check if the Product is installed
Start Repair of the main product (R0)
Install the main product (I0)

Check if the SP4 is installed
Install SP4 (I1)


Check if SP4 is installed
Uninstall SP4 (U1)

Check if the main product is installed
Uninstall the main product (U0)

I should also mention that each installation has it’s own registry key under Uninstall. Even more, the main installation key changes when SP4 get installed/uninstalled. These keys can be used to check if the products are installed or not.

That’s it. Enjoy and good luck.

P.S. If you encounter any problem doing this or if the explanation is unclear, please let us know. Feedback is appreciated.

Citrix Online Plugin 12.3 Silent Installation


One of our customers needed recently a package for the Citrix Online Plugin, version 12.3. We were given an exe file: CitrixOnlinePluginFull.exe (16.3 MB) made by Citrix System and a list of command line params (they’re not relevant yet).

The EXE file is an archive and contains 6 msi files and some auxiliary tools used during the installation. The installation can be done using the EXE file directly, or by installing the needed MSIs one by one.


I. Installation using CitrixOnlinePluginFull.exe

The EXE can be installed and uninstalled silently by using the /silent command line parameter.

A list of parameters can be found on the Citrix’s support website.

The most important are

  • /silent – used to run a silent installation
  • /noreboot – used to prevent a reboot of the machine
  • ADDLOCAL=”features” – selects the features/products to be installed
    • example: ADDLOCAL=”ICA_Client,PN_Agent,SSON,Flash,USB” – this will install the 5 features (out of 6)
  • /uninstall – obviously, used for uninstall
  • Properties can be passed to the MSIs:
    • ENABLE_SSON=yes

Please check the full list of parameters in order to see which can be useful if you need to do a silent installation or a package for this.

Cisco claims that THIS is the recommended way to go, because of future possible updates. They might fail if you decide to extract the MSIs or choose a different way. There is, however, an issue with it: there is no repair functionality provided. That means that if something affects the integrity of the software (i.e. deleting certain files from Program Files\Citrix\ICA Client), the setup won’t be able to repair. You can try by removing all the EXEcutables from that folder. What will happen? The re-installation will fail constantly. The uninstallation as well. You’ll be stuck with a non-working citrix client and no way to fix it.

Sometimes, the EXE might fail because its location has a very long path.

That’s why we chose option #2:


II. Installation using the extracted MSIs

First, we need to extract everything from the EXE. Use your default compression tool and extract the files in a single folder.

According to Cisco, the MSIs have to be installed in the following order:

  •     ICAWebWrapper.msi
  •     SSONWrapper.msi
  •     GenericUSB.msi
  •     DesktopViewer.msi
  •     CitrixHDXMediaStreamForFlash-ClientInstall.msi
  •     PNAWrapper.msi

For the uninstall, the order has to be reversed (start with PNAWrapper).

You should also know that the MSIs accept extra parameters (properties).

  • ICAWebWrapper.msi – you can pass ENABLE_DYNAMIC_CLIENT_NAME=Yes to it
  • SSONWrapper.msi – it can use ENABLE_SSON=yes
  • PNAWrapper.msi – it uses SERVER_LOCATION=.. and SILENT=1. The latter is used in a custom action launch condition. Set it to 1 if you do not want the process PNAMain.exe to start.

The MSIs have to be launched from a location that has a not too long path. Copying them somewhere on C drive will do the trick. Otherwise, they might fail.

Using this option will give you install/repair/uninstall functionality and more control over the package components.