Session Pre-Launch

2 users found this article helpful

When a user opens a remote application or desktop, a session must first be launched. Launching a session can take time, which will result in the user waiting for the application to start.

To improve user experience, a session can be launched ahead of time, before the user actually opens an application.

When a session is pre-launched, it will all happen in the background, so the user will not see any windows or message boxes on the screen. When the user starts an application, it will open using the pre-launched session, so it will start very quickly.

For information about how to configure session prelaunch, see Client policies.

Advantages of Session prelaunch:


When you configure the session prelaunch, the following options are available:


You can configure rules when session prelaunch must not be used. The following options are available:

Exclude sessions pre-launch:

It allows you to specify dates on which the pre-launch must not be used. Click on the plus-sign icon and select a date. The list can contain multiple entries.

Extended Session Prelaunch for Parallels Client:

Session prelaunch is now extended to other platform-specific clients including macOS, Linux, iOS, and Android. 

  1. Enable sessions prelaunch via RAS Policies > Session or Connection > Session prelaunch, or from Parallels Client.
  2. Select Session prelaunch Basic or Machine learning mode.

Mac Client:

Android Client:


Was this article helpful?

Tell us how we can improve it.