You can use a silent install to deploy a default or customized Notes® release to users without user intervention. This enables centralized Notes install or upgrade deployment to many users without requiring user intervention.

To automate Notes installation and upgrade using a silent install or upgrade deployment, you can use any of the following customization tools separately or in conjunction with one another:

• Customized Notes install kit – customized Notes install manifest (install.xml file in Notes install kit) and updateSite folder contents

  You can customize the Notes standard configuration install kit to add additional third party features and plug-ins, remove certain supplied features (Composite Applications Editor, HCL Connections (Activities), and embedded HCL Sametime®). You can also control feature install visibility and default options in the Notes installation panels or silent install prompts.

  All features in the install manifest that have their required attribute set to true are installed. However, you can also specify features from the Notes install manifest as command line arguments.

• MSI transform file (a .mst file based on the HCL Notesversion.msi file supplied in the Notes install kit)

  A transform file (.mst) is created by using the suppliedHCLNotes.itw and HCL Notes version.msifiles in conjunction with the InstallShield Tuner for Notes, to configure various aspects of what you want installed and how.

  You can use a transform file to control certain settings or install options such as the following.

  Note: A transform can be used in conjunction with various silent install command line options and/or a customized Notes install kit.

  • certain Domino® policy or NOTES.INIfile settings
  • single or multi-user install type
• For details on creating a transform file, see Obtaining a tuner and creating a transform file to customize Notes installation in the related information.
• Silent install command line options

  Notes silent install can be run with or without MSI command line options to allow for further customization.

Considerations when planning a Notes silent install or upgrade
Silent install is useful for installing, reinstalling, or upgrading Notes on the MSI command line or as part of a script or batch file process.

Running a Notes silent install or upgrade using optional arguments
You can use optional command line arguments when running a Notes install or upgrade from the MSI command line.

Using the install manifest "default" setting for silent feature specification
During a silent install, specify the features to install using the following information as a guide.

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.

Installing Notes silently using the cascaded MUI pack (Windows)
You can install Notes silently using the cascaded Multilingual User Interface (MUI) pack. The cascaded MUI pack installs the English version of Notes and translated MUI packs at one time.

Example: Using setup.exe to call a transform file during Notes silent install
You can optionally call a transform file (.mst) during Notes silent install on a supported Windows platform.

Performing a Notes silent install on Mac OS X
You can run a Notes silent install on Mac OS X.

Example: Creating and providing a batch file for Notes silent install
You can create and provide a batch file for users that executes a Notes silent install.

Example: Sharing command line utilities for installing Notes
You can provide command line utilities to users to enable them to more easily install Notes themselves.

Setting up Notes installation using scriptable setup
The scriptable setup option uses the CONFIGFILE= setting in the NOTES.INI file to provide user information for the setup phase of the Notes installation program.

Related concepts
Customizing Notes installation
Using Notes Smart Upgrade
Using the Smart Upgrade Run-As wizard
Considerations when planning a Notes silent install or upgrade
Running a Notes silent install or upgrade using optional arguments
Using the install manifest "default" setting for silent feature specification
Customizing Notes install using the tuner
Example: Using setup.exe to call a transform file during Notes silent install

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