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.
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.
Using the AUT Catalog to upload new Notes versions
When a new version of HCL Notes® or HCL Client Application Access becomes available that you want to deploy, you use the AUT Catalog (autcat.nsf) to upload its install executable file to 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, distributing, and installing 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, and optionally, install, 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.
    - 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.
      - Using the AUT Catalog to upload new Notes versions
        When a new version of HCL Notes® or HCL Client Application Access becomes available that you want to deploy, you use the AUT Catalog (autcat.nsf) to upload its install executable file to AUT servers.
        Creating a Version Path document to upload a new Notes install file to AUT servers
        To prepare to deploy a new version of Notes 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 Notes can be upgraded to the new version.
      - Pushing Notes installs to the AUT Catalog using Domino AutoUpdate
        Starting in Domino 14.0 Fixpack 1, the Domino AutoUpdate app contains functionality that you can use to have Notes installation sofware pushed to the Notes AUT Catalog.
    - 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.

Using the AUT Catalog to upload new Notes versions

When a new version of HCL Notes® or HCL Client Application Access becomes available that you want to deploy, you use the AUT Catalog (autcat.nsf) to upload its install executable file to AUT servers.

About this task

The following tables describes AUT Catalog terms to become familiar with before you upload your first install executable.

Table 1. AUT Catalog terms
Term	Description
Version Path	A required document that you create in the AUT Catalog to define and upload an install executable file for a new version of Notes, to prepare for deploying it to AUT servers. A Version Path defines: Type of client kit (platform). For example, for a Notes client StandardAllClient-Win32, StandardNotesClient-Win32, or BasicNotesClient-Win32. Or, for an HCL Client Application Access (HCAA) client, HCAA-Win32. Version(s) to upgrade from; Version to upgrade to. For example, a Version Path document could define an upgrade of Notes StandardNotesClient-Win32 from 10.0.1 to 10.0.1 FeaturePack 1.
Version Map	A required document that you create in the AUT Catalog that lists at least one Version Path to apply to a set of users. Selecting a Version Map in the Client Upgrade > AUT tab in a Desktop Settings policy is required to upgrade clients of a group of users. A Version Map can list multiple Version Paths. For example, a Version Map that lists the following two Version Paths allows both Notes standard and basic clients to be upgraded: Upgrade StandardNotesClient-Win32 from 10.0.1 to 10.0.1 FeaturePack 1 Upgrade BasicNotesClient-Win32 from 10.0.1 to 10.0.1 FeaturePack 1
Install manifest	An XML file that describes an install executable file that is provided with the web download kit for a new Notes or HCAA version. It provides information such as the release number, the type of client, the language, and the name of the install executable file. When you create a Version Path document, you can import the install manifest so the install executable file information is populated for you. Here's an example of install manifest content for Notes: `<?xml version="1.0" encoding="utf-8"?> <manifest appid="{3E1B33CC-8C2E-4EED-B6A2-3BB3EE0ACFF1}" name="StandardAllClient-Win32" version="Release 10.0" lang="en"> <packages> <package name="setup10.0.exe" size="81830632" hash="sg+3qzEtiK7djQ23+Glcjs4TI24="/> </packages> </manifest>`