Home
Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
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.
Configuring AUT servers
To configure Domino servers to be AUT servers, configure TLS on the servers and then create a Configuration document for the AUT servers.
Setting up TLS on AUT servers
HCL Notes® clients connect to AUT servers over secure HTTPS connections. Before you configure AUT servers, complete this procedure to create an TLS certificate on AUT servers.

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.
    - Configuring AUT servers
      To configure Domino servers to be AUT servers, configure TLS on the servers and then create a Configuration document for the AUT servers.
      - Setting up TLS on AUT servers
        HCL Notes® clients connect to AUT servers over secure HTTPS connections. Before you configure AUT servers, complete this procedure to create an TLS certificate on AUT servers.
      - Creating a Configuration document for AUT servers
        After you set up TLS on the AUT servers, create a group for the AUT servers in the Domino directory and then create a Configuration document that is associated with the group. The Configuration document enables the servers for AUT and specifies a server DNS (an AUT server or a round-robin DNS name) that Notes clients connect to check for updates.
    - Ways to add Notes install files to the AUT catalog
      With HCL Domino 14.0 Fixpack 1, you get an additional option for adding HCL Notes to the Notes AUT Catalog as a means of distributing Notes to AUT servers. Note that this capability applies only for Notes, not HCAA.
    - Creating a Version Path document to upload a new HCAA install file to AUT servers
      To prepare to deploy a new version of HCL Client Application Access (HCAA) on AUT servers, create a Version Path document to define and upload the install executable file for the new version into the AUT Catalog. You also define in the document which version or versions of HCAA can be upgraded to the new version.
    - Creating a Version Map to assign upgrade paths to users
      To deploy a new Notes version to users, you create a Version Map document in the AUT Catalog in which you select one or more Version Path documents that define an upgrade path.
    - Use Desktop Settings to enable clients to install updates
      After you've used the AUT Catalog to deploy a new install executable file on the AUT servers, use the Client Upgrade > AUT tab in Desktop Settings policy to specify on which users' clients the package is installed.
  - 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.
  - 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.

Setting up TLS on AUT servers

HCL Notes® clients connect to AUT servers over secure HTTPS connections. Before you configure AUT servers, complete this procedure to create an TLS certificate on AUT servers.

To create a TLS certificate on AUT servers, generate a TLS SHA-2 certificate in a keyring file, deploy the keyring file on the AUT servers, and import the certificate into the Domino® Directory of the AUT servers.

Next, create a Configuration document in the Domino Directory for AUT servers according to which procedure applies to your Domino version:

Domino 12.0 servers and later

For Domino servers running 12.0 and later, to set up TLS it is best to use the Certificate Store application (certstore.nsf) with the TLS credentials document needed for an Internet site. For more information, see Certificate management with CertMgr.
For the AUT download site, create a TLS credentials document in certstore.nsf with the fully qualified hostname of the AUT download site.
If you have existing keyring files for the same hostname, you can import them certstore.nsf as described in Upgrading TLS credentials.
Update the Keyring file name field for the AUT Internet site in the Domino Directory, using the same hostname that is specified in the TLS Credentials document in certstore.nsf.

Domino 10.0.1 and 11.0.1 servers

Use OpenSSL (available on the Internet) and KYRTool (installed with Domino) to generate the keyring file for the AUT Servers to use. For instructions, see the article How to set up SSL using a third-party Certificate Authority (CA) on the HCL Software Support site.
Copy the keyring file to the data directory of each AUT server.
Import the certificate into the Domino Directory:
1. Copy the Internet certificate file to your Domino Administrator client computer.
2. From the Domino Administrator, click the People & Groups tab and the Certificates view.
3. Click Actions > Import Internet Certificates.
4. Browse for and open the local certificate file.
5. Verify that the certificate is selected in the Open Internet Certificates box and then click Accept All.
6. Click View > Refresh and verify that the new certificate is now displayed in the Certificates view of the Domino Directory.