Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
- Installing and upgrading Domino® servers
  Perform a new or upgrade install of one or many Domino® servers.
- Installing and upgrading Notes® clients
  - Notes® Auto Update
    You don't have to rely on third-party products to automate deployment of new versions and updates of HCL Notes® or HCL Client Application Access (HCAA). Instead, you can enable Auto Update (AUT) servers to deploy updates automatically.
  - Customizing Notes® installation
    As an administrator, you can customize the Notes® install and upgrade process for your users to install just the features that they need. For example, you can customize the install kit using MSI tuner capabilities and you can also customize the install kit to add or remove Eclipse-based features.
  - Specifying custom data directories for multi-user install or upgrade
    You can configure Notes® custom data directories during Notes multi-user install or upgrade on Windows™ or Citrix XenApp.
  - Understanding the Notes® single user to multi-user migration assistant tool
    The single-user to multi-user migration tool converts a Notes® single-user installation to a multi-user installation.
  - Using the Notes® Install Cleanup Utility (NICE) tool
    You can use the supplied Notes® Install Cleanup Executable (NICE) tool to clean up a failed install, failed uninstall, or failed upgrade. You can also use the tool to uninstall an existing version of Notes, and clean up extraneous files, before performing an upgrade installation. The tool is available for Notes on supported Windows™ platforms only, and must be run by an administrator.
  - Automating a customized or default Notes® deployment using silent install
    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.
    - 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.
  - Installing and upgrading Notes® in a single user environment
    You can install Notes® on Microsoft™ Windows™ or Citrix platforms in a single user environment using either the Notes-only or the Notes Allclient installer.
  - Installing and upgrading Notes® multi-user
    Installing Notes® in a multi-user user environment enables multiple users to sequentially log in to the same machine and use the same Notes install directory with their own Notes data directory.
  - Installing a non-English version of Notes®
    Notes® is available for install and upgrade in multiple languages.
  - Adding or removing installed Notes® features within a release
    Optionally add new features, or remove installed features, by rerunning the Notes® installation executable within the same release.
  - Managing client plug-in deployment
    While you can customize your client installer to add new or remove supplied features and plug-ins when you install or upgrade your clients, you can also provision (install and automatically update) stand-alone or third party features and plug-ins to your existing Notes® or Lotus® Expeditor run-time using a combination of Domino® policy or Eclipse preferences, a widget resident in a widgets catalog on an HTTP or Domino server, and a Eclipse update site (with signed features and plugin .jar files) optionally resident in a centrally managed NSF-based update site.
  - Uninstalling Notes®
    While it is not necessary to uninstall Notes® to upgrade to a new release, you should uninstall a Beta release before upgrading.
- Planning your upgrade to Notes and Domino 12.0.2
  Use this documentation to upgrade the existing Domino® server and subsequently upgrade the Notes® client to a new release. You can also upgrade additional clients such as Domino Administrator and Domino Designer clients and additional features and plug-ins such as the embedded HCL Sametime® client.

Automating a customized or default Notes® deployment using silent install

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 Notes version.msi file supplied in the Notes® install kit)
A transform file (.mst) is created by using the supplied HCLNotes.itw and HCL Notes version.msi files 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.INI file 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.

For related information about automating a Notes® upgrade from one release to another using the Notes® SmartUpgrade and/or SURUNAS procedures see Using Notes® Smart Upgrade and Using the Smart Upgrade Run-As wizard.