General Installation Options - Integration for Microsoft Outlook 2019 - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Integration for Microsoft Outlook 2019
Platform
OnBase
Product
Integration for Microsoft Outlook 2019
Release
Foundation 22.1
License
Standard
Essential
Premier

To run the Hyland Office Products Deployment Installer:

  1. Execute setup.exe with administrator privileges. This can be done by right-clicking on the file name and selecting Run as administrator. This executable is usually located in the \ClickOnce\Office Products folder of your source installation files.
  2. The Ready to Install dialog box is displayed. Click Install.
  3. Click Launch or Finish, depending on the module being installed. The Welcome to the Deployment Creation Wizard dialog is displayed.

    Select Advanced Mode to enable the ability to update certain aspects of the installation where the default values are populated by the installer. Not selecting this option automatically uses the default values populated by the installer.

    CAUTION:

    Any necessary changes to the files in the deployment folder or the contents of the deployment folder, such as custom changes to the *.config file for the module, must be made before clicking Next at the Deployment Signing dialog box. If you are in Advanced Mode, you still have the option to edit files in the deployment folder at the File Edit Notification dialog box that is displayed after the Deployment Signing dialog box.

    Note:

    If your servers are configured to use an HTTPS binding, or you are going to enable Active Directory or LDAP Authentication, you should enable Advanced Mode in order to be able to configure these options in your deployment.

  4. Click Next. The Instance Settings dialog box is displayed.
    Note:

    If the Package Selection dialog box is displayed, select the package to deploy then click Next to reach the Instance Settings dialog box.

  5. Select the name of the application instance from the drop-down list under the Instance Name section , or select it from the drop-down select list if you are updating an existing instance. To create a new instance name:
    1. Click the Add button to the right of the drop-down list. The Create New Instance dialog box is displayed.
      Note:

      If you create a new instance name for an existing deployment, the package must be redeployed to client machines under the new instance name.

    2. Enter a name for the new instance in the field provided. The name entered is used to distinguish this deployment from other deployments, so it must be unique.
      Note:

      The instance name cannot contain any of the following characters: [ ] < > , ; : + = " / \ | ? * # '

    3. Click OK.
  6. The Deployment Version Number fields can be used to manually set a new version number for this deployment. This number is used by client machines to determine if the application installed needs to be updated.

    The Deployment Version Number is incremented automatically by the deployment wizard. The initial Deployment Version Number is 1.0.0.0, and there is no need to change this number.

    Note:

    The Deployment Version Number is not available unless Advanced Mode is selected on the Welcome to the Deployment Creation Wizard dialog. To enable the Deployment Version Number, click Back and select Advanced Mode on the Welcome to the Deployment Creation Wizard dialog.

  7. Select the Require clients to upgrade to version check box to force client machines to upgrade to the current instance. This option is selected by default.
  8. Click Next. The Deployment Location dialog box is displayed.
  9. Click Change beside the Deployment Folder field to select a different folder. The Deployment Folder can be a local path or network location and is the folder to which the application files are copied on the deployment server.
    Note:

    If you are updating an existing deployment, you cannot change the Deployment Folder. If you create a new instance with a different Deployment Folder, the old deployment is not updated and the package must be redeployed to client machines with the new Deployment Folder location.

    CAUTION:

    Files in the Deployment Folder selected are overwritten.

  10. Click Next. The How do you want to deploy...? dialog is displayed.
  11. Click the Web Server icon to deploy the application to client workstations via a URL (e.g., https://web-server/Application/DeployedApp.application).
    Note:

    If IIS is not installed, you cannot select Web Server and must deploy the application via a UNC path.

    Click the From a Shared Folder icon to deploy the application to client workstations via a UNC path (e.g., \\machine-name\Application\DeployedApp.application).

    Note:

    The From a Shared Folder option is not available if deploying to a network location (e.g., \\MyServer\MyShare).

    Select Skip this step to configure the deployment folder manually as a shared folder or a virtual directory.

  12. Click Next.