Home
Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
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.
Upgrading Notes® clients
You can push an upgrade to Notes® clients using Notes Smart Upgrade or other third party mechanism, 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.

Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
- Translated documentation
  The HCL Domino 11.0.1 documentation is currently available in the following languages.
- What's new in Domino® 11?
  Learn about all of the new features for administrators in HCL Domino® 11.
- Overview
  Welcome to HCL Domino® Administrator Help.
- Domino trial
  A trial version of HCL Domino® 11.0.1 is available free of charge.
- 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
  - 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.
    - Upgrading Domino® servers
      Upgrading a Domino® server refers to installing a new release of Domino software.
    - Upgrading Notes® clients
      You can push an upgrade to Notes® clients using Notes Smart Upgrade or other third party mechanism, 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.
      - Backing up and restoring Notes® client files
        Domino® administrators should periodically back up Notes® applications and files for users.
      - Upgrading from Notes® single user to Notes® multi-user
        While it is not possible to upgrade from a Notes® single user installation to a Notes multi-user installation during an upgrade install, you can use the supplied Notes® single user to multi-user migration assistant tool to migrate an existing single user installation to a multi-user installation within the same release and then run the 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.
        Using Smart Upgrade server failover
        HCL Notes® Smart Upgrade with server failover is available in a clustered server environment.
        Specifying an Allclient or Notes-only kit for Smart Upgrade
        Smart Upgrade contains the Smart Upgrade kit recognition feature. For Windows™, Smart Upgrade can determine whether to install a Notes® client-only kit or an Allclients kit for each user. The Allclient kit is only available for a single user install, not a multi-user install.
        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.
      - 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.
- Planning
  Use this topic as an overview of planning task.
- Configuring
  Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
- Securing
  This section describes security features, including execution control lists, IDs, and SSL.
- Administering
  This documentation provides information about the administration tools for managing and monitoring servers and databases.
- Tuning
  Use this information to improve HCL Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
- Troubleshooting
  This section describes how to find and solve problems with HCL Domino® server and Administrator client.
- Notices

Understanding the Smart Upgrade timer

This topic explains the behavior of the Smart Upgrade timer.

If the user's Smart Upgrade timer setting has expired, when the user logs in to Notes®, the following occurs:

Smart Upgrade compares the version value of the user's installed Notes® client to the version value specified in the Source version field of the Smart Upgrade kit document. The Notes® client sends a match pattern to the server including the Notes® client's current version, the platform and the localization. The Install type is also sent. The server then looks for a matching kit.
If the server finds a match, it sends a flag back to the Notes® client indicating an upgrade kit may exist.
Notes® searches the Smart Upgrade application for a match for its current version, platform, localization and install type.
Note: The Notes® client only recognizes kits for the user specified in the Allowed Users and Servers field of the Smart Upgrade kit document.
If the user's Deploy version field in the desktop policy settings document contains a version value, Notes® compares that version to the one specified in the Destination version field of the kit document.
Note: Specifying the upgrade kit version value in the Deploy version field of the desktop policy settings document is optional. If that field is blank, but an upgrade kit is available, Smart Upgrade skips this step and uses the version value of the upgrade kit to continue the upgrade process.
If a match is found, and users are specified or are members of a specified group, Smart Upgrade prompts the users to upgrade their Notes® client.
Users can upgrade when prompted or delay the upgrade for a specified time period. If the user has a policy that specifies an upgrade deadline and that date has expired, Smart Upgrade displays an Update Now button that forces the user to upgrade. If Remind me every hour after upgrade deadline has passed is set in the policy settings document, users can delay the upgrade in one hour increments before being prompted again.