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 a new version of Notes
Understand the things to consider and actions to take before installing a new version of HCL Notes.
Steps to deploy a new version of Notes
The following steps are typical ones to use to deploy a new version of Notes in your environment.
Roll out the deployment
After certifying the pilot deployment, deploy Notes to the rest of your environment.

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.
  - 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.
    - MarvelClient Essentials
      Domino includes MarvelClient Essentials by Panagenda.
    - Automate and standardize
      Before the upgrade, take the opportunity to automate and standardize.
    - Clean, tighten, and fix
      Before the upgrade, clean, tight and fix the current Notes client environment.
    - Notes client install best practices
      Follow these install best practices.
    - Steps to deploy a new version of Notes
      The following steps are typical ones to use to deploy a new version of Notes in your environment.
      - Plan the deployment
        It is important to plan for the deployment of the new version of Notes.
      - Backing up and restoring Notes® client files
        Domino® administrators should periodically back up Notes® applications and files for users.
      - Download and customize the install kit
        There are many ways to customize the Notes installation.
      - Build and test the deployment package
        Follow these guidelines to build and test the deployment package.
      - Pilot the upgraded client
        Test the upgraded Notes version with a pilot deployment.
      - Roll out the deployment
        After certifying the pilot deployment, deploy Notes to the rest of your environment.
        (Optional) Upgrade mail files with the mail conversion utility
        When you upgrade users' mail files to the current Notes® mail template or to the iNotes® template, you can upgrade one file at a time or use the mail conversion utility to automate design upgrade. You can also use the mail template conversion utility to convert a mail design from one language to another language. Run the mail conversion utility on an applicable Domino® server.
      - Manage the desktop
        Consider post-installation requirements.
    - Using Notes® Smart Upgrade and other upgrade tools
      You can push an upgrade to Notes® clients using Notes Smart Upgrade and/or other third party mechanisms, such as Smart Upgrade Run-As wizard (SURUNAS) or Upgrade-by-mail. You can also upgrade Notes clients using the Notes installation executable either silently (command line) or using the installer's graphical user interface. The supplied installation executable is used for an initial install or an upgrade install.
    - Maintaining Notes clients
      Upgrading Notes to the latest maintenance release and Fix Pack is a better choice than applying hotfixes

Roll out the deployment

After certifying the pilot deployment, deploy Notes to the rest of your environment.

Plan the roll-out based on bandwidth.
- Consider how many desktops must be upgraded and plan your roll- out based on network bandwidth as well as your IT support capabilities.
- In case of low WAN bandwidth, consider alternatives such as LAN storage devices or Smart Upgrade Governor
Provide the support plan to help desk staff.
- Use the feedback and lessons learned during the pilot to determine how much deskside support may be needed.
Monitor the deployment.
- Throughout the deployment, monitor the progress by using the tracking features of the tool in use.
- Considering using MarvelClient Essentials to help monitor the deployment.

Push out initial policy settings.
- Configure hierarchical policy settings document to control the desktop configuration. The settings are detected automatically at first client launch.
Update mail templates
- After the server and client have been upgraded, then upgrade mail templates.
Update folder designs
- The mail file folder design is not automatically updated with a template change. You must use a Desktop policy to update the folder design.
- Prior to updating the folder design, have users empty their Trash folders.