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.
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.
Using Notes® Smart Upgrade
HCL Notes® Smart Upgrade is a administrative tool for pushing Notes client upgrades to users. Smart Upgrade notifies users to upgrade their Notes clients by a stated date and simplifies the upgrade process by essentially performing the upgrade the task with little or no user intervention.
Creating the Smart Upgrade application link and controlling concurrent downloads
In the Domino® Directory, the Configuration Settings document contains a Smart Upgrade Database Link field in which you paste the link to the Smart Upgrade application.

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.
  - 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.
    - 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.
      - Using Notes® Smart Upgrade
        HCL Notes® Smart Upgrade is a administrative tool for pushing Notes client upgrades to users. Smart Upgrade notifies users to upgrade their Notes clients by a stated date and simplifies the upgrade process by essentially performing the upgrade the task with little or no user intervention.
        Understanding the Smart Upgrade timer
        This topic explains the behavior of the Smart Upgrade timer.
        Creating a Smart Upgrade application
        Use the Smart Upgrade kits template (smupgrade.ntf) to create the Notes® Smart Upgrade application that will store the upgrade kits.
        Creating the Smart Upgrade application link and controlling concurrent downloads
        In the Domino® Directory, the Configuration Settings document contains a Smart Upgrade Database Link field in which you paste the link to the Smart Upgrade application.
        Adding upgrade kits to the Smart Upgrade application
        After downloading a Notes® install kit, make the kit available to users by creating a kit document in the Smart Upgrade application and then either attaching the kit to the kit document or storing the kit in a directory on a shared network drive that users can access.
        Creating and using a policy document for Notes® Smart Upgrade
        You can optionally use a desktop policy settings document to enable Notes® Smart Upgrade to function automatically, to deploy different releases of the Notes client to different groups of users, to upgrade Notes clients through several updates at one time, to automatically create and use a Smart Upgrade Tracking Reports application, and to control when updates occur in order to preserve server performance.
        Creating and using a Smart Upgrade Tracking Reports application
        The Smart Upgrade Tracking Reports application stores Smart Upgrade tracking reports that contain status information for all Smart Upgrade attempts in a domain.
        Maintaining Notes® Smart Upgrade
        After you have set up the HCL Notes® Smart Upgrade application and Smart Upgrade policy, perform the following tasks to maintain Smart Upgrade.
      - Using the Smart Upgrade Run-As wizard
        Use the Smart Upgrade Run-As wizard (SUSETRUNASWIZARD.EXE) to create an executable file (SURUNAS.EXE) that Notes® client users, running on Microsoft™ Windows™, can run to upgrade their Notes clients. SURUNAS is ideal for pushing Notes client upgrades to users who do not have administrator or elevated privileges.
    - Maintaining Notes clients
      Upgrading Notes to the latest maintenance release and Fix Pack is a better choice than applying hotfixes

Creating the Smart Upgrade application link and controlling concurrent downloads

In the Domino® Directory, the Configuration Settings document contains a Smart Upgrade Database Link field in which you paste the link to the Smart Upgrade application.

About this task

Domino® uses the replica ID of the Smart Upgrade application in the link and does the following in this order:

Looks for a local replica, and if found, uses it.
Looks for a replica on any cluster mates if the server is in a cluster, and if found, uses it.
Uses the application on the server specified in the link in the Server Configuration document.

During this procedure, you enable the Smart Upgrade Governor feature that allows you to limit the number of concurrent Smart Upgrade attempts.

Procedure

In the Domino® Administrator, open the Smart Upgrade application that you created.
Click Edit > Copy as link > Application link.
Click Configuration > Server > Configurations.
Select the server, and then click Edit Configuration.
Click the Smart Upgrade tab.
Note: Smart Upgrade first checks for the Smart Upgrade link in the Configuration Settings document of the home server specified in the Notes® client Location document. If that Configuration Settings document does not contain a Smart Upgrade link, Smart Upgrade next checks the * - [All Servers] Configuration Settings document for the link.
On the Smart Upgrade tab, paste the link in the Smart Upgrade Database link field.
In the Limit Concurrent Smart Upgrade field, enable the Smart Upgrade Governor.
Note: When Smart Upgrade Governor is enabled, you can limit the number of times that Smart Upgrade attempts are made by specifying a value in the Maximum Concurrent Downloads field.
In the Maximum Concurrent Downloads field enter a value for the maximum concurrent number of Smart Upgrade attempts that can be made while the Smart Upgrade Governor is enabled. The default is 100.
Save and close the Configuration Settings document.
Add upgrade kits to the Smart Upgrade application.