When you create a global application entitlement, you can specify whether users can start multiple sessions of the same published application on different client devices. This feature is called multi-session mode.
For example, if a user opens a published application in multi-session mode on client A, and then opens the same published application on client B, the published application remains open on client A and a new session of the published application opens on client B. By comparison, if the user opens the published application on client A in single-session mode, the session on client A is disconnected and reconnected on client B.
When you enable multi-session mode, you can specify whether it is on by default, off by default, or enforced.
- When multi-session mode is on or off by default, users that have Horizon Client can disable or enable multi-session mode by modifying the Multi-Launch setting on the client. Users that have earlier versions of Horizon Client cannot change the default setting.
- When multi-session mode is enforced, it is always on and users cannot disable it in Horizon Client.
For more information about using the Multi-Launch setting, see the Horizon Client documentation.
The multi-session mode feature has the following requirements and limitations for global application entitlements.
- The multi-session mode setting that you configure for the global application entitlement must match the setting that is configured for the application pools associated with the global application entitlement. For information about enabling multi-session mode for application pools, see the Windows Desktops and Applications in Horizon document.
- You cannot enable the session pre-launch feature for the global application entitlement, or the application pools associated with the global application entitlement, when multi-session mode is enabled. The session pre-launch feature is not supported when multi-session mode is enabled.
