Session sharing is a mode in which more than one published application runs within a single ICA/HDX connection. Session sharing occurs when a user has an open session and launches another application that is published on the same XenApp server; the result is that the two applications run in the same session. Session sharing is configured by default when you specify that applications appear in seamless window mode.

Inconsistent results may occur when applications are configured for different requirements, such as encryption and color depth. As session sharing helps to lower overall resource utilization, try to publish applications with consistent settings where possible.

Seamless window

With seamless windows, the Windows application server manages the display of the application. This means an application’s windows behave in the same way as an application running on a Windows application server, regardless of the user’s desktop environment. The window can be resized, stacked, maximized and minimized. The Windows Start menu and Task bar do not display.

Note seamless windows are not suitable for displaying Windows desktop sessions: use a kiosk or independent window instead.

To use seamless windows:

• The application server must be a Windows 2000/2003 application server.
• The Sun Secure Global Desktop Enhancement Module for Windows must be installed on the application server.
• The Windows application object must be configured to:
  • use Microsoft RDP as the Windows protocol; and
  • Display Using (–displayusing) a seamless window.
• The user must use a client that supports seamless windows.

If any of the above conditions are not met, the Windows application displays in an independent window instead.

You can only use seamless windows with the browser-based webtop, see the supported client platforms.

Notes

• If an application is launched in a seamless window, you can toggle between a seamless and independent window by pressing the SCROLL LOCK key.
• Applications that have non-rectangular windows, for example a media player with a customized skin, display in a rectangular window.
• On Windows client devices, seamless windows are not affected by the Cascade, Tile Windows Horizontally, or Tile Windows Vertically window commands.
• If a screen saver or the Windows Security dialog displays, the window automatically switches to an independent window. Unlocking the application automatically restores the window to a seamless window.
• If a seamless window application is resumed on a display that is a different size (larger or smaller) to the original session, the application is displayed in an independent window.
• Each application displaying in a seamless window has its own RDP connection.

Depending on the Receiver or plug-in, when a user opens an application, it can either appear in a seamless or non-seamless window. These window modes are available for Citrix Receiver for Windows, Web Interface, and other plug-ins.

• In seamless window mode, published applications and desktops are not contained within an ICA session window. Each published application and desktop appears in its own resizable window, as if it is physically installed on the client device. Users can switch between published applications and the local desktop.
• In non-seamless window mode, published applications and desktops are contained within an ICA session window. This creates the effect of the application appearing in two windows.

The mode that you choose typically depends on the type of client device that your users will be using and whether you are publishing a desktop or individual applications. Desktops are typically published in non-seamless window mode. This table provides examples of when you might want to publish desktops and applications.

When a user launches a published application, Receiver or the plug-in establishes a connection to a XenApp server and initiates a session. If session sharing is not configured, a new session is opened on the server each time a user opens an application. Likewise, every time a user opens a new application, a new client connection is created between the client device and the server.

Session sharing is a mode in which more than one published application runs on a single connection. Session sharing occurs when a user has an open session and launches another application that is published on the same server; the result is that the two applications run in the same session. For session sharing to occur, both applications must be hosted on the same server. Session sharing is configured by default when you specify that applications appear in seamless window mode. If a user runs multiple applications with session sharing, the session counts as one connection.

If you want to share sessions, ensure all applications are published with the same settings. Inconsistent results may occur when applications are configured for different requirements, such as encryption.

Note: Session sharing is not supported on PocketPC clients. Session sharing takes precedence over load balancing, except when a server is fully loaded.