Installation
  • 28 Oct 2023
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Installation

  • Dark
    Light
  • PDF

Article summary

Server compatibility

The Universal Agent is only compatible with Liquit Workspace Servers that run version 4.0 or later.

The Universal Agent is available as separate packages per architecture. It is also available as an executable setup that contains all the supported MSI installations in one setup for easy distribution.

MSI installation properties

A few settings can be specified through the MSI installation properties. For example to install the Agent for a primary zone:

msiexec /i Liquit-Universal-Agent-x64.msi WORKSPACE_URL=https://workspace.liquit.com

The following MSI installation properties are supported (all property names should be in upper case):

NameDescription
WORKSPACE_URLThe URL of the primary zone. Leave empty for using the current configuration.
LAUNCHERModify the state of both Liquit Launcher and login in the Agent.json:
  • 0 Disable both launcher and user login.
  • 1 Enable only the Liquit Launcher.
  • 2 Disable Liquit Launcher but do allow user login.
DEPLOYMENTModify the state of the deployment mode in the Agent.json:
  • 0 Disable deployment mode.
  • 1 Enable deployment mode and start the process after installation finishes.
  • 2 Enable deployment mode but do not start the deployment process.
INSTALL_WEBVIEW2This option controls the installation behavior of the Microsoft WebView2 component which is required by the Universal Agent:
  • 0 Do not install the WebView2 component during installation.
  • 1 Install the WebView2 component during installation. (Default)

The Universal Agent needs an internet connection to install Webview2. When WebView2 isn't installed yet and there is no internet connection, an error message will be displayed during the installation of the Agent.
AUTOSTART_USERHOSTControl whether the UserHost process needs to be started after the installation is completed.
  • 0 Do not start UserHost.exe.
  • 1 Automatically start UserHost.exe for all sessions. (Default)
OVERRIDE_CONFIGSpecify the behaviour of overriding the Agent.json configuration file during installation. This option is ignored when an Agent.json file is located in the same directory as the installer.
  • 0 Use the existing Agent.json file from the device. If there is no Agent.json file but there is an Agent.xml file, it converts the XML into JSON. If no XML or JSON file exists, it uses the default Agent.json file embedded with the MSI. (Default)
  • 1 Use the default Agent.json file embedded with the MSI.
  • 2 If there is no Agent.json file but there is an Agent.xml file, it converts the XML into JSON. If no XML or JSON file exists, it uses the default Agent.json file embedded with the MSI.
  • 3 Use the existing Agent.json file from the device. If it doesn't exist, it uses the default Agent.json file embedded with the MSI.
    MIGRATE_DATABASESpecify the behaviour of the migration process of the package state information from the Workspace Agent database when no Universal Agent database exists:
    • 0 Do not migrate
    • 1 Migrate (Default)
      MIGRATE_CACHESpecify the behaviour of the migration process for the Workspace Agent content cache:
      • 0 Do not migrate Workspace Agent's content cache.
      • 1 Move the primary zone's Workspace Agent content cache to the Universal Agent cache.
      • 2 Move the primary zone's Workspace Agent content cache to the Universal Agent cache and remove the Workspace Agent content cache for other zones. (Default)
      • 3 Copy the primary zone's Workspace Agent content cache to the Universal Agent cache.
      • 4 Copy the primary zone's Workspace Agent content cache to the Universal Agent cache and remove the Workspace Agent content cache for other zones.
      • 5 Do not migrate Workspace Agent's content cache, but remove all of it if present.

        Was this article helpful?