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.
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.
Testing application upgrades
In general, application upgrades occur seamlessly without issue. To test Domino application upgrades, follow these best practices.

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.
    - 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.
  - 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.

Testing application upgrades

In general, application upgrades occur seamlessly without issue. To test Domino application upgrades, follow these best practices.

Review the list of removed features

Before fully testing your applications, review the list of features that have been removed from the Domino server platform in recent releases. See the Related information.

Review changes to the OpenJDK

For information about the OpenJDK included in the Domino 12 server, see New Java Runtime Environment.

Test an upgrade of a sampling of applications

Include in your upgrade testing:

Mission-critical applications that are based on different designs
Applications used by executives
Complex or custom applications that include:
- Back-end integration
- Reliance on third-party software
- Undocumented functions and features
- Extensions or add-in tasks using nsf_hooks, ext_mgr, and home-grown APIs
Sample of applications that use a common or standard template

Note: Use the Recompile All LotusScript tool in Designer to check for LotusScript issues.

Documents test results

Document the results of testing and convey them to the application developers.

Resolve issues

Resolve issues found based on your priorities and testing results:

Decide which application problems to fix before deploying to production.
Create a small team to address problems that arise after deploying to production.
Put applications into the pilot test environment for acceptance testing.
On successful testing, archive copies of new templates.