When an administrator has activated multi-session mode for a published application, you can use multiple sessions of the same published application when you log in to the server from different client devices.
For example, if you open a published application in multi-session mode on client A, and then open 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, when multi-session mode is deactivated (single-session mode), the published application session on client A disconnects and reconnects on client B.
The multi-session mode feature has the following limitations.
- Multi-session mode does not work for applications that do not support multiple instances, such as Skype for Business.
- If the application session is disconnected while you are using a published application in multi-session mode, you are logged off automatically and any unsaved data is lost.
- If the Mac client system goes to sleep while you are connected to a published application in multi-session mode, the published application session is not resumed.
- You cannot use the same published application in both single-session mode and multi-session mode. For example, if you are using a published application in single-session mode, you must quit the application before you can change it to multi-session mode.
Prerequisites
An administrator must activate multi-session mode for the application pool. End users cannot modify the multi-session mode for a published application unless an administrator allows it. See Windows Desktops and Applications in Horizon.
