4.2.2.1 VirtualUI: Pre-Launched Sessions

To reduce the connection time for applications using the VirtualUI protocol you can pre-launch Windows sessions before the user actually starts the application.

Why is this useful?

By enabling the Sessions Management > Start with service start option, all predefined sessions will begin initializing in the pool as soon as the server starts, remaining ready to launch the configured application.

When a user clicks on an access profile, Thinfinity® Workspace will immediately launch the application.

Pre-launched sessions improve the initial performance of VirtualUI applications by reducing user wait time, keeping sessions ready in the background.

This feature is especially useful in agent pool deployment scenarios, where all the target resources are functionally equivalent. To enhance user experience, you can pre-activate the sessions that will be used.

You can enable pre-launched sessions from the VirtualUI tab in the Thinfinity® Workspace Configuration Manager.

Configure VirtualUI Access Profile

Depending on your needs, you'll need to configure additional parameters, such as:

Session Management Options

• On Demand: This is the default mode. A session is created when the user clicks on the access profile.

• Start with Service Start: Sessions are created and disconnected automatically based on the user configuration as soon as the service starts.

Configuration Parameters

• Sessions: Specifies the number of pre-launched sessions at startup.

• Shared Users: By default, this is set to 1, meaning each session serves one user at a time. You can increase this number to allow multiple users to run applications within the same session. The service will maintain the specified number of sessions. When a user closes an application, the session is terminated and a new one is automatically created. The maximum number of applications the server can run in this mode is calculated as: #Sessions × #Shared Users.

Warning

If more than one shared user is allowed, there is no guarantee that all of a user’s applications will run in the same session.

• Agent Pool: Identifies the tag of the agent pool. Once the pool is configured, assign the applications that will run under that pool. For example, in the agent pool session settings, you must declare the pool name.

Warning

Any changes to pool definitions will terminate all related sessions and disconnect the users associated with them.

For more information, please refer to our Knowledge Base article.\