Home
Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
Planning your upgrade to Notes and Domino 12.0.2
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 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.
Deployment sequence for enterprise businesses
An enterprise business is generally defined as one having more than 10,000 users and more than 50 servers. It can take many weeks or even months to upgrade all servers in an enterprise environment.
Mitigating the time required to rebuild Domino directory views
Two critical views, ($USERS) and ($SERVERACCESS), are used when a Notes client or a Domino server attempts to authenticate with a Domino server. When you upgrade the design of the Domino directory from the latest pubnames.ntf template, these views are rebuilt from scratch when first opened 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.
- Installing and upgrading Notes® clients
- Planning your upgrade to Notes and Domino 12.0.2
  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.
    - Deployment best practices
      Here are deployment best practices, many of which are particularly important in enterprise environments that have many thousands of users.
    - Creating a Domino server test Environment
      If you do not have a test environment, it is highly recommended that you create one.
    - Testing application upgrades
      In general, application upgrades occur seamlessly without issue. To test Domino application upgrades, follow these best practices.
    - Piloting the upgrade in the production environment with a small set of users
      Pilot the upgrade in the production environment, considering the following as you do:
    - Deployment sequence for small and medium businesses
      Small and medium businesses (SMBs) are generally defined as ones having 10,000 users or less and 50 Domino servers or less.
    - Deployment sequence for enterprise businesses
      An enterprise business is generally defined as one having more than 10,000 users and more than 50 servers. It can take many weeks or even months to upgrade all servers in an enterprise environment.
      - Mitigating the time required to rebuild Domino directory views
        Two critical views, ($USERS) and ($SERVERACCESS), are used when a Notes client or a Domino server attempts to authenticate with a Domino server. When you upgrade the design of the Domino directory from the latest pubnames.ntf template, these views are rebuilt from scratch when first opened after the upgrade.
      - Controlling the replication of the updated Domino directory
        It’s a best practice to replicate the upgraded Domino directory from the Domino administration server for the domain out to other servers.
  - 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 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.

Mitigating the time required to rebuild Domino directory views

Two critical views, ($USERS) and ($SERVERACCESS), are used when a Notes client or a Domino server attempts to authenticate with a Domino server. When you upgrade the design of the Domino directory from the latest pubnames.ntf template, these views are rebuilt from scratch when first opened after the upgrade.

Rebuilding these views can take a long time in enterprise environments due to the many more users in the Domino directory, especially if the Domino server is running so that the view rebuilds are competing for cycles. Users attempting to access a Domino server that is running when these views are being rebuilt can experience significant delays or hangs and Domino cluster failover will be unavailable.

Use any of the following strategies to avoid this problem:

Rebuild the views while the server is down, allowing users to fail over to another server.
Rebuild the views on the first server you upgrade. Upgrade each subsequent server, but before starting it, copy the rebuilt Domino directory from the first server to it.
Rebuild and replicate the directory off-hours, to minimize user impact.
Control the replication of the updated Domino directory from the Domino administration server to other servers.