HCLSoftware Business Partner
Domino Consulting Services
CRUCIAL Notes Tools
+1 212-599-2048

Domino Consulting Services
CRUCIAL Notes Tools
Domino administration
Notes development

Facebook Twitter YouTube
Chat now       
.
ProductsDownloadsNewsAbout usContact


Need a Domino Consultant? Call NotesMail +1 212-599-2048 - HCLSoftware Business Partner

INSTALLING

Performing a Notes silent install or upgrade on Windows

MSI command line arguments are available, and may be required, for running a Notes® command line install to add or remove Notes client features during initial install, release upgrade, or within the same Notes release.

Before you begin

You must be logged in as an administrative user or user with elevated privileges to install or upgrade Notes.

About this task

Run the Notessetup.exe from the directory in which it resides locally.

Note: ADDFEATURES and REMOVEFEATURES properties are available only as command line arguments when using a Notes silent install. These properties can be set directly on the command line or used within an MSI Transform file during silent installation mode only. To control the feature selections in the feature panel in the UI mode, use the Notes install manifest (install.xml) file settings or consider using the UpdateSiteMgr tool supplied with the Notes install kit.

The Notes features that can be included on the MSI silent install command line are as follows:

  • Notes.Designer.Install -- Notes single user install only (Allclient kit)
  • Notes.Admin.Install -- Notes single user install only (Allclient kit)
  • Activities -- Connections
  • SametimeUI -- Embedded HCL Sametime®
  • Feedreader -- Feeds sidebar panel
  • CAE -- Composite Applications Editor
  • ALL -- All available MSI options and all features available for install as specified in the Notes install kit’s install manifest(install.xml)

Feature names are as shown in the following table. See Running a silent install or upgrade using optional arguments and Calling a transform file during Notes silent install for command line options not described in the following examples.

Table 1. Using ADDFEATURES during Notes upgrade
ScenarioCurrently installedCommand lineResult
Adding Activities when upgrading Notes Allclient 8.5 and CAEADDFEATURES=ActivitiesUpgrade CAE. Install Activities/Connections.
Upgrading with no changesNotes Allclient with default features installedsetup.exe /s /v"/qb+"Upgrade all the default features that were installed with the earlier release.
Upgrading and adding ALL featuresNotes client with only Notes installedADDFEATURES=ALLUpgrade Notes and install ALL optional MSI features. Install ALL optional install manifest (install.xml) features.

Table 2. Using REMOVEFEATURES during Notes upgrade
ScenarioCurrently installedCommand lineResult
Removing Activities when upgrading Notes Allclient with CAE, Activities/ConnectionsREMOVEFEATURES=ActivitiesUpgrade CAE. Uninstall Activities/Connections.

Table 3. Using ADDFEATURES within the same release
ScenarioCurrently installedCommand lineResult
Adding Activities after re-running setup.exe Notes with CAEADDFEATURES=ActivitiesInstall Activities/Connections.
Modifying with no changes Notes Allclient with default features installedsetup.exe /s /v"/qb+"Leave everything as is.
Modifying the install to add ALL featuresNotes client with only Notes installedADDFEATURES=ALLInstall ALL optional MSI features. Install ALL optional manifest (install.xml) features.

Table 4. Using REMOVEFEATURES within the same release
ScenarioCurrently installedCommand lineResult
Removing Activities Notes with CAE, Activities/ConnectionsREMOVEFEATURES=ActivitiesUninstall Activities/Connections.

Examples are as follows:

  • Using the REMOVEFEATURES argument when removing Notes features silently

    Use the REMOVEFEATURES argument to uninstall named features during an upgrade install or on re-running an install for the same release. Sample REMOVEFEATURES command line syntax is as follows:

    setup /s /v"REMOVE=Name of the feature to be uninstalled

    For example, when rerunning the Notes command line installer to remove Activities, you would use the following command line:

    setup /s /v"REMOVE=Activities /qb+

  • Using the ADDFEATURES argument when installing Notes features silently

    Use the ADDFEATURES argument to install named features during an upgrade install or on re-running an install for the same release. Sample ADDFEATURES command line syntax is as follows:

    setup /s /v"ADDFEATURES=Name of the feature to be uninstalled

    For example, to add the CAE and Feedreader, use the following command line:

    setup /s/v"ADDFEATURES=CAE,Feedreader /qb+"

    You can optionally use SELECTINSTALLFEATURES to install these named features:

    setup /s /v"SELECTINSTALLFEATURES=Feedreader /qb+

  • Using the ADDFEATURES and REMOVEFEATURES arguments together

    You can use ADDFEATURES and REMOVEFEATURES arguments when upgarding to a new Notes release and installing or removing Notes features silently. You can add and/or remove MSI-only features, Notes install manifest-only features, and hybrid features during a silent installation. You can combine ADDFEATURES and REMOVEFEATURES in a single command line. For example, to add Activities but remove the Feed Reader you could use the following command:

    setup /s /v"ADDFEATURES=Activities REMOVEFEATURES=Feedreader /qb+

    There are instances where the ADDFEATURES and REMOVEFEATURES command line arguments cannot be used on the same command line. The ADDFEATURES=ALL and REMOVEFEATURES arguments cannot be used in the same command. As well, you cannot specify the same features in both the ADDFEATURES and REMOVEFEATURES arguments in the same command. However, you can use these two arguments in the same command if they specify different features. For example, the following command is not supported:

    setup.exe /s /v"SETMULTIUSER=1 ADDFEATURES=ALL REMOVEFEATURES=SametimeUI,Feedreader /L*v c:\temp\log852.log /qb+


Additional examples are as follows:
  • To perform a Notes silent multi-user install or upgrade , use the SETMULTIUSER=1 command line statement:

    setup.exe /v"SETMULTIUSER=1 /qb"

  • To run the install in silent mode, using default values, without a progress bar, use the following syntax:

    setup.exe /s /v"/qn"

    Note: For example, this command installs Notes to the single user default C:\Program Files\HCL\Notes directory and Notes data folders and files to the C:\Program Files\HCL\Notes\data directory.

  • To display a message when installation is complete or if install fails, use the + parameter as follows:

    setup.exe /s /v"/qn+"

  • To display a progress bar during the installation, in addition to displaying the message indicating that the installation is complete or it has failed, use the following syntax:setup.exe /s /v"/qb+"
  • To specify a non-default destination directory, for example C:\HCL\Notes, use the following syntax:

    setup /S /V"ADDFEATURES=ALL PROGDIR=C:\HCL\Notes DATADIR=C:\HCL\Notes\Data /qn"

    Note: Each feature in the Notes install manifest (install.xml) for which the required attribute is set to true will be installed.

  • To specify which install manifest features to install, obtain theinstallfeature ID syntax from the Notes install manifest (install.xml). To install any of these features, include the feature ID value in the ADDFEATURES property on the command line. Specify comma-separated names in quotes as follows.

    Note the placement of the quote, equals sign, and space characters.

    setup /s /v"ADDFEATURES=Activities,SametimeUI,CAE /qn"


Parent topic: Automating a customized or default Notes deployment using silent install

Related concepts
Running a Notes silent install or upgrade using optional arguments
Considerations when planning a Notes silent install or upgrade
Example: Using setup.exe to call a transform file during Notes silent install
Customizing Notes install using the tuner
Considerations for installing and upgrading Notes on Windows
Eclipse files and folders in the Notes install kit
Installing a non-English version of Notes

Related tasks
Obtaining a tuner and creating a transform file to customize Notes installation
Example: Using msiexec command line utilities for installing Notes
Example: Creating and providing a batch file for Notes silent install
Customizing Notes install for features and plug-ins on Windows and Mac
Adding and removing components from the Notes install kit using UpdateSiteMgr