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 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 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.
Creating the SURUNAS.EXE file locally
You can create the Smart Upgrade Run-As wizard (SURUNAS.EXE) executable file to reside locally.

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.
  - 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.
    - 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.
      - 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.
        Creating the SURUNAS.EXE file locally
        You can create the Smart Upgrade Run-As wizard (SURUNAS.EXE) executable file to reside locally.
        Creating the SURUNAS.EXE executable on a network share
        You can create the SURUNAS.EXE executable to be resident on a network share, rather than locally.
      - Using Upgrade-by-mail
        Upgrade-by-mail sends an e-mail notification to users instructing them to upgrade their Notes® client and optionally, their mail file template. You can also use Upgrade-by-mail to notify users that their mail files have been migrated to Notes® mail.
    - Maintaining Notes clients
      Upgrading Notes to the latest maintenance release and Fix Pack is a better choice than applying hotfixes

Creating the SURUNAS.EXE file locally

You can create the Smart Upgrade Run-As wizard (SURUNAS.EXE) executable file to reside locally.

Procedure

Run SUSETRUNASWIZARD.EXE.
Choose to save the new executable in a self-contained package in the SURunAs executable file and click Next.
Choose the files to be stored in the SURUNAS.EXE file. If the files you need are not listed, click Add Files, browse to and select the files and then click Next.
Specify desired command line options and click Next.

Note: Use the /w command line argument whenever you use Smart Upgrade Run-As.
Specify the path where SURUNAS.EXE is to be stored, and click Next.
Review summary information. Optionally save the settings by clicking Save all settings on exit and click Next.
Click Finish and Done.