Home
Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
Installing and upgrading Notes® clients
Managing client plug-in deployment
While you can customize your client installer to add new or remove supplied features and plug-ins when you install or upgrade your clients, you can also provision (install and automatically update) stand-alone or third party features and plug-ins to your existing Notes® or Lotus® Expeditor run-time using a combination of Domino® policy or Eclipse preferences, a widget resident in a widgets catalog on an HTTP or Domino server, and a Eclipse update site (with signed features and plugin .jar files) optionally resident in a centrally managed NSF-based update site.
Limiting feature install and update with update sites
Provisioning settings are available on the Client Upgrade tab in the Domino® Administrator server Configuration Settings document. This capability is specific to the Eclipse Update Manager (EUM).
Specifying available update sites
Domino® server-based update of features and plug-ins enables you to control which update sites user can obtain features from. Using fields on the server Configuration Settings document in the Domino Administrator client, you can control where (and if) users can obtain features for install and update. If the administrator allows, users can initiate feature install and update. The update process searches an update site or site list for feature updates, as well as updates to composite applications. Update sites can be Eclipse update sites or NSF-based update sites.
Specify different site controls for feature install and update
You can specify that feature update can only be performed from a site list but that feature install be allowed from other sites as specified in the Update Manager user interface or CA XML.

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
  - Notes® Auto Update
    You don't have to rely on third-party products to automate deployment of new versions and updates of HCL Notes® or HCL Client Application Access (HCAA). Instead, you can enable Auto Update (AUT) servers to deploy updates automatically.
  - Customizing Notes® installation
    As an administrator, you can customize the Notes® install and upgrade process for your users to install just the features that they need. For example, you can customize the install kit using MSI tuner capabilities and you can also customize the install kit to add or remove Eclipse-based features.
  - Specifying custom data directories for multi-user install or upgrade
    You can configure Notes® custom data directories during Notes multi-user install or upgrade on Windows™ or Citrix XenApp.
  - Understanding the Notes® single user to multi-user migration assistant tool
    The single-user to multi-user migration tool converts a Notes® single-user installation to a multi-user installation.
  - Using the Notes® Install Cleanup Utility (NICE) tool
    You can use the supplied Notes® Install Cleanup Executable (NICE) tool to clean up a failed install, failed uninstall, or failed upgrade. You can also use the tool to uninstall an existing version of Notes, and clean up extraneous files, before performing an upgrade installation. The tool is available for Notes on supported Windows™ platforms only, and must be run by an administrator.
  - Automating a customized or default Notes® deployment using silent install
    You can use a silent install to deploy a default or customized Notes® release to users without user intervention. This enables centralized Notes install or upgrade deployment to many users without requiring user intervention.
  - Installing and upgrading Notes® in a single user environment
    You can install Notes® on Microsoft™ Windows™ or Citrix platforms in a single user environment using either the Notes-only or the Notes Allclient installer.
  - Installing and upgrading Notes® multi-user
    Installing Notes® in a multi-user user environment enables multiple users to sequentially log in to the same machine and use the same Notes install directory with their own Notes data directory.
  - Installing a non-English version of Notes®
    Notes® is available for install and upgrade in multiple languages.
  - Adding or removing installed Notes® features within a release
    Optionally add new features, or remove installed features, by rerunning the Notes® installation executable within the same release.
  - Managing client plug-in deployment
    While you can customize your client installer to add new or remove supplied features and plug-ins when you install or upgrade your clients, you can also provision (install and automatically update) stand-alone or third party features and plug-ins to your existing Notes® or Lotus® Expeditor run-time using a combination of Domino® policy or Eclipse preferences, a widget resident in a widgets catalog on an HTTP or Domino server, and a Eclipse update site (with signed features and plugin .jar files) optionally resident in a centrally managed NSF-based update site.
    - Client feature deployment
      There are several ways to deploy Notes® client features and plug-ins to users, including a customized add-on installer, a deployment widget and source widget catalog, and a customized Notes install kit. For all methods, the feature or plug-in to be deployed should be properly signed before deployment.
    - Installing a new feature using the Notes® install kit
    - Deploying client plug-ins with widgets and the widget catalog
      You can use a widget to deploy a new feature and corresponding plug-in to an existing Notes® client using a combination of the widgets catalog, an NSF-based update site in which the feature resides, an XML file attached to the widget that calls the feature's update site, and Domino® policy or Eclipse preferences.
    - Creating a customized add-on installer
      The HCL Expeditor framework enables you to create and use an add-on installer as an alternative method for deploying a third-party feature or plug-in to an existing Notes® installation. For example, rather than deploy a custom feature to users as part of the Notes install kit, or use a widget to deploy a custom feature to an existing Notes runtime, you can create and use an add-on installer.
    - Creating a new feature
      You can learn to create custom or third-party features for use with Notes® using these and other resources.
    - Signing custom or third-party features and plug-ins for install and update
      Eclipse plug-ins can be created and used to extend Notes® client functionality. Features and plug-ins are provisioned with the client software.
    - Creating and using an NSF-based update site
      You can use the Eclipse Update Site template to create an NSF-based update site application and then import some or all of the features from an Eclipse update site into the NSF-based update site.
    - Limiting feature install and update with update sites
      Provisioning settings are available on the Client Upgrade tab in the Domino® Administrator server Configuration Settings document. This capability is specific to the Eclipse Update Manager (EUM).
      - Specifying available update sites
        Domino® server-based update of features and plug-ins enables you to control which update sites user can obtain features from. Using fields on the server Configuration Settings document in the Domino Administrator client, you can control where (and if) users can obtain features for install and update. If the administrator allows, users can initiate feature install and update. The update process searches an update site or site list for feature updates, as well as updates to composite applications. Update sites can be Eclipse update sites or NSF-based update sites.
        Add an update site to the update site list
        You can add an additional update site to the NSF-based update site list in the server Configuration Settings document.
        Edit an existing update site in the update site list
        You can change the server name or URL of a site in the update site list using the server Configuration Settings document.
        Delete an existing update site from the update site list
        You can delete a site from an update site list using the Domino® server Configuration Settings document.
        Specify that feature update be performed from the feature's update site
        You can specify that feature update only be allowed from the update site specified for that feature.
        Specify that feature install can occur from a default update site, CA XML or update manager
        You can specify that feature install occur from a default update site, CA XML, or a site specified using the Eclipse Update Manager (EUM).
        Specify that feature update can occur from a default update site or feature.xml
        You can specify that feature update occur from a default update site, feature.xml, or a site specified using the Eclipse Update Manager (EUM).
        Specify that feature install or update can occur from the whitelist only
        You can specify that feature install or update using the Eclipse Update Manager (EUM) be available only from the whitelist. This method enables you to control where install and update can occur from using a list of approved update sites.
        Specify different site controls for feature install and update
        You can specify that feature update can only be performed from a site list but that feature install be allowed from other sites as specified in the Update Manager user interface or CA XML.
    - Creating and using a traditional third-party installer
      Using the Lotus® Expeditor platform, you can create a third party installer to add new features after Notes® has been installed.
    - Configuring component update for composite applications
      You can use composite applications to install or update custom or third-party features in Notes®.
    - Enabling user-initiated update with EUM
      To allow users to install or update custom or third-party Eclipse features and plug-ins into an existing Notes® installation, you can enable display of the Eclipse update manager user interface. By default, the Eclipse update manager (EUM) is not displayed. You can enable the EUM using either Domino® Desktop policy or a plugin_customization.ini file setting.
  - Uninstalling Notes®
    While it is not necessary to uninstall Notes® to upgrade to a new release, you should uninstall a Beta release before upgrading.
- 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.

Specify different site controls for feature install and update

You can specify that feature update can only be performed from a site list but that feature install be allowed from other sites as specified in the Update Manager user interface or CA XML.

About this task

This method is applicable when you want to allow feature install from various sites but only permit feature update from an approved site. For example, third-party features maintain their original update site location in their feature.xml. You may choose to move that feature to an authorized update site and install from that site. However, if the Use update site specified in Feature option is enabled, the update could retrieve from that external update site, which is not desirable. This method enables you to prevent update from occurring from that site.

Procedure

From the Domino® Administrator, click Server > Configurations.
Select the Server Configuration document you want, and click Edit Configuration.
Click Client Upgrade > Provisioning.
Disable Use update site specified in Feature.
Disable Allow client updates only from these sites.
Enable the default update sites that are currently specified in the server Configuration Settings document.