Connection

To configure connection properties, select the Connection node and then go through each child node configuring their respective properties.

Primary Connection

The primary connection always defaults to the primary RAS Secure Gateway, but you can modify the following connection properties:

1. Specify a friendly name for the connection.

2. Auto login: Enable or disable auto login in RAS User Portal. If the option is disabled, auto login will be disabled in User Portal and the user will not be able to change it. For more information, see Auto Login.

3. In the Authentication type drop-down list, select the desired method of authentication:

   • Credentials. The user will have to enter credentials to log on.

   • Single Sign-On. This option will be included in the list only if the Single Sign-On module is installed during Parallels Client installation. The credentials that the user used to log on will be used to connect to the remote server.

   • Smart Card. Select this option to authenticate using a smart card. When connecting to the remote server, a user will need to insert a smart card into the card reader and then enter a PIN when prompted.

   • Web. If selected, the SAML SSO authentication is allowed. For more information, see SAML SSO Authentication.

   • Web + Credentials. The same as Web, but users are prompted to enter credentials when they launch a published application. To enable the Web + Credentials method, you must configure your IdP and RAS as described in IdP side configuration and SP side configuration.

Note: Smart card authentication is not supported in Parallels Client for Linux.

Note: The Web + Credentials method works only in Parallels Client for Windows.

Note: The allowed authentication type(s) must be specified in RAS Console in Connection > Authentication.

1. Select or clear Save password as needed (if credentials are used for authentication). This means forcing a client to save the password for this connection.

2. Specify the domain name (if credentials are used for authentication).

Secondary Connection

If you have more than one RAS Secure Gateway, you can define a secondary connection, which will be used as a backup connection in case the primary gateway connection fails.

To add a secondary connection:

1. Select the Secondary connections item.

2. In the Secondary connections pane, click Tasks > Add and specify a server name or IP address.

3. Select the connection mode and modify the default port number if necessary.

If you have multiple secondary connections, you can move them up or down in the list. If the primary connection cannot be established, Parallels Client will use secondary connections in the order listed.

Reconnection

In this pane, specify what to do if the connection is dropped:

• Reconnect if connection is dropped. if this option is selected, Parallels Client will try to reconnect if the connection is dropped. The Connection retries property specifies the number of retries.

• Show connection banner if reconnection is not established within. Specifies the number of seconds after which the connection banner will be displayed in Parallels Client. This will inform the user that the connection was dropped and will allow them to take actions on their own.

Computer name

Specify the name that a computer will use during a remote desktop session. If set, this will override the default computer name. Any filtering set by the administrator on the server side will make use of the Override computer name setting.

Advanced settings

• Connection timeout. The Parallels Client connection timeout value.

• Show connection banner if connection is not established within. Specifies the number of seconds after which the connection banner will be displayed. This will inform the user that the connection cannot be established and will allow them to take actions on their own.

• Show desktop if published application does not start within. If a published application is not launched within the time period specified in this field, the host server desktop will be shown instead. This is helpful if an error occurs on the server side while launching an application. By showing the server desktop, the user can see the error message.

Web authentication

• Select or clear the Use default OS browser option. If the option is selected, the SAML SSO login dialog on the client side will open in the default browser. If the option is cleared, the browser built into the Parallels Client will be used.

• The Open browser window to complete log out option is used when the built-in browser is used. In this case, there's no control over the SAML log out, so when this option is selected, a URL will open to perform the logout from SAML. By default, this web page will not be displayed, but if you need to interact with the browser, you can enable this option.

For more info, see SAML SSO Authentication.

Session prelaunch

When a user opens a remote application, 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.

To enable (or disable) session prelaunch, choose one of the following in the Mode drop-down list:

• Off. No session prelaunch is used.

• Basic. A session is prelaunched as soon as the user gets the application listing. The assumption is, the user will open an application within the next few minutes. The session will stay active for 10 minutes. If the user doesn't open an application during that time, the client will disconnect from the session.

• Machine Learning. When the application listing is acquired, a session is prelaunched based on user habits. With this option enabled, Parallels Client will record and analyze the user habits of launching applications on a given day of the week. A session is started a few minutes before the user usually opens an application.

When a session is prelaunched, 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 prelaunched session, so it will start very quickly.

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

• Use the Exclude sessions prelaunch list to specify dates on which the prelaunch must not be used. Click on the plus-sign icon and select a date. The list can contain multiple entries.

• You can also exclude a published resource from the session prelaunching scheme altogether. This way, the resource is excluded from the analysis and is never considered by Parallels Client when making a decision whether to prelaunch a session. For example, when you have a server on which you never want to prelaunch sessions, you can flag all published resources hosted by that server as to be excluded from session prelaunch. To exclude a published resource from session prelaunch, in the RAS Console, navigate to Published Resources, select a resource and then select the Exclude from session prelaunch option.

Local proxy address

The setting in this section specifies to which IP address to bind the local RDP proxy. Select the Use 127.0.01 IP address when using Gateway mode in VPN scenarios option. You should have this setting enabled. Disabling it may lead to users not being able to open applications or desktops when using a VPN. This setting applies to Parallels Client for Windows only.