Creating a Version Path document to upload a new Notes install file to AUT servers

To prepare to deploy a new version of Notes on AUT servers, create a Version Path document to define and upload the install executable file for the new version into the AUT Catalog. You also define in the document which version or versions of Notes can be upgraded to the new version.

Before you begin

  • Download the web kit that contains the install file executable for the new version from the HCL download site and save it to a local file location. The new version can be any kind of update such as a full product release, a feature pack release, or a hot fix.
  • Have handy the AUT Notes install manifest .xml file for:
    • The version that you are upgrading to.
    • The version that you are upgrading from.
    The Notes install manifest.xml files are available for download in the following articles in the HCL Support site:
    • Notes 10.0.1 versions: article KB0069494
    • Notes 11.0.x versions: article KB0074862
    • Notes 12.0.x versions: articleKB0097848
    • Starting with Notes 14.0 Fixpack 1, the install manifest.xml files are no longer available on the HCL Support site. The files are now on the HCL Software Download & Licensing Portal (Filename:
      Note: Starting with Domino 14.0 Fixpack 1, there is an alternative way to have the Version Path document created by the Domino AutoUpdate database, without your needing to handle the manifest files directly. For more information, see Pushing Notes installs to the AUT Catalog using Domino AutoUpdate.


  1. Open the AUT Catalog on any AUT server.
  2. Select Version Paths.
  3. Click Import Manifest and select the Notes install manifest file for the version that you are upgrading to.
  4. Complete the following fields in the Version Path document:
    Note: The values of fields marked with an asterisk (*) in the following table are filled in for you from the information in the install manifest file for the version you are upgrading to. If for some reason you didn't import the install manifest, you complete these yourself.
    Product* HCL Notes
    Platform* Client type and platform associated with the install files, for example, StandardAllClient-win32.
    Language* Language version.
    Upgrade from version
    Specify the version string of the Notes version or versions to allow upgrades from. Enter this information manually.
    • To determine the version number of a release that you want to allow upgrades from, refer to the AUT Notes  install manifest .xml file for that release.

    • The minimum version you can upgrade from using AUT is version Notes 10.0.1.
    • Use a comma to separate version strings.
    For example, the version string for 10.0.1 FP1 is: V1001FP1_03262019.
    To version* The new version of Notes. It must be greater than 10.0.1.
    Note A description of the package to help you identify it.
    Display name This name is created when you save the document. It is derived by concatenating the values of the previous fields.
    Upload Use to select the install executable file for the new version that you saved previously to a local location.
    Actions Commands that are run on the Notes client to install the new version. Default commands are derived from the install executable file and are filled in for you. For example:
    install, run: {exe}
    postinstall, version: {toVersion}, onsuccess: exitsilentlyonlaunchcmd
    The following example shows a custom command that uses arguments to install silently with a progress bar:
    install, run: notes1001_designadmin_windows_prod.exe, args: [-s -a /s /v"/qb+"], success: exitsilentlyonlaunchcmd
    Comments Additional comments to note.
  5. Click Save & Close.
  6. To deploy the new install executable to the AUT servers, select Deploy Files from the action bar in either the Version Paths or Files view. All pending additions and updates to the currently deployed files are applied.


  1. The install executable is uploaded as an attachment to the Version Path document. In the Files view, the Uploaded column shows the date and time the upload occurred.
  2. The AUT Catalog change replicates to any other AUT servers.
  3. The install executable is downloaded from the AUT Catalog to the following location on each AUT server:
  4. In the Files view of the AUT Catalog, the Deployed column shows the date and time when the install executable is deployed on all AUT servers.