Home
Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
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.
Preparing your environment for the upgrade
Time spent doing a thorough evaluation of your environment prior to upgrading is time well spent. Capturing baselines of your existing server infrastructure allows you to compare how the upgraded environment is performing.
Creating a debug file for pre-V9.0.1 upgrades
For V9.0.1 and later Domino versions, information from the Domino server console is saved in a console.log file located on the Domino server in the Data\IBM_TECHNICAL_SUPPORT directory. You can refer to this file to view information generated at the console before, during, or after the upgrade.

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
- 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.
  - Security considerations prior to upgrading
    It’s important to review your security practices before upgrading, especially if you are upgrading from an old version.
  - Preparing your environment for the upgrade
    Time spent doing a thorough evaluation of your environment prior to upgrading is time well spent. Capturing baselines of your existing server infrastructure allows you to compare how the upgraded environment is performing.
    - Running Fixup
      Before you upgrade Domino servers, run the Fixup task to detect and address any corruption within your Domino applications. Running Fixup is particularly important if you are upgrading from a pre-V9.0.1 version of Domino.
    - Verifying that system databases have inheritance enabled
      Verify that database design inheritance is enabled on standard databases so that the design task can refresh database designs from the standard templates after the upgrade while the Domino server is down. If database inheritance is not enabled, you must replace the database design manually using the Domino Administrator. Note: If you are upgrading a previously customized Domino Directory template to a new version of that template, also see the following topic.
    - Creating a debug file for pre-V9.0.1 upgrades
      For V9.0.1 and later Domino versions, information from the Domino server console is saved in a console.log file located on the Domino server in the Data\IBM_TECHNICAL_SUPPORT directory. You can refer to this file to view information generated at the console before, during, or after the upgrade.
    - Evaluating your current environment
      Investigate thoroughly the state of your current environment.
    - Monitoring your current environment
      Monitoring your current environment is a critical part of any upgrade, even an upgrade to a point release.
    - Evaluating operating system and hardware requirements for the new version
      Evaluate system requirements.
    - Considerations if moving from a 32-bit operating system to a 64-bit operating system
      As of Domino V10, a Domino 32-bit server is no longer provided.
    - Evaluating coexistence of features across versions
      Understand what you need to consider if operating Domino V12 and Notes V12 in an environment that includes earlier versions.
    - Creating an inventory of applications
      Creating an inventory of your applications allows you to get an understanding of your application landscape as input for requirements and architectural discussions. It also gives you an opportunity to clean up your application environment.
    - Planning HCL Traveler upgrades
      If upgrading a Domino server that runs HCL Traveler, keep the following points in mind:
  - Planning the deployment of the new release
    Depending on the size of your organization and the number of Domino servers involved, an organization upgrade schedule may range from a few hours to a few weeks or months.
  - Upgrading a Domino server
    Before upgrading a Domino server, review the upgrade considerations and choose the upgrade option to use.
  - Upgrading post-V11 AD Password Sync to V12.0.2 or later
    Upgrade Domino AD Password Sync installations that use Domino 12.0 or 12.0.1 to Domino 12.0.2 or later in order to use the new "AD Password Sync" server install type available in 12.0.2 and later.
  - Planning the deployment of a new version of Notes
    Understand the things to consider and actions to take before installing a new version of HCL Notes.

Creating a debug file for pre-V9.0.1 upgrades

For V9.0.1 and later Domino versions, information from the Domino server console is saved in a console.log file located on the Domino server in the Data\IBM_TECHNICAL_SUPPORT directory. You can refer to this file to view information generated at the console before, during, or after the upgrade.

About this task

If you are upgrading a pre-V9.0.1 version of Domino, the console.log file is not created. Instead, you can configure Domino to create a debug file by adding the following notes.ini setting: DEBUG_OUTFILE=filename.txtwhere filename.txt is a name you choose. If you don’t specify a directory location, the file is created in the Data\IBM_TECHNICAL_SUPPORT directory on the server. To put it in another location include the path, for example, DEBUG_OUTFILE=c:\temp\filename.txt.