When you create an application pool and manually specify an application, you can add information about the application. It is not a requirement that the application is already installed on any RDS host.
Worksheet: Application Properties for Creating an Application Pool
| Property | Description | Fill in Your Value Here |
|---|---|---|
| Select an RDS Farm or Desktop Pool | Select a farm or a desktop pool from the list provided. For desktop pools, only desktop pools with supported session type Application or Application and Desktop are available. | |
| 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. | |
| Version | Version of the application. | |
| Publisher | Publisher of the application. | |
| Path | Full pathname of the application. For example, C:\Program Files\app1.exe. 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. | |
| Pre-launch | 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. If you enable this option on applications published from a desktop with session type Application and Desktop, the desktop session may not be available. Note: Application sessions can be disconnected when the Pre-launch session timeout (applications only) option is set when you add or edit the application farm. | |
| Enable single application launch limit | You can limit the number of application instances a user can launch from an application pool to just one instance. An attempt to re-launch the application will bring the first instance to focus. If you activate this setting, multi-session mode is not available. | |
| Connection Server Restrictions | You can restrict access to the application pool to certain Connection Servers by clicking Browse and selecting one or more Connection Servers. If you intend to provide access to applications through Omnissa Access, and you configure Connection Server restrictions, the Workspace ONE catalog might display applications to users when those applications are actually restricted. Users going through the Workspace ONE catalog will be unable to launch these applications. | |
| Category Folder | Specifies the name of the category folder that contains a Start menu shortcut for the application pool entitlement on Windows client devices. | |
| 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. | |
| Allow Machine Name Selection | Enabling this option will allow a command line launch of Horizon Client to specify a machine name to connect to, for example for test or troubleshooting purposes. | |
| Multi-Session Mode |
You can start published application sessions in the following modes:
Single-session: If the user opens a published application on client A in single-session mode, and then opens the same published application or another published application based on the same farm on client B then, the session on client A is disconnected and reconnected on client B.
Multi-session: If the user opens a published application on client A in multi-session mode, and then opens the same published application or another published application based on the same farm on client B, the published application remains open on client A and a new session of the published application opens on client B. Such sessions are logged off on disconnect. You cannot enable the session pre-launch feature when multi-session mode is enabled.
Note: Multi-session mode is not available if you select Enable application launch limit.
The multi-session mode has the following values:
Note: Horizon Web Client is available with Horizon 8 versions 2412 and later. For Horizon 8 versions 2406 and earlier, Horizon Web Client is called "HTML Access." This page uses the name "Horizon Web Client" to refer to both Horizon Web Client and HTML Access. For more information about using the Multi-Launch setting, see the Horizon Client documentation. Note: This setting is not supported for applications based on a desktop pool. | |
| Isolated Session Mode | You can configure an application pool so that every launch of the application starts in a new, separate RDSH session rather than joining an existing session for that user. This applies whether it's an additional launch of the same application, or a launch of a different application from the same farm. Each application launch starts in a new, independent session rather than reusing one, allowing users to run multiple concurrent instances of the same application in fully isolated sessions, which supports workflows where per-instance session isolation is required. The new session can be created on the same RDS host or a different RDS host within the farm.
This setting is disabled by default and must be explicitly enabled when you create or edit the application pool. It can also be enabled at the Global Application Entitlement level. Before enabling this setting, ensure the farm has sufficient capacity for the expected number of concurrent application sessions per user, since each launch consumes a separate session rather than sharing one. When enabled, the administrator should set a Max Isolated Sessions value which sets an upper limit on the number of instances of the app each user can launch. The default is 10. Client support for this feature:
Note: Isolated Application Launch cannot be enabled together with Enable single application launch limit. |
Was this page helpful?