Home
Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
Installing and upgrading Notes® clients
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.
Customizing Notes® install using the tuner
Some aspects of Notes® installation can be customized to allow you to control the options that are installed and/or available to users. You can use the InstallShield tuner for Notes to customize many aspects of Notes installation on a Microsoft™ Windows™ client, using the .msi and .itw files supplied in the Notes install kit to create a unique transform (.mst) file.
Example: Applying scriptable setup using a transform during Notes® install
You can apply NOTES.INI settings during Notes® install using a transform file. This example uses the CONFIGFILE= setting to point to a setup text file that contains the parameters for the post-installation phase of Notes client setup.

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.
- Downloading and distributing software using AutoUpdate
  AutoUpdate notifies you of the latest HCL Domino and Domino product family available on the Domino server, and allows you to download the software. You can also use it to distribute software to groups or selected 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.
    - Customizing Notes® install for features and plug-ins on Windows™ and Mac
      You can customize the Notes® install kit to add new or third-party features at install or upgrade or to remove certain supplied features from the kit prior to install or upgrade using the procedure outlined here.
    - Installing and subscribing to preset feeds
      The deploy\extras folder in the Notes® install kit contains a PRESETFEEDS.OPML XML file in which preset feed subscriptions are supplied. You can edit this file to contain the default feeds you want. Check the Notes install kit's PRESETFEEDS.OPML file for the latest default preset feed subscriptions.
    - Customizing Notes® install using the tuner
      Some aspects of Notes® installation can be customized to allow you to control the options that are installed and/or available to users. You can use the InstallShield tuner for Notes to customize many aspects of Notes installation on a Microsoft™ Windows™ client, using the .msi and .itw files supplied in the Notes install kit to create a unique transform (.mst) file.
      - Obtaining a tuner and creating a transform file to customize Notes® installation
        You can use an MSI tuner to create a transform file or new setup installation executable for customizing some aspects of Notes® install or upgrade. You can then specify that the Notes installer uses the values in the transform files instead of default values.
      - Example: Using msiexec command line utilities for installing Notes®
        You can use the msiexec command line statement to install Notes® by specifying the .msi file, and optionally the .mst file, to use during installation.
      - Example: Applying scriptable setup using a transform during Notes® install
        You can apply NOTES.INI settings during Notes® install using a transform file. This example uses the CONFIGFILE= setting to point to a setup text file that contains the parameters for the post-installation phase of Notes client setup.
  - 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.
  - 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.
- Upgrading
  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.

Example: Applying scriptable setup using a transform during Notes® install

You can apply NOTES.INI settings during Notes® install using a transform file. This example uses the CONFIGFILE= setting to point to a setup text file that contains the parameters for the post-installation phase of Notes® client setup.

About this task

The setup.txt file can be placed on shared network resource or distributed to individual user desktops.

Note: For more information about using scriptable setup, see the topic Setting up Notes® installation using scriptable setup in the related information. For information about using the tuner, see Obtaining a tuner and creating a transform file to customize Notes® installation.

Procedure

Create a setup.txt file using the following parameters. Save your file as setup.txt.
- IM.server=ServerName1.domain.com
- IM.port=1533
- IM.ConnectWhen=0
- IM.Protocol=0
To allow the new setup.txt file to be referenced, open the NOTES.INI file and add this setting:
```
ConfigFile=\\Path_To_File\SETUP.TXT
```
Use the InstallShield Tuner for Notes® to create a transform file (.mst) to distribute the new ConfigFile= setting in the NOTES.INI file.