You can manually specify the application that you want to publish as a multi-session application pool. If an application that you want to specify manually is not already installed, Horizon Console displays a warning message. The published application can support multiple user sessions at the same time.



  1. In Horizon Console, select Inventory > Applications.
  2. Select Add > Add Manually.
    The pool configuration dialog box appears.
  3. Configure the required settings.
    Setting Description
    Application Pool Type

    Select RDS Farm and then select a Linux-based farm from the drop-down menu.

    Note: To create a multi-session application pool, you must base the pool on a farm of Linux host machines that are enabled for multi-session capabilities.
    ID Unique name that identifies the pool in Horizon Console. This field is required.
    Display Name Pool name that users see when they log in to Horizon Client. If you do not specify a display name, it will be the same as ID.
    Access Group This is a read-only field. You must specify the access group when you create the farm on which the application pool is based.
    Version Version of the application.
    Publisher Publisher of the application.
    Path Full pathname of the application. For example, /usr/bin/gnome-terminal. This field is required.
    Start Folder Full pathname of the starting directory for the application.
    Parameters Parameters to pass to the application when it starts. For example, you can specify -username user1 -loglevel 3.
    Description Description of this application pool.

    Select this option to configure an application so that an application session is launched before a user opens the application in Horizon Client. When a published application is launched, the application opens more quickly in Horizon Client.

    If you enable this option, the configured application session is launched before a user opens the application in Horizon Client, regardless of how the user connects to the server from Horizon Client.

    Note: Application sessions can be disconnected when the Pre-launch Session Timeout (Applications Only) option is set when you add or edit the Linux-based farm.
    Connection Server Restrictions

    You can restrict access to the application pool from certain Connection Servers by clicking Browse and selecting one or more Connection Servers. The default value is No Restrictions.

    If you intend to provide access to published applications through VMware Workspace ONE Access and you configure Connection Server restrictions, VMware Workspace ONE Access application might display applications to users when those applications are actually restricted. VMware Workspace ONE Access users will be unable to start these applications.

    Category Folder

    You can specify the name of the category folder that contains a Start menu shortcut for the application pool entitlement on Windows client devices. To configure this setting, click Browse. The default value is Disabled.

    Client Restrictions

    Select whether to restrict access to entitled application pools from certain client computers.

    You must add the names of the computers that are allowed to access the application pool in an Active Directory security group. You can select this security group when you add users or groups to the application pool entitlement.

    This setting is deactivated by default.

    Entitle Users After Adding Pool Select this option to open the Add Entitlements dialog box automatically after the pool is created.
    Multi-Session Mode

    Select Disabled.

    Note: Linux application pools do not support multi-session mode, which is not to be confused with the concept of a multi-session pool. If you specify a setting to enable multi-session mode, that setting has no effect.

    Linux applications can only be configured in single-session mode. For example, if a user opens an application on client A and then opens the same application or another application based on the same farm on client B, then the session on client A is disconnected and reconnected on client B.

  4. Click Submit to create the published application pool.

What to do next

Entitle users to access the pool. In Horizon Console, select the application pool, select Entitlements > Add entitlement, and add users or groups.

You can view the number of entitled users that are using a published application in the User Count column in the application pools page.

If you must ensure that Connection Server starts the application only on Linux host machines that have sufficient resources to run the application, configure an anti-affinity rule for the application pool. For more information, see Configure an Anti-Affinity Rule for a Linux Application Pool in Horizon Console.