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.
Upgrading a Domino server
Before upgrading a Domino server, review the upgrade considerations and choose the upgrade option to use.
Considerations when upgrading a Domino server
Read about the things to consider before upgrading a Domino server.
Shutting down a server cleanly
Before upgrading a Domino server, it’s important to shut down the server cleanly, without errors or hangs.

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
- 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.
  - 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.
    - Considerations when upgrading a Domino server
      Read about the things to consider before upgrading a Domino server.
      - Install directories
        When upgrading Domino servers from a V10 or earlier release, the data directories from the previous version are retained. On fresh installations, new default directories introduced in V11 are used.
      - Hardware and/or operating system upgrades
        In some environments, you may need to update the operating system and/or the hardware to support the new Domino server version.
      - Upgrades and transactional Logging
        If you have transactional logging enabled on your current Domino server, you cannot change the location of where your Domino server is installed during the upgrade process. There are many files contained within the transactional logging system that list the existing Domino server location. If you change the Domino server location before or after the upgrade process, the Domino server will not restart.
      - Upgrades and DAOS
        If you plan on moving the location of Domino Attachment Object Service (DAOS) files for any reason, for example, because the current drive is running low in physical space, then complete these steps:
      - Upgrades and clusters
        If you have clustered Domino servers, you should upgrade all Domino servers in the cluster. This ensures that all Domino servers use the same version of Domino and the same set of Domino templates. You can upgrade one Domino server at a time in the cluster. Remember that ACLs and replication settings do not prevent designs from propagating in a cluster.
      - Shutting down a server cleanly
        Before upgrading a Domino server, it’s important to shut down the server cleanly, without errors or hangs.
      - Indirect files to save time running maintenance tasks
        During a Domino server upgrade, you’ll run Domino database maintenance tasks.
      - Installer feature for Windows to run as a non-admin account
        As part of our ongoing work to continuously improve security for Domino, we have updated the Windows installer to enable Domino to be installed to run as a non-admin user.
    - Options for upgrading a Domino server
      A Domino upgrade provides a good opportunity to consider other changes to your Domino infrastructure, for example, hardware or operating system upgrades.
    - Upgrading a customized Domino® Directory template
      When a new version of the Domino® Directory template (pubnames.ntf) becomes available, make sure to use it so that you can take advantage of new Domino features. Complete this procedure to preserve customization when you upgrade your customized Domino Directory template to a new version of the template.
  - 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.

Shutting down a server cleanly

Before upgrading a Domino server, it’s important to shut down the server cleanly, without errors or hangs.

About this task

If the server doesn’t shut down cleanly, complete the following steps. These steps invoke the Recovery Manager and flush the transaction logs to disk, simulating a clean server shutdown.

Procedure

Run nsd -kill.

With the Domino server shut down, run a Domino maintenance task against a non-existent database. For example, run c:\domino>nfixup.exe fred.nsf, which generates output like this:

c:\domino> nfixup.exe fred.nsf 
Restart Analysis (117 MB): 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
Recovery Manager: Recovery being performed for DB d:\notefile\mail.box
Recovery Manager: Recovery being performed for DB d:\notefile\names.nsf
Recovery Manager: Recovery being performed for DB d:\notefile\log.nsf
Restart Replay (116 MB): 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
04/22/2018 04:33:03 PM Recovery Manager: Restart Recovery complete. (3/2 databases needed full/partial recovery)
04/22/2018 04:33:07 PM Informational, rebuild view needed - collection object was deleted (reading d:\notefile\names.nsf view note Title:'($Servers)')
04/22/2018 04:33:08 PM Informational, rebuilding view - container integrity lost (reading d:\notefile\names.nsf view note Title:'($Servers)')
04/22/2018 04:33:08 PM Informational, rebuild view needed - collection object was deleted (reading d:\notefile\names.nsf view note Title:'($Servers)')
04/22/2018 04:33:10 PM Database Fixup: Started
04/22/2018 04:33:10 PM Database Fixup: The pathname 'd:\notefile\fred' was not found: File does not exist
04/22/2018 04:33:10 PM Database Fixup: Shutdown