After you have installed the 2X ApplicationServer & LoadBalancer Client, you can now launch the 2X ApplicationServer & LoadBalancer Client to access your published applications.

To open the 2X ApplicationServer & LoadBalancer Client:

Configuring 2X ApplicationServer & LoadBalancer Client for Windows

When launching the 2X ApplicationServer & LoadBalancer Client you will be prompted to configure a new 2X connection. Please refer to the ‘Farm’ section below for more information about how to setup a new 2X connection

2X ApplicationServer Client for Windows is able to connect with multiple farms where farms is a common term used in remote session computing to refer to a group of Terminal Servers. A 2X Farm consists of a 2X Publishing Agent joined with one or more 2X Terminal Server Agents.

One or more 2X Client Gateway can be used to expose the 2X Farm. To add a new farm in the 2X Client, one should use the hostname or IP where the 2X Client Gateway Service is installed.

Farms

The first thing you must do is to add a new farm, by clicking ‘File’ and select ‘Add New 2X Connection...’ or right click on ‘2X Connections’ and click ‘Add New 2X Connection...’.

Application Server

In the Application Server area, type the Primary Server name or IP. This should be the name or IP where the 2X Client Gateway resides.

If your administrator enabled ‘Broadcast 2X Client Gateway Address’ option on the server, you can click on the browse button ‘...’ and you should see the available farm/s in your area. If you do not see any farms, simply ask your administrator for the application server IP and port and add this information manually. You can also add a Secondary Server, in case a backup 2X Client Gateway is available.

The Client may choose the connection mode and has three ways to connect.

In Regular Gateway mode the Clients are connected with the 2X Client Gateway and another connection is made between the 2X Client Gateway and the Terminal Servers.

In Direct mode connection the Clients first ask the 2X LoadBalancer for the best available Terminal Server and then connect directly with the Terminal Server.

In SSL mode, the connection is done as in the regular gateway mode but the connection is encrypted.

NOTE: In order to connect through the 2X Client Gateway you just need to set the port number that was configured on the Client Gateway Port in the Connection Settings Page. (Default Gateway Port 80)

Logon

Enable ‘Logon automatically to the Farm’ to enable the 2X Client connect automatically instead of displaying the logon page every time you need to access the farm.

Use System Credentials (SSO) – To use the local current system credentials when connecting with that particular farm enable ‘Use System Credentials (SSO). When you enable this option, you’ll automatically log-in when connecting with the 2X Client Gateway and the Terminal Servers. Please note that you need to choose to install this module while installing the 2X ApplicationServer Client to be able to use the SSO.

On the ‘Logon’ section, enter your username, password and domain to be used when retrieving your published applications. This information is saved, encrypted, locally under the HKCU hive.

Local Resources

In case you want to configure how local resources are handled by the terminal server, simply click on the ‘Local Resources’ tab and select the options you want (these are the same options available with the regular Microsoft RDP Client).

Experience

The experience tab allows you to tweak the connection speed to optimize the performance of the connection with the remote host.

If you are using a connection to a remote computer in a local network that runs at 100mbit or up, it is usually safe to have all of the experience options turned on.

Network

In the Network Tab you may configure network settings to be able to connect to 2X ApplicationServer using a proxy.

To be able to connect to a Proxy Server, check the Use Proxy Server checkbox. The following are different proxy connection types that can be used:

SOCKS4 – Enable this option to transparently use the service of a network firewall.

SOCKS4A – Enable this option to allow a client that cannot connect to resolve the destination host’s name to specify it.

SOCKS5 – Enable this option to be able to connect using authentication.

HTTP 1.1 – Enable this option to connect using standard HTTP 1.1 protocol connections.

After selecting a connection type, the Proxy Host (domain name or IP Address) and port number have to be specified.

For SOCKS5 and HTTP 1.1 connections, authentication has to be enabled, check the Proxy Requires Authentication checkbox, and type in user credentials.

Advanced Settings

Use Client System Colors - Enable this option to use the client system Colors instead those specified on the Terminal Server.

Use Client System Settings – Enable this option to use the client system settings instead those specified on the Terminal Server.

Create shortcuts configured on server – For each published application, the administrator can configure shortcuts on the clients desktop and start menu folder. With this option one can choose to have or not to have these shortcuts.

Register file extensions associated form the server – For each published application, the administrator can associate certain file extensions. With this option the client can choose to register or not these file extensions.

Redirect URLs to client - Enable this option to use the local web browser when opening ‘http:’ links.

Redirect Mail to client – Enable this option to use the local mail client when opening ‘mailto:’ links.

Reconnect if connection is dropped – Enable this option to automatically reconnect to the Terminal Server if the connection is dropped.

Embed published desktop in Launcher – Enable this option to access the published desktop inside the 2X ApplicationServer Client

Span desktops on all monitors – Enable this option to span the published desktops across al connected monitors.

Enable desktop smart sizing – Desktop smart sizing enables the Clients to scale the Client window display of desktop when resizing.

Use primary monitor only for published applications – Enable this to start published applications in your primary monitor only and not have it span through all the monitors connected to your system.

2X Universal Printing

To use the 2X Universal Printing, the Clients will just have to click ‘Print’ while using the published application on the Terminal Server and select ‘2X Universal PDF Printer’.

In the 2X Universal Printing tab the Client can configure to choose:

Print to default printer – Use the default printer on the client side.

Select printer before printing – Open the dialog to choose the printer before printing.

Use the following printer – Click on ‘...’ to select the printer and always use the selected printer when printing through the 2X Universal PDF Printer.

View document to print – Use this option to view the printed document using the default PDF viewer instead of printing.

Options

In the Options Area one can select to choose the data format output. The options are Portable Document Format (PDF), Enhanced Meta File (EMF) and Bitmap (BMP).

Advanced Settings

In the Advanced Settings tab, you may configure the default behavior of 2X ApplicationServer & LoadBalancer Client.

Hide Launcher when application is launched - If this option is enabled, the launcher will get minimized in the system tray after an application is launched.

Always on Top - To enable 'Always on Top' feature, highlight the 'Always on Top’ checkbox. With this feature enabled other applications will no longer mask the launcher.

Do not warn if server certificate is not verified – When connected over SSL, and the certificate is not verified a warning message will be displayed. One can disable this warning message by enabling this option.

Show folders page – To show the folders page in the 2x Client enable this option. This will show the available folders while showing the hierarchy of the application groups as configured on the server.

Minimize to tray on close or escape – Enable this feature to place the 2X ApplicationServer Client to the System Tray when click on the close button or hit escape.

Enable the Client to reconnect automatically to a session in the event of a network failure – To reconnect automatically in the event of a network failure enable this option.

Launch automatically at Windows startup – This option will place a shortcut in the start menu folder of the Client and the 2X Client will launch automatically with the Windows startup.

Span Desktops on all monitors – Enable this option to span the published desktops across al connected monitors.

Add Farm automatically when starting web or shortcuts items – This option will add the preferences of the farm in the 2X Client when starting an item contained in a farm that is not yet listed.

Don't show prompt message for auto add farms – Enable this option to disable prompt messages when adding auto farms.

Auto Refresh Farms – Enable this option to auto refresh each farm; hence check continuously that each farm is still alive.

Enable Desktop smart sizing – Desktop smart sizing enables the Clients to scale the Client window display of desktop when resizing.

Check for updates on startup – This option is available only with administrative rights. On the startup of the 2X Client, it will check for any available updates of the Client.

In the Advanced Settings tab click ‘Check for updates now ...’ to check if there are any available updates for 2X Client. If there are updates available one can click ‘Update’ which will download the latest setup and install the Client or click ‘Download’ which will download the latest setup to a specified location.

Listing of Published Applications

After configuring the 2X ApplicationServer & LoadBalancer Client simply click ‘OK’. If you entered a valid username and password and the server IP address and port are correct, you should see the list of published applications available to your username/computer/IP address on the main window.

If you want to create shortcuts for your published applications on your local desktop computer, simply right click an application and select ‘Create shortcut’. A shortcut for that application will be placed on your desktop.

NOTE: The 2X ApplicationServer & LoadBalancer Client uses the Microsoft RDP protocol when connecting to your terminal servers. This means it fully supports all the features supported by the RDP 5.2 specifications at the time of writing. In case some of these do not work as expected, try launching the regular Microsoft RDP Client and connect to your terminal servers to see if they work or not. If they work as expected but do not work when using the 2X ApplicationServer & LoadBalancer Client, please contact our technical support as explained on the ‘Troubleshooting’ section of this manual.

Terminal Server Connection

2X ApplicationServer Client is able to connect to multiple Terminal Server Desktops using an RDP connection. To connect to a desktop click ‘File’ and select ‘Add New Terminal Server Connection...’

Connection

Connection settings

In the Connection settings area, type the Primary Connection name or IP. This should be the name or IP of the desktop you want to connect to. The ‘Alias’ will give the connection a display name for better readability.

NOTE: In order to connect through the 2X Client Gateway you just need to set the Port number that was configured on the Client Gateway Port in the Connection Settings Page. (Default Gateway Port 80)

Logon

Enable ‘Auto Login’ to automatically log into the remote desktop when accessing it

Use System Credentials (SSO) – To use the local current system credentials when connecting with that particular farm enable ‘Use System Credentials (SSO). When you enable this option, you’ll automatically automate the log-in process when connecting with the 2X Client Gateway and the Terminal Servers. Please note that you need to choose to install this module while installing the 2X ApplicationServer Client to be able to use the SSO.

On the ‘Logon’ section, enter your username, password and domain to be used when retrieving your published applications. This information is saved, encrypted, locally under the HKCU hive.

Display

Remote desktop size

To configure the desktop size using the available area on the client enable ‘Use available area’. To configure a pre defined desktop size disable ‘Use available area’ and choose the size of the published desktop by dragging the slider ‘Size’ in the properties section. To obtain a full screen view, drag the slider all the way to the right.

Remote desktop size

Display the connection bar when in fullscreen mode – This will show the RDP connection bar at the top of the page.

Embed published desktop in Launcher – Enable this option to access the published desktop inside the 2X ApplicationServer Client

Connect to console – Enable this option to connect to the console session (session 0) of the Terminal Server

Span desktops on all monitors – Enable this option to span the published desktops across al connected monitors.

Enable desktop smart sizing – Desktop smart sizing enables the Clients to scale the Client window display of desktop when resizing.

Local Resources

Programs

Start a program

Enable ‘Start the following program on connection’ to start an application when a connection to the remote desktop is established.

Type the path and file name of the application that you would like to launch in the ‘Program path and file name’ field (Example – “c:\windows\notepad.exe”).

You can also set a start folder in the ‘Start in the following folder’ field (Example – “c:\windows”).

Experience

The experience tab allows you to tweak the connection speed to optimize the performance of the connection with the remote host.

If you are using a connection to a remote computer in a local network that runs at 100mbit or up, it is usually safe to have all of the experience options turned on.