Windows Unattended Installation

Unattended Installation Overview

Default:

• An unattended operation does not prompt the user for input; instead, it gets input from properties passed to the installation file on the command line.

• These properties are described in the Command Line Reference.

• No messages are displayed during unattended installation, upgrade, reinstallation, or uninstallation.

Step 1: Before Beginning

Default:

• Before beginning your installation, perform the necessary pre-installation steps.

• Determine your strategy for installing an external web server:

  • The easiest option is to install Microsoft Internet Information Services (IIS) before beginning the installation. The installer can auto-configure this web server.

  • If you intend on using a different web server or manually configuring the IIS web server, review Installing a Web Server for necessary steps that must be performed prior to the installation.

Step 2: Determine Properties to Specify

Default:

• You do not need to include any additional properties to perform a basic unattended installation. The installer will use the default options.

More:

• Review details on using command-line properties.

  • Use the form: PROPERTYNAME=argument.

  • Properties must be upper-case.

  • Arguments are not case-sensitive.

  • Each property must be separated by one or more spaces.

• Refer to the Command-Line Properties Reference for the properties available for unattended installations.

• Make a note of any properties you will use for your unattended installation.

Step 3: Determine Features to Install

Default:

• The ADDLOCAL property is used to determine which features to install.

• If it is left blank, it defaults to ADDLOCAL=ALL which installs all features.

• For a basic development environment, there is no need to include this property. All features will be installed.

More:

• Review details on specifying custom-installable features.

  • Use the ADDLOCAL property to specify which features to include.

  • Specify the featurename of a component group, followed by the featurename components within that group separated by a comma. Repeat this for each component group to create a comma-separated list.

• Refer to the Custom-Installable Features References for available features.

Step 4: Create Installation Command

Default:

• Use the following command:

  <path>\<installer>.exe /instance <instancename> /q{b|n} <properties>
  

  

  where:

  • <path> — The path to the installation file.

  • <installer>.exe — The name of the installation file. If omitted, the default path is C:\InterSystems\IRISn, where n is {empty}, 1, 2, ... 127.

  • <instancename> — The name for the new instance. If omitted, the default value is IRISn, where n is {empty}, 1, 2, ... 127.

  • /qb or /qn — Whether to display a progress bar during the installation (/qb) or to perform a fully silent installation (/qn).

  • <properties> — The properties to passing to the installer (see the Command-Line Properties Reference).

More:

• Replace <properties> with any properties you would like to include in the installation.

• Use the ADDLOCAL property to specify which features you would like to install.

Examples:

• Install an instance with the default instance name in an installation directory named C:\InterSystems\MyIris on a 64–bit windows system:

  C:\downloads\IRIS-<version_number>-win_x64.exe /qn INSTALLDIR=C:\InterSystems\MyIris
  

  

• Install an instance with the instance name IrisA:

  C:\downloads\IRIS-<version_number>-win_x64.exe /instance IrisA /qn
  

  

• Install a subset of features using the ADDLOCAL property:

  C:\downloads\IRIS-<version_number>-win_x64.exe /qn ADDLOCAL=cube, server, server_user
  

  

Step 5: Install the Instance

Default:

• Execute the command, including any properties, using a command-line interface.

• Once the Installation finishes, proceed to Windows Post-Installation.