Contents x
    Installation
    • 22 Nov 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Installation

    • Updated on 22 Nov 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Liquit Workspace Agent 3.x moves to extended support​

    Liquit Workspace 4.2 is the latest version where the Liquit Workspace Agent (XML-based) is supported.​
    The bootstrapper is still able to download the (XML-based) Liquit Workspace Agent in Liquit Workspace 4.2 but this is the last version.

    (Liquit Workspace Agent is available as an executable setup that contains all the supported MSI installations in one setup for easy distribution. You can find it on our Downloads page.

    MSI installation properties

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

    msiexec /i Liquit-Workspace-Agent.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.xml:
  • 0 Disable both Liquit Launcher and user login.
  • 1 Enable only the Liquit Launcher.
  • 2 Disable Liquit Launcher but do allow user login.
    • Leave empty for using the current configuration.
    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.
    OVERRIDE_CONFIGSpecify the behaviour of overriding the Agent.xml configuration file during installation. This option is ignored when an Agent.xml file is located in the same directory as the installer.
  • 0 Do not override
  • 1 Override
    • The default value is 0. This option is ignored when an Agent.xml file is located in the same directory as the installer.
    Was this article helpful?
    What's Next