Welcome
Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
Installing and upgrading Notes® clients
Uninstalling Notes®
While it is not necessary to uninstall Notes® to upgrade to a new release, you should uninstall a Beta release before upgrading.
Cleaning a previous or partial Notes® installation from your client
Review these suggestions if you experience a problem installing or uninstalling Notes®.

Welcome
Welcome to the HCL Domino® 14.0 documentation.
What's new in Domino 14?
Learn about all of the new features for administrators in HCL Domino® 14.
Overview
Welcome to HCL Domino® Administrator Help.
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.
  - 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.
    - Uninstalling Notes® from a Windows™ client
      Use the following procedure to uninstall Notes® from the Microsoft™ Windows™ client.
    - Uninstalling Notes® from a Mac OS X client
      You can uninstall Notes® by dragging HCL Notes.app from /Applications to the trash. You can also uninstall Notes using the uninstaller application supplied with the Notes install media. Both methods preserve user data.
    - Uninstalling Notes® from a Citrix client
      Use the following procedure to uninstall Notes® from the Citrix client.
    - Uninstalling Notes® silently
      You can uninstall Notes® silently. The uninstall leaves each user's data directory and workspace intact to preserve data.
    - Cleaning a previous or partial Notes® installation from your client
      Review these suggestions if you experience a problem installing or uninstalling Notes®.
- 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.
Planning
Use this topic as an overview of planning task.
Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
Securing
This section describes security features, including execution control lists, IDs, and TLS.
Administering
This documentation provides information about the administration tools for HCL Domino.
Tuning
Use this information to improve HCL Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, advanced database properties, cluster statistics, and the Server Health Monitor.
Troubleshooting
This section describes how to find and solve problems with HCL Domino® server and Administrator client.
Notices

Cleaning a previous or partial Notes® installation from your client

Review these suggestions if you experience a problem installing or uninstalling Notes®.

About this task

Uninstall instructions are provided in this guide. If, after uninstalling a previous or partial release, you continue to experience install or uninstall problems, use the cleanup instructions that applies to your operating system.

Cleanup instructions for Windows™

About this task

To clean a Notes® or partial Notes® install from your Microsoft™ Windows™ client, complete the following procedure:

Procedure

Delete all folders in the Notes® install path\ except the \data folder.
Back up the Notes® install path\data folder and then delete all subdirectories in install path\data. Do not delete any root-level files from the Notes® install path\data folder.
If Notes® appears in your Add/Remove Program panel, run the Windows™ installer cleanup utility located at Microsoft™ Help and Support.
Retry the installation.

Cleanup instructions for Linux™ as root user

About this task

To clean a Notes® or partial Notes® install from your Linux™ client, complete the following procedure:

Procedure

Remove install path/install.log (and any other log files that remain in that directory).
Remove install path/framework.
Remove /root/InstallShield (unless you have installed other programs on your system with InstallShield).
Remove /root/ibm.
Remove /root/install.log if present.
Remove /root/install.xml if present.
Remove /etc/ibm/notes if present.
Retry the installation.

Cleanup instructions for Linux™ as non-root user

Procedure

Remove /home/user name/ibm.
Remove /home/user name/InternalProvisioning.log.
Remove the contents of /tmp owned by user name.
Retry the installation.