2 x application server

Introduction 1

2XApplication Server XG v10.6

Introduction 2

URL: www.2x.com

E-mail: [email protected]

Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of 2X SOFTWARE Ltd.

2X ApplicationServer is a copyright of 2X SOFTWARE Ltd. 1999-2012 2X SOFTWARE Ltd. All rights reserved.

Version 10.6 Last updated July 25, 2013

Introduction 3

Contents

Introduction 6

What is 2X ApplicationServer and How Does it Work? .................................... 6 How Does it Work? ........................................................................................... 6 2X ApplicationServer System Requirements .................................................... 7

Installing 2X ApplicationServer 8

2X ApplicationServer Services ........................................................................ 12 Pre- Configuration MS Terminal Server Settings ............................................ 13 Server Settings................................................................................................ 13 Connection Settings ........................................................................................ 14

Configuring 2X ApplicationServer 16

Introduction to the Configuration of ApplicationServer ................................... 16 2X ApplicationServer Console Environment & Components .......................... 17 Components of the Navigation Bar ................................................................. 17 Console Environment ...................................................................................... 18 Console Environment Basic Layout ............................................................. 19 Main Menu - 2X Console Settings .................................................................. 20

2X Startup Wizard 23

Publish a Virtual Desktop ................................................................................ 24 Publish an Application ..................................................................................... 25 Publish a Desktop ........................................................................................... 27 Setup LoadBalancer ....................................................................................... 28

Farm 29

Terminal Servers ............................................................................................. 31 Find a Terminal Server ................................................................................... 32 Add a Terminal Server .................................................................................... 33 Editing a Terminal Server ............................................................................... 34 Delete a Terminal Server ................................................................................ 41 Server Groups ................................................................................................. 41 VDI Hosts ........................................................................................................ 42 Find a VDI Host ............................................................................................... 43 Add a VDI Host ............................................................................................... 44 Edit a Virtual Host ........................................................................................... 51 Delete a Virtual Host ....................................................................................... 51 Check Agent .................................................................................................... 52 VDI Virtual Guests Settings ............................................................................ 53 Pool Management ........................................................................................... 55 2X Templates .................................................................................................. 59 Maintenance Mode ......................................................................................... 62 Persistent Guests ............................................................................................ 67 Remote PCs .................................................................................................... 68 Find Remote PCs ........................................................................................... 69 Add /Delete Remote PCs ............................................................................... 70 Edit a Remote PC ........................................................................................... 71 Gateways ........................................................................................................ 75 Installing the 2X Secure Client Gateway Remotely from the 2X Console ...................................................................................................... 76 2X Secure Client Gateway Properties ............................................................ 78 Backup Servers ............................................................................................... 92 Adding 2X Backup Servers ............................................................................. 93 Modifying 2X Backup Servers ......................................................................... 96 Promoting a Backup server to Master Server ................................................. 96 Solution Guide................................................................................................. 97

Introduction 4

Load Balancing 98

Load Balancing ............................................................................................... 98 Counters .......................................................................................................... 99 Advanced Settings ........................................................................................ 100 Tunneling Policies ......................................................................................... 101

Publishing 104

2X Publishing Wizard .................................................................................... 104 Applications ................................................................................................... 105 Folder ............................................................................................................ 121 Publish Document Content ........................................................................... 142 Publish Applications using Drag and Drop ................................................... 150 Publish Applications Configuration ............................................................... 151 Setup LoadBalancer ..................................................................................... 152

2X Universal Printing 153

Universal Printing .......................................................................................... 153 Fonts Management ....................................................................................... 155

2X Universal Scanning 156

Universal Scanning ....................................................................................... 156 Scanning Applications ................................................................................... 157

Connection Settings 159

2X Publishing Agent ...................................................................................... 159 Second Level Authentication ........................................................................ 161

Client Manager 172

Devices ......................................................................................................... 172 Devices States .............................................................................................. 173 Manually adding a device ............................................................................. 174 Editing device settings .................................................................................. 190 Deleting a device........................................................................................... 190 Allow/Deny devices ....................................................................................... 190 Options .......................................................................................................... 191 Device Report ............................................................................................... 196 Groups .......................................................................................................... 198 2XOS ............................................................................................................. 200 Printers .......................................................................................................... 202 Banner ........................................................................................................... 204 Scheduler ...................................................................................................... 205 2X Client Policies Tab ................................................................................... 207

Information 212

Status Tab ..................................................................................................... 212 Notification Tab ............................................................................................. 213 Logging Tab .................................................................................................. 215 Auditing Tab .................................................................................................. 216 Software Update Tab .................................................................................... 217 Support Tab .................................................................................................. 218

Reporting 220

Selecting a Reporting Engine ....................................................................... 220 Using eG Innovations Reporting Engine ....................................................... 220

Licensing 224

Introduction 5

Available 2X Clients 226

Installing the 2X Terminal Server Agent Manually 227

2X Terminal Server Agent System requirements ......................................... 227 Installation Procedure ................................................................................... 227

Installing the 2X VDI Agent Manually 232

2X VDI Agent System requirements ............................................................. 232 Installing the 2X VDI Agent Manually ........................................................... 232

Installing the 2X Gateway Manually 238

Installing the 2X Guest Agent Manually 243

2X Guest Agent System requirements ......................................................... 243 Installing the 2X Guest Agent Manually ........................................................ 243

Installing the 2X PC Agent Manually 248

2X PC Agent System requirements .............................................................. 248 Installing the 2X PC Agent Manually ............................................................ 248

2X Additional Utilities 253

2XA Generator .............................................................................................. 253 Parameters .................................................................................................... 253 2XA Generator Examples ............................................................................. 254

Features 255

Additional Resources .................................................................................... 257

Troubleshooting and Support 258

Introduction ................................................................................................... 258 Knowledgebase............................................................................................. 258 Request Support via E-mail .......................................................................... 258 Request Support via Phone .......................................................................... 258

About 2X 259

Introduction 6

INTRODUCTION

What is 2X ApplicationServer and How Does it Work?

2X ApplicationServer XG provides vendor independent virtual desktop and application delivery from a single platform. Accessible from anywhere with the 2X Cloud Portal, 2X ApplicationServer XG allows you to publish full desktops and applications within a virtual environment, improving desktop manageability, security and performance. 2X ApplicationServer XG extends Windows Terminal Services by using a customized shell and virtual channel applications using the Microsoft RDP protocol. It supports all major Hypervisors from Microsoft, VMware, Citrix and more enabling the publishing of virtual desktops and applications to the 2X Client. The product includes powerful universal printing and scanning functionality, high capacity resource based load balancing and management features. With the 2X ClientManager Module for 2X ApplicationServer XG you can also centrally manage user connections, thin client and PCs converted into thin clients using the free 2XOS.

How Does it Work?

When a client requests a virtual desktop, the system finds a guest on one of the least loaded hosts and starts or restores the guest connection. Using Microsoft RDP protocol, the virtual desktop is presented to the user.

Thin client computing is solving the growing management problem of fat clients (PCs), allowing employees to roam easily and seamlessly, improving performance. Companies that have migrated to a thin client environment consistently see huge savings on support, hardware and upgrade costs. In a world where energy use is an increasing concern, implementing a thin client environment improves energy costs as well. A study conducted by Bloor Research shows that "Deploying thin client technology across enterprises can cut costs by up to 70%".

Introduction 7

2X ApplicationServer System Requirements

2X Publishing Agent and 2X SecureClientGateway are preferably installed on the following operating systems: Windows Server 2012, Windows 2008/R2Server/Enterprise Server; Windows 2003 Server/Enterprise Server.

2X Terminal Server Agent must be installed on Windows Server 2012 with Remote Desktop Services role, Windows 2008/R2Server/Enterprise Server with Remote Desktop Services role; Windows 2003 Server/Enterprise Server with Terminal Services enabled.

For supported desktop 2X Client please click the link for more information.

2X Client is also supported on different mobile platforms including Android, iOS and Blackberry.

NOTE: The 30-day trial version and the full version of the application have the same features. After the 30-day trial period has expired, the only action necessary will be to enter a valid license key on the Licensing page. Re-installation will not be necessary. Please refer to the Licensing chapter in this manual for more information.


INSTALLING 2X APPLICATIONSERVER

Before you run the installation procedure please make sure that you are logged on with administrator rights and that the system requirements are met. Make sure all other Window programs are closed. The 2XAppServer.msi file can be found on our website, www.2X.com, available as a free download. Run the 2X ApplicationServer setup program on the machine to be used as your access point to your terminal servers and/or virtual hosts. Choose what to install according to your needs and requirements. Two common scenarios are the regular gateway scenario and the direct mode scenario. For more advanced and alternative scenarios and solutions please read 2X Server Based Computing Guide. Double click on the 2XAppServer.msi file and a welcome dialog box will appear. Click Next.

2X ApplicationServer Setup Program welcome screen.

Accept the license agreement by checking the I accept the terms in the License Agreement checkbox.


The License Agreement.

Accept the default location or Browse to where you want to install 2X ApplicationServer and click Next.

Choosing the location where 2X ApplicationServer will be installed.

Select 2X ApplicationServer XG for complete product installation.


Choose Your Installation type Setup Wizard installs 2X ApplicationServer

Click install to continue with the installation of 2X ApplicationServer.

Click on Finish to launch the Configuration Utility. If the utility does not automatically open, go to Start>2X Application Server Console to launch the utility.


Setup Completed


2X ApplicationServer Services

To start, stop and configure 2X ApplicationServer Services, run the Microsoft Management Console Services.msc. 2X ApplicationServer services are configured to start automatically when the system starts. The services installed depend on the installation you selected.

2X Secure Client Gateway, 2X Publishing Agent, 2X Redundancy Service and 2X Terminal Server Agent, 2X VDI Agent

2X Publishing Agent - provides load balanced applications and desktop publishing.

2X Redundancy Service - provides redundancy to 2X ApplicationServer

2X SecureClientGateway - tunnels all traffic needed by 2X applications on a single port and provides secure connections.

2X TerminalServer Agent provides terminal server information to 2X Publishing Agent

2X VDI Agent provides VDI host information to the 2X Publishing Agent

NOTE: All users who are connected via the 2X Secure Client Gateway will be disconnected if the 2X Secure Client Gateway service is stopped or restarted. Note that the default port (80) may already be in use (for example, by an HTTP server) in this case it will be necessary to use a port number not currently in use by other local services.


Pre- Configuration MS Terminal Server Settings

With Terminal Services Configuration, you can reconfigure the properties of the RDP-TCP connection, including limiting the amount of time client sessions can remain active on the server, setting protection levels for encryption, and selecting which permissions you want users and groups to have. Terminal Services Group Policies or Terminal Services extension to Local Users and Groups are the settings that you use to set connection properties on a per-user basis. You can set different session time limits for each user when you use the Terminal Services extension to Local Users and Groups. Use Terminal Services Configuration to set the same time limit to all users who log on using the same server connection.

Configuring Terminal Services Connections

From the Start menu > Administrative Tools>Terminal Services Configuration

Server Settings

Click on Server Settings and click the Restrict each user to one session option. This enables reconnections to previously disconnected user sessions, conserving server resources.

NOTE: This feature is also configurable in the Load Balancing section.


Connection Settings

Select Connections and double-click the RDP-TCP connection. This will open the RDPTCP Properties dialog box.

Logon Settings Tab

Logon Settings

Verify that the Always prompt for password checkbox is unchecked; allowing clients to launch applications using the credentials that have been saved on the 2X Client. This will avoid unnecessary repeated authentication cycles.


Environment Tab

Environment

On the Environment tab make sure that the option Run initial program specified by user profile and Remote Desktop Connection or Terminal Services client is ENABLED. Click Ok.


CONFIGURING 2X APPLICATIONSERVER

Introduction to the Configuration of ApplicationServer

After you have installed 2X ApplicationServer you can now launch the 2X ApplicationServer Console for additional configuration.

Launching the 2X ApplicationServer Console

To open the 2X ApplicationServer Console go to: Start > [All] Programs > 2X > ApplicationServer > 2X ApplicationServer Console


2X ApplicationServer Console Environment & Components

The 2X ApplicationServer Console is a completely self-contained environment that is used to enable Universal Printing and Scanning, publish seamless applications, also providing load balancing to published desktop sessions and Virtual Desktop Hosts, Terminal Server and/or Citrix sessions. Below is a brief description of each component located in the Navigation Bar.

Components of the Navigation Bar

Farm

Add Virtual Desktop Hosts, Microsoft Terminal Servers and Citrix Servers to the farm.

Load Balancing

Choose the load balancing method to be used.

Publishing

Publish applications, application groups, virtual desktops and desktops.

Universal Printing

Enable Universal Printing to each Terminal Server.

Universal Scanning

Enable Universal Scanning to each Terminal Server.

Connection Settings

Configure which port to use for each service.

Client Settings

Configure and enable client settings.

Information

Find information about the modules used, enable logging, and enable notification.

Licensing

Obtain or review your licensing information and license number for 2X ApplicationServer products.


Console Environment

Console Environment/Publishing

11.. The Navigation Bar enables you to navigate through the main features offered by 2X ApplicationServer Console. You can also change which features are displayed using the View Menu.

22.. The Published Applications Explorer panel is a navigational tree which represents the organization of your published applications, application groups and desktops.

33.. The Published Applications Properties panel contains up to four additional tabs that will display Information, Publish From, Application and Filtering options for each published application.

44.. The Publishing Tools allow you to Add, Delete, and Disable, Sort and Find for selected published applications. You can also move your published applications using the Move Up or Move Down tools. The publishing tools also provide you with the ability to publish your applications to the web.

55.. The Toolbar consists of a set of tools grouped together that provides quick and convenient access to commonly performed operations.


Console Environment Basic Layout

Console Environment Basic Layout

1. The Navigation Bar enables you to navigate through the main features offered by the 2X Console. You can also select which main feature to be displayed from the View Menu.

2. The Properties Pane is the main area from where you can edit and modify each configuration.

3. The Information Pane gives a quick look and summary about the particular selected page.

4. The Toolbar consists of a set of tools grouped together to provide quick and convenient access to commonly-performed operations.


Main Menu - 2X Console Settings

File Menu

2X ApplicationServer will allow you to easily backup and restore your configuration. The entire configuration is saved to a .dat file in XML format. This tool can also be useful if you want to distribute the same settings across other 2X Consoles.

File Import Settings and Export Settings

To Backup Settings Click File and Export Settings and make sure to save the .dat file in a secure location.

To Restore Settings Click File and Import Settings and open the .dat file. The settings will be retrieved and activated after you click the Apply button. The configuration files include all the settings that have been configured and saved throughout the 2X ApplicationServer console. This includes all terminal servers, load balancing methods, list of applications, connection settings and the license keys. This tool is very useful as a configuration backup procedure, especially if you would like to distribute the same settings across other installations of the 2X ApplicationServer applications.


View Menu

The View Menu enables you to navigate through the main features offered by the 2X Console. You can also choose to view or not to view the toolbar from this menu.

Language Menu

Changing the language to your preferred language is as easy as clicking on the Language menu. This feature allows you to change all functions in the console to your preferred language. The default language will use the language that is configured in the Regional and Language Options.

Help Menu

The Help menu contains several features listed below:

Access the 2X ApplicationServer by clicking on Manual

Online version of the manual

Obtain contextual help about a particular field or control by clicking on Help>Context Help. When the mouse pointer changes to a ? pointer, you are able to click on any item and display relevant help for that particular field or control. You may also use F1 or click on the Help button located in the right-bottom corner of the console.

To order online while you are using the console, click on Help and select Order Online A new page will open in your default browser guiding you on how to order this product.

Sending a query to 2X support is as easy as clicking on the Help menu and selecting Send Support Request. A form will load and you will be able to enter the details of the problem and your information.

Version information of the product.

NOTE: The application will automatically send your settings and the current log file so that 2X support can replicate your problem. You are also able to send an attachment with your query such as a screenshot to support your query.


Toolbar Settings

To customize the toolbar, right click in the Toolbar area and select Customize You can customize the button and icon view according to your preferences.

Toolbar Settings


2X STARTUP WIZARD

2X ApplicationServer incorporates a Startup Wizard which will guide you through each step needed to setup Virtual Desktops, Published Applications, Published Desktops or Terminal Servers (for load balancing) in a quick and efficient manner. In the toolbar area, simply click on the Wizard icon or you can also choose from the options located in the tool bar of 2X ApplicationServer Console.

NOTE: Press Cancel if you want to configure your farm manually. Click here to go directly to setting up your Farm.

Startup Wizard

Start by selecting what you want to publish. You can choose from:

Virtual Desktop Add a new Virtual Host and publish a virtual desktop.

Published Application Add a new Terminal Server and publish applications.

Published Desktop Add a new Terminal Server and publish a desktop.

Setup LoadBalancer Add Terminal Servers to the 2X LoadBalancer


Publish a Virtual Desktop

Virtual Desktop Configuration

Enter a Name and Description for the published virtual desktop.

Properties

In the Connect to field, choose where you want your Virtual Desktop to connect to:

Any Guest The Virtual Desktop connects to any guest from a selected Pool. Click on the drop down arrow to choose which Pool to connect to.

Specific Guest - Will connect the virtual desktop to a specific Guest. Click on the drop down arrow to choose Virtual Guest.

Guest - Connects the Virtual Desktop to a Guest from a selected Pool. Click on the drop down arrow to choose the Pool. In the where name equals field, select the Username or IP Address.

Specific 2X Template This option will allow you to connect the Virtual Desktop to a specific 2X Template.

Persistent Checkbox

Check this box so that the User connects to the same Guest. (Available with Any Guest, Guest and Specific 2X Template)


Publish an Application

Select where you want to publish the application from:

All Servers in Farm - includes all the servers that are added to the farm. If only one server is present you will be automatically be taken to the Startup Wizard Publish Applications dialog box.

Server Groups This option is not available for publishing applications.

Individual Servers - allows you to choose the servers you would like to use to publish an application one by one by checking the checkbox next to the name of the server.

New Server - add a new server to the farm and use it to publish an application.

Publish An Application


Add Applications

Click on the Browse button and select the Executable (.exe) file of the application that you would like to publish. You can also drag and drop an executable (.exe) file onto the box at the top of the dialog box. You will see a new entry in the list box which shows all applications that will be published. When all applications to be published have been selected, click on Finish.

Publish Applications


Publish a Desktop

Select where you want to publish the desktop from:

All Servers in Farm - Includes all the servers that are added to the farm. If only one server is present you will be automatically be taken to the Startup Wizard Publish Applications dialog box.

Server Groups This option is not available for publishing desktops.

Individual Servers - Allows you to choose the servers you would like to use to publish a desktop, by checking the checkbox next to the name of the server.

New Server - Add a new server to the farm and use it to publish an desktop.

Published Desktop

After you have determined the source of the published desktop, all you need to do is name it and add a description.

Click Finish to complete the process.


Setup LoadBalancer

Select Setup LoadBalancer. Each available server in the farm is listed and the information regarding each Agent is also listed.

Select the connection type. The choices are MS Terminal Server (RDP), Citrix Server (ICA) or Both (RDP/ICA).

Check the box next to each server that you would like to add to the LoadBalancer.

Select the server to be used for load balancing

When you have selected all the servers that you want to add, simply click on Finish.

Farm 29

FARM

2X ApplicationServer provides connectivity with Multiple Farms and the ability to publish seamless applications or published desktops from multiple servers simultaneously.

Farm Info Tab

Click on Farm in the Navigation panel. The Farm Info tab lists the amount of Active Servers, Backup Servers, Gateways, Remote PCs, Terminal Servers, VDI Hosts, VDI Pools and 2X Templates (not shown) in the information panel.

Farm 30

Farm Design Tab

In the Farm Design tab administrators are allowed to view and change their infrastructure graphically, providing ease of use and administrative control. You can easily add Terminal Servers, Gateways, hypervisors and other network components.

Farm Design Tab

From the toolbar, select the component to add from the following:Terminal Server

VDI Host

Remote PC

Gateway

Backup Server

Farm 31

Terminal Servers

On this page you can add Terminal Servers or Citrix Servers to the farm. You have two options to add servers to the farm. You can either automatically search for available Terminal Servers or Citrix Servers within your domain by clicking the Find button

Or

You can click on the Add button to add the Terminal Servers or Citrix Servers if you know the machine name or IP address.

Add Terminal Servers or Citrix Servers to the farm

NOTE: The checkbox next to the server name indicates that the particular server is available to users on this farm. To disable a server temporarily, uncheck this box.

Farm 32

Find a Terminal Server

Click the Find button to automatically search for available Terminal Servers and Citrix Servers.

Find available Terminal Servers

All Terminal Servers and Citrix Servers within your domain will appear on the list of available servers to your farm, also identifying terminal server type (Windows or Citrix) and availability of 2X Terminal Server Agent on the respective server. To add a server to the farm, enable the checkbox in front of the server name. Click the OK button to save your changes.

NOTE: It will be necessary to install 2X Terminal Server Agent on all Terminal Servers and Citrix Servers before they can successfully participate in a load-balanced farm.

Farm 33

Add a Terminal Server

To add a server to your farm click the Add button and then type the server name or IP address in the Server: field as shown in the figure below. Then click Next.

Configure each server properties

2X ApplicationServer will check and make sure that the 2X Terminal Server Agent is installed. Check the status and if the service is not installed, click the Install button. . If you unable to install the Terminal Server Agent please refer to section TS Agent manual Installation to manually install the agent.

Add Terminal Server

Click Add if the Agent is already installed.

Farm 34

Editing a Terminal Server

To edit the configuration of each Server, select a server and click the Properties button.

You can also double click each Server to edit its configuration.

Properties Tab

Server Properties / Properties Tab

Enable or disable the use of the terminal server in the farm by using the Enable Server in farm checkbox.

To change the server name or IP address of a particular terminal server, use the Server field. Each terminal server can be configured to accept RDP traffic, ICA traffic or both from the Type field.

Enter the maximum number of sessions you want this server to accept. A Description can be added to each server to clearly identify each terminal server.

Farm 35

Agent Settings Tab

Agent settings

Enter the RDP port that will be used to connect a session.

The Change Direct Address checkbox allows you to configure and enter a new direct address. This address is used in Direct Connection mode only (internal or external IP address); depending on where your clients will be. If the IP address is external, they must be assigned at your firewall to your servers.

Publishing Session Timeout field is used to set the amount of time that each session will stay connected in the background after the user has closed all published applications. This is done to avoid unnecessary reconnections with the server.

Selecting the Allow Client URL/Mail Redirection box allows http and mailto links to be opened using local applications instead of using terminal server resources. The Configure allows the Administrator to block any URLs from being redirected to the clients.

To block URLs, from being redirected to the client, click Configure to open the following window as shown:

Farm 36

Configure URL redirection

Click Add and insert the URLs to be blacklisted in the list box. Press OK after adding the URLs.

To edit a URL from the list box, select the URL you want to edit and click Edit and make the necessary changes.

To remove a URL from the list box, select the URL you want to remove and click Remove.

Please note that URLs that has the first part matching the entry are not sent to the client. URLs are compared as a string and name resolution is not performed.

Selecting the Allow 2XRemoteExec to send command to the client would allow the server session to send commands to the client. This is done by using the command line application called 2XRemoteExec packaged with the 2X ApplicationServer. Command line options include the following:

Command Line Parameter Parameter Description

-s Used to run the 2XRemoteExec in silent mode. When inserted in the command line, pop up messages from the application will be displayed. Omitting this parameter would not display any pop up messages.

-t Is used to specify the timeout until the application is started Timeout must be a value between 5000ms and 30000ms. Note that the value inserted is in ms. If the timeout expires the command returns with an error. Please note that the application might still be started on the client.

-? Shows a help list of the parameters that 2XRemoteExec uses.

Path for Remote Application The Application that will be started on the client as prompted from the server.

The following table shows examples on how to run the 2XRemoteExec.exe command line application:

Examples Action

Shows a message box briefly describing the parameters that can be used.

Shows a message box briefly describing the parameters that can be used.

2XRemoteExec -? Shows a message box briefly describing the parameters that can be used.

2XRemoteExec C:\Windows\System32\Notepad.exe

Runs notepad on the Client.

2XRemoteExec s t 6000 C:\Windows\System32\Notepad.exe C:\read me.txt

Opens the document C:\read me.txt using notepad on the Client. No message is shown and 2XRemoteExec would wait for 6 seconds or until the application is started.

Farm 37

Logging allows the server to log actions that occur on the server; and also identifies any issues related to the server. Click on Request Log to download a copy of the log file. You can clear the servers log file by clicking Clear Log File. This feature can also be accessed on the Terminal Servers tab by right-clicking directly on the server and clicking on Debug Mode. To be able to download or clear the log file, the 2X Terminal Server Agent must be running in debug mode.

Farm 38

RDP Printer Tab

RDP Printer Settings

The RDP Printer tab gives you the option of selecting the format of redirected printers. The format may vary depending of which version and language of the server you are using.

Set your RDP Printer Name Format by choosing from the following three options:

Printername (from Computername) in Session no.

Session no. (computername from) Printername

Printername (redirected Session no)

Farm 39

Check Remove session number from printer name to remove the session number from printer name.

Printer Settings with Redirected Printer

Check Remove client name from printer name to enable that feature.

Printer Settings with Redirected Printer, Removed Client Name and Session Number

Farm 40

Scheduler Tab

Scheduler

Using the Scheduler, you can configure your terminal server to not accept connections between set times. To add a Scheduler Entry simply click Add and enter the date and time you want to restrict access to the terminal server. The Duration field accepts time in days, hours, minutes, seconds or any combination. Example: 3 days, 5 hours, 45 minutes, 30 seconds. The Repeat field allows you to repeat the scheduled entry.

Add Scheduler Entry

The Scheduler tab will be available when editing the terminal servers properties.

On disable field allows you to choose what action should be taken for current sessions by 2X ApplicationServer , once a terminal server has been disabled during a scheduled active entry.

Farm 41

NOTE: 2X Terminal Server Agent should be installed on each terminal server added to the farm. 2X Terminal Server Agent collects the information required by the 2X Publishing Agent so that each session is able to load balance according to available resources. For more information on installing the Terminal Server Agent, please refer to section TS Agent Manual Installation to manually install the agent.

Delete a Terminal Server

To delete a terminal server from the farm, select the particular server and click the Delete button. You can also use the Delete key from the keyboard instead of using the Delete button.

Server Groups

Click the Add button in the Server Groups Panel to create a server group or to organize your terminal servers in groups. In the Name field type the name of the server group; then select the servers that should be included in that group. Server Groups are useful when you want to publish an application or a desktop which is located on a number of MS Terminal Servers but not in the entire farm. For example, you can group MS Terminal Servers that host particular applications and then select that group in the Publish From tab when publishing applications. Groups are also useful when configuring specific filters so that connections to non published desktops can be redirected to specific servers.

Group Properties

Farm 42

VDI Hosts

The VDI Hosts page contains the settings that allow you to add VDI Hosts (VMware, Microsoft Hyper-V, Citrix, Parallels, Microsoft Virtual Server, Oracle VirtualBox, Virtual Iron, etc).

There are two ways to add a VDI Host to the farm. You can automatically search for available VDI Hosts within your domain by clicking the Find button or you can click on the Add button to add the VDI Hosts, if you know the machine specifications.

VDI Hosts Add or Find a VDI Host

NOTE: The checkbox next to the server name indicates that the particular server is available to users on this farm. To temporarily disable a server, uncheck this checkbox.

Farm 43

Find a VDI Host

Click the Find button to automatically search for available VDI Hosts.

Find available VDI Hosts

All VDI Hosts within your domain will appear on the list of available servers to your farm, also identifying agent status, host type and version. To add a server to the farm, check the box in front of the server name the click OK. Click on the Install Agent button to install the VDI Agent. For more information please refer to Installing the 2X VDI Agent Manually.

Farm 44

Add a VDI Host

To remotely add a host to your farm click the Add button and then choose a VDI Type. Enter the host name or IP address in the VDI Host: field as shown in the figure below. Appliance settings can only be used with certain servers. Please refer to the list of approved providers and choose the specific document for more information on how to connect to your virtual host.

Remotely add a new Host

Click Next to continue.

Farm 45

2X ApplicationServer will check to make sure the 2X VDI Agent is installed. If the Agent did not reply or the service is not installed, click the Install button.

NOTE: To install the VDI host manually, refer to Installing the VDI Agent Manually section of this manual.

Click Next if the Agent is already installed.

VDI Agent Information

Farm 46

VDI Host Properties

Configure each VDI Host properties

To enable this host in the farm, make sure that the Enable Host in farm box is checked. In the VDI Type: field, select the VDI provider of the host and enter the version that you are using into the VDI Version field. To change the host name or IP address of a particular VDI host, use the VDI Host field. Enter port number in the VDI Port: field. Appliance settings can only be used with certain servers. Please refer to the list of approved providers and choose the specific document for more information on how to connect to your virtual host. To start using the new host, please enter the username and password of the host. If you would like to test the username and password before using, click on Check Credentials before clicking OK.

Farm 47

Agent Settings

Configure the VDI Agent Settings

To connect to the VDI Host directly check the Change Direct Address box. This address is used in Direct Connection mode only (this is an internal or external IP address) depending on where the clients will be. (If external, these IP addresses must be assigned at the firewall to your servers). Enter a Description so that the host can be easily identified. In the Max connections field, enter the maximum number of connections this host will accept. Publishing Session Timeout field is used to set the amount of time that each session will stay connected in the background after the user has closed all published applications. This is done to avoid unnecessary reconnections with the server. Checking the Allow Client URL/Mail Redirection box allows http and mailto links to be opened using local applications instead of using terminal server resources. Logging allows the server to log actions that occur on the server; basically used to identify any issues related to the server. Click on Request Log to download a copy of the log file. You can clear the servers log file by clicking Clear Log File. To be able to download or clear the log file, the 2X Terminal Server Agent must be running in debug mode.

NOTE: It will be necessary to install 2X VDI Agent on all VDI Hosts before they can successfully participate in a load-balanced farm.

Farm 48

RDP Printer Tab

RDP Printer Tab






Farm 49

Check Remove session number from printer name to remove the session number from printer name.

Printer Settings with Redirected Printer

Check Remove client name from printer name to enable that feature.


Farm 50

Scheduler Tab

Scheduler Tab

Using the Scheduler, you can configure your virtual server to not accept connections between set times.

To add a Scheduler Entry simply click Add and enter the date and time you want to restrict access to the terminal server.

Farm 51

Add Scheduler Entry

The Duration field accepts time in days, hours, minutes, seconds or any combination. Example: 3 days,, 5 hours, 45 minutes, 30 seconds. The Repeat field allows you to repeat the scheduled entry. The Scheduler tab will be available when editing the terminal servers properties. The On disable field allows you to choose the action taken on the current sessions by 2X ApplicationServer once a terminal server is disabled while a scheduled entry is active.

Edit a Virtual Host To edit the configuration of each host, select the particular host and click the Properties button. You can also double-click on each host to edit its configuration.

Delete a Virtual Host

To delete a host from the farm, select the particular host and click the Delete button. You can also use the Delete key from the keyboard instead of using the Delete button.

Farm 52

Check Agent

Once you have finished adding your Virtual Desktop Hosts, select a virtual host and click the Check Agent button. If the 2X Publishing Agent can communicate with the 2X VDI Agent running on the host, you will receive this message:

2X VDI Agent verified by Check Agent

NOTE: Make sure that the 2X VDI Agent is installed on each Virtual Desktop Host added to the farm. 2X VDI Agent will collect the information required by the 2X Publishing Agent to load balance each session according to available resources.

Farm 53

VDI Virtual Guests Settings

To view the Virtual Guests connected to the selected Virtual Desktop Server click on Virtual Guests Settings From here you can start, stop, suspend or reset any of the Virtual Guests connected to the server.

Virtual Guest List

The above example shows a particular Guest in a Suspended state. The only option available is to Start the service.

In the example below, the selected Guest is in a Powered On state, so the options are to Stop, Suspend or Reset.

Farm 54

To view the advanced settings of the a selected Virtual Guest, click on Properties....

Virtual Guest Advanced Settings

Enable Do not use this guest checkbox so the system ignores the particular Virtual Guest.

The Computer Name field allows you to set the network name (domain name / IP address) of the computer that the system will use to connect to the Virtual Guest.

The Port field contains the port number that the system will use to connect to the Virtual Guest.

Use the Connection Timeout field to set a time limit on attempts a 2X ApplicationServer can connect to the particular Virtual Guest.

Protocol is the method used for 2X ApplicationServer to communicate with the Virtual Guest.

You can set what actions the guest will take if a user disconnects from a session by choosing an option from the If session disconnects drop down list. You can choose the amount of time that needs to pass before the selected action is taken.

A session can be terminated after the user disconnects from the session. You can choose the amount of time that needs to pass before the disconnected session is terminated. The user can reconnect to a previous session if that session is still available.

Farm 55

Pool Management

Pools offer administrators more flexibility when managing an extensive number of Guests, especially when they are implemented in large company infrastructures. 2X ApplicationServer console provides the framework and tools needed to create a complete Pool Management foundation.

To add a Pool to your farm click the green + symbol and then enter the Pool name.

To delete a Pool, click on the Pool in the Name list and then click on the red - symbol.

Pool Management Tab

The Default Pool includes all Guests in the farm.

Farm 56

Adding Pool Members to a Pool

Select the Pool that you want to add Members to and then click on the Add... button.

Adding Guests to a Pool

Choose from the following types of Guests:

All Guests in Farm: All guests that are located in the farm..

All Guests in Host: All guests that are located on a particular host.

Guest: A single guest located in the farm.

Native Pool: Group of guests that have been previously configured from the hypervisor management tool. Please note that the hypervisor may use different terminology instead of pools (e.g. resource pools)

2X Template: Guests that are automatically created from a 2X Template.

Wildcard Function

The Wildcard field is used to match specific guests from any available guests within a pool. Select the guests from the list and add to your Pool. Use the asterisk ( * ) symbol to match any characters.

For example, XP* will find only guests whose name starts with XP and *XP* will find guests with XP in their name.

Farm 57

Delete a Pool Member

Select the Pool member you want removed and click on Delete. The selected Guest is then deleted from that Pool.

Pool Guests

The Pool Guests button allows you to view and manage Guests in a particular Pool. Select a Pool and the Guests that are included in that Pool appear in the Virtual Guests List.

Click on the Refresh button to view new additions to the Pool list.

Click on a Guest in a Pool and then click on Clear Settings

Virtual Guests List

Choose a Guest from the Virtual Guests List and click on Check Agent to verify that the Guest Agent is installed.

Farm 58

Select a Guest within a Pool and click on Properties.

Guest Advanced Settings

The Guest Advanced Settings dialog box appears and you can further configure each Guest in the Pool.

Enable Do not use this guest checkbox so the system ignores the particular Virtual Guest.

The Computer Name field allows you to set the network name (domain name / IP address) of the computer that the system will use to connect to the Virtual Guest.

The Port field contains the port number that the system will use to connect to the Virtual Guest.

Use the Connection Timeout field to set a time limit on attempts a 2X ApplicationServer can connect to the particular Virtual Guest.

Protocol is the method used for 2X ApplicationServer to communicate with the Virtual Guest.

You can set what actions the guest will take if a user disconnects from a session by choosing an option from the If session disconnects drop down list. You can choose the amount of time that needs to pass before the selected action is taken.

A session can be terminated after the user disconnects from the session. You can choose the amount of time that needs to pass before the disconnected session is terminated. The user can reconnect to a previous session if that session is still available.

Farm 59

2X Templates With the aid of 2X Templates you can better utilize host resources. 2X Templates allows you to automatically create and deploy Guest VMs when needed. To create a 2X Template, click on the 2X Templates tab and then click on Add

Creating a 2X Template

The Virtual Guests List dialog box appears. Select a Guest that will be designated as a 2X Template, then click on OK.

Adding a 2X Template

Farm 60

Once you have selected which guest you will be converting to a 2X Template, the Guest Agent Information dialog box appears containing all the information that is associated with that particular Guest.

Creating a 2X Template

If the agent is not verified or installed, you can install it by clicking the install button. The Guest Agent makes it possible to create new clones, use universal printing and scanning.

Installing 2X Guest Agent

Farm 61

After the Guest Agent has been installed a new dialog box appears showing the updated Guest Agent information. Click Make Template to create a 2X Template.

Guest Agent Information

2X Templates Information button

Given that clones are created from the templates, it is possible to view information about the clones created from the templates by clicking Info

Farm 62

Template Guests Lists Information If the Guest Agent needs to be updated, you can do it from this window.

Maintenance Mode If there is the need to update the template OS, you need to put the template into Maintenance Mode. In the mode the OS can be booted and modified, Once the desired changes have been applied you can put the template off Maintenance Mode. This is required when you need to: install Operating System service packs, install new software, or uninstall current packages. During maintenance mode, clones cannot be created from the guest, and the entry from the 2X Templates in Farm becomes greyed out.

2X Templates List

NOTE: When maintenance mode is applied on a template, this will only effect newly created VMs. Any VMs already created, are not effected.

Farm 63

2X Template Properties Select a 2X Template from the list and then click on Properties. The 2X Template Properties dialog box opens. Properties Tab

Properties Tab

2X Template: Enter a descriptive name for the 2X Template or re-name existing templates. Maximum Guests: The maximum number of guests that can be created. Pre-created Guests: Enter the number of guests that will be pre-created so that users will find a desktop ready without having to wait for the cloning process to finish. Guest Name: Enter the Guest Name. Please note that each guest name is appended with the guest ID. If you dont want to allocate space on the server for Guests that are not in use, enable the Check the Delete unused guests checkbox and set the time limit if you would like the guests that are not being utilized deleted.

Farm 64

Advanced Tab

Advanced Tab HyperV templates

The Folder field is the location where the newly created guests (created from the 2X Template by ApplicationServer) will be created.

This folder feature is available for Hyper-V, Parallels Server4, Citrix Xen and VCenter .

If the hypervisor you are using supports Native Pools, then the newly created Guests will be part of the specified Native Pool: location. VmWare ESX, VmWare VCenter and VmWare Server 2 support Native Pools.

Farm 65

Sys Prep Tab The SysPrep tab contains settings you need to be able to join your Guest to either a workgroup or a domain.

SysPrep Tab

Computer Name: Enter the computer name that will be using the 2X Template guest. Owner Name: Enter the user or owner name of the user that will be using the 2X Template guest. Organization: Enter your organizations name Administrative password: Enter the administrator password. Join workgroup: Select this option if the guest will be part of a workgroup. Enter the workgroup name in the field provided. Join domain: Select this option if the guest will be part of the domain. Enter the appropriate information such as the domain name and the administrative credentials.

Farm 66

License Keys Tab The License Keys tab allows you to add the licensing information of the Guests operating system.

License Keys Tab

Add License Key

Click on Add and the Add License Key dialog box appears. Enter the License key information and the maximum number of guests that will be using the license.

Farm 67

Persistent Guests

When a published application from a guest is set as persistent, the first time a user launches the application, the publishing agent will create a persistent guest rule. Below is the list of rules that the publishing agent preserves. The publishing agent will always connect the user to the same guest when the persistent rule is used.

The Persistent Guests can be viewed and managed on this tab. The information that is provided includes the Guest name, Host IP address, the last time this guest was used, when the persistent guest rule was created and the state of the persistent rule. Click on the headings and you can choose to show or hide any of the column headings.

Persistent Guest Rules

Click on the Refresh button to view new additions to the Persistent Guests list. To delete a persistent guest entry, select and click on Delete. To delete all the existing persistent guests in the list, click on Delete All. Choose to automatically remove persistence if the guest is not used for the specified amount of time. Choose from 24 hours, 1 day, 1 week or 30 days.

Farm 68

Remote PCs

With Remote PCs, a physical machines desktop can be published (after it is added to the Farm). This will enable 2X Clients connected to 2X ApplicationServer to open RDP connections directly to a physical computer as opposed to a virtual desktop or a terminal server session. Automatically search for available Remote PCs within your domain by clicking the Find button or click on the Add button to add a Remote PCs.

Remote PCs

NOTE: The checkbox next to the PC name indicates that the particular PC is available to users on this farm. To disable a PC temporarily, uncheck the box.

Farm 69

Find Remote PCs

Click the Find button to automatically search for available Personal Computers.

Find available Remote PCs

All available PCs within your domain will appear in the list of personal computers in your farm. The Agent status is identified and the MAC address is also listed. To add a PC to the farm, enable the checkbox in front of the PC name. Click the OK button to save changes. Click on Install Agent if the remote PCs agent is not found or needs to be installed

Farm 70

Add /Delete Remote PCs

To add a PC to your farm click the Add button. Enter the remote PCs name or IP address.

Enter the MAC address or simply click on the Get MAC address button to add the MAC identification.

Add an available Remote PCs

Delete Remote PCs

To delete a Remote PC, select it and click on the Delete button. You can also use the Delete key from the keyboard instead of using the Delete button.

Farm 71

Edit a Remote PC

To edit a Remote PC, select a remote pc from the list and click on Properties. Or double click on a remote pc in the list and the properties dialog box opens.

Remote PC Properties

Properties Tab

Make sure that Enable Remote PC box is checked so the new Remote PC is enabled in your Farm.

In the Remote PC field, you can enter or edit the name of the remote pc.

Enter the MAC Address of the PC you would like to add. Use the Get MAC button, if you are adding your local machine, to easily get the MAC Address.

Note: The MAC Address is needed if you want to use the Wake on LAN feature. When running a published PC desktop from the 2X Client, you will need the MAC address to boot up a PC that may be switched off.

The Protocol field identifies the protocol used by the Remote PC.

A Description can be given which can be used to easily identify different Remote PC;s from one another.

Farm 72

Agent Settings Tab

The Port field contains the port number that the system will use to connect to the Remote PC.

You can configure the direct address by checking the Change Direct Address box and entering a new direct address. This address is used in Direct Connection mode only. This can be an internal or external IP address; depending where the clients will be.

If external, the IP address must be assigned at your firewall to your servers.

Agent Settings Tab

2X ApplicationServer is able to wake a PC by sending a packet over the network. This will continue until the receipt of the packet is acknowledged or until the connection is timed out. In the Connection Timeout field, choose a connection time-out.

The Publishing Session Timeout field allows you to designate a time before the publishing session times out conserving system resources.

Checking the Allow Client URL/Mail Redirection box allows http and mailto links to be opened using local applications instead of using terminal server resources.

Farm 73

RDP Printer Tab






You can also remove the session number and the client name from the printer name by enabling each of the corresponding checkboxes. Examples are shown below.

Farm 74

Printer Settings with Client Name and Session Number


Farm 75

Gateways

The 2X Console can manage all the 2X Secure Client Gateways on the Farm and will list them in the Gateways section. The 2X Secure Client Gateway can also be remotely installed on a server. Any 2X Secure Client Gateways connected to a 2X Publishing Agent will be automatically added and listed as Auto Discovered.

2X Secure Client Gateways

Farm 76

Installing the 2X Secure Client Gateway Remotely from the 2X Console Click on the Install button to start installing 2X Secure Client Gateway.

In the Server field, enter the name of the machine that will be used as a 2X Secure Client Gateway or browse for available machines on the network. Click Resolve to retrieve the IP address of the machine. The Mode field has two options, Normal and Forwarding. If the 2X Secure Client Gateway is configured to be a forwarding gateway, all the connections will be forwarded to the next 2X Secure Client Gateway. You can choose to forward connections to any 2X Secure Client Gateway that has been already added to the Farm.

Adding a 2X Secure Client Gateway

Farm 77

Before installing the 2X Secure Client Gateway, you can choose to override the system credentials that will be used for authentication. Click Install to start installing the 2X SecureClientGateway service on the remote server.

Installing 2X Secure Client Gateway

NOTE: In order to install the 2X Secure Client Gateway, select Custom in the Installation Type and check the 2X Secure Client Gateway option. Please refer to Installing 2X ApplicationServer for more information on how to install the 2X Secure Client Gateway.

Farm 78

2X Secure Client Gateway Properties

The properties of any 2X Secure Client Gateway available in the farm can be edited from the 2X Console. Click on the 2X Secure Client Gateway you want to edit and click on Properties

Properties Tab

2X Secure Client Gateway Properties

From the Properties tab, you can enable or disable the 2X Secure Client Gateway in the farm. The server name and the IP address of the server can be edited on the properties tab. Enter a brief description to easily identify the 2X Secure Client Gateway.

NOTE: The Server and IP(s) fields can not be edited if the 2X Secure Client Gateway is installed locally.

Farm 79

Network Tab

2X Secure Client Gateway Port (default TCP 80) is used to tunnel all 2X traffic. The traffic that is tunneled through this port include the 2X Publishing Agent traffic (load balanced application and desktop publishing), HTTP Server and RDP traffic. The 2X Secure Client Gateway Port can also be used to tunnel secure connections (SSL).

RDP Port (default TCP 3389) is used for clients who require basic load balanced desktop sessions. Connections on this port do not support published items.

If terminal services are enabled on the machine where the 2X SecureClientGateway is installed, the RDP Port should not be the same as the one for the standard RDP (3389).

Citrix Port (default TCP 1494) is used for the incoming Citrix connections which will be forwarded to the configured Citrix servers according to the load balancing configuration. To disable this service, uncheck the box in front of Citrix Port. Enable the Broadcast 2X Secure Client Gateway Address checkbox to broadcast the 2X Secure Client Gateway address, so that 2X Clients will be able to auto find their primary server (2X Secure Client Gateway address).

2X Secure Client Gateway network settings.

Enable Thin Client Support to allow thin clients on the network to connect to 2X ApplicationServer. This will enable the Thin Client devices to download a version of 2XOS and install it on the Thin Client or to Network Boot 2XOS. The Client Heart Beat Server Port is used to obtain Thin Client states (see section Devices States). You can change the TFTP timeout if you are experiencing timeouts while downloading the OS files. TFTP port is used to transfer the 2XOS from the server to the client. When you enable the DHCP Proxy the system will allow the 2XOS to discover the TFTP server on the network. If you disable DHCP proxy, you must manually setup your DHCP server with the boot server name and bootfile name. Please note that gateways set in forwarding mode do not support Thin Clients.

Farm 80

Advanced Tab

Advanced 2X Secure Client Gateway Settings

Gateway Mode

From the Advanced settings you can configure the operation mode of the gateway. You can choose between Normal mode and Forwarding mode. In the Normal mode all requests are forwarded to the 2X Publishing agent and to the HTTP Server configured. You can add backup servers with the main server in use. In the Forwarding mode all requests are forwarded to the next 2X Secure Client Gateway in the Chain, this is normally used where cascading Firewalls are found.

When the gateway is set in forwarding mode the following considerations have to be followed:

NOTE: All ports must be the same on each 2X Secure Client Gateway. Therefore, if a 2X Secure Client Gateway on server A is listening on port 80 and is configured to forward the requests to 2X Secure Client Gateway on server B, server B should be configured to listen on port 80. This also applies for the Citrix port (default 1494) and SSL (default 443). NOTE: In order to install 2X Secure Client Gateway, select Custom in the Installation Type and check the 2X Secure Client Gateway option. Please refer to the chapter entitled Installing 2X ApplicationServer for more information about how to install the 2X Secure Client Gateway.

Farm 81

NOTE: If you have problems starting the service, check the Log File and Event Viewer for more information. Please note that if the configured 2X Secure Client Gateway port is assigned with another service, the 2X Secure Client Gateway Service will not be able to start the service. In this case you must either configure the default port (80) to another port or configure the other service to use another port. NOTE: Users will not be able to connect through the gateway if this service is stopped. All connections running through 2X Secure Client Gateway Service will be dropped if the service is stopped or restarted.

IP Address

It is also possible to bind the Gateway with a certain IP address. This feature provides the Administrator with the ability to open the 2X Secure Client Gateway for certain IP address instead of opening 2X Secure Client Gateway on all available addresses.

Bind Gateway to an IP Address

Farm 82

You can optimize the connection for selected IP Addresses to improve the experience of clients which have high latency or slow connections. This has most effect when an RDP connection uses large amounts of data. It is suggested that for internal connection this option is not used.

To configure connection optimization, click the button adjacent to the Optimize connection for the following IPs: field, and the following window is shown.

You can optimize the connection from one of the following options:

All available addresses Connection coming from any IP address will be optimized.

Specific addresses Connections coming from the IP addresses selected from the list will be optimized.

None from the available No connections from the available IP addresses will be optimized.

Enabling the RDP DOS Attack Filter checkbox protects the Gateway from Denial of Service.

Farm 83

SSL/TLS Tab

SSL/TLS Configuration

You can enable Secure Sockets Layer (SSL). In SSL mode, the 2X Secure Client Gateway provides end-to-end SSL encryption to your terminal servers. If you want your clients to connect to the 2X Secure Client Gateway using SSL, check Enable SSL on Port: checkbox. The port number used for SSL connections can be changed. By default, 2X ApplicationServer allows both SSL v2 and SSL v3. You can choose to only allow the use of SSL v3 by enabling Allow only SSL v3 checkbox. Enable the Allow only strong ciphers checkbox to set the gateway to a medium to high level of encryption.

Farm 84

To use SSL and secure the connection, you must enter a Private Key file and a Certificate file. You can use your own or simply click on Generate new certificate to create them.

Enter your information and the FQDN of your 2X ApplicationServer (Common name) and click Save.

Generate New Certificate

NOTE: If clients are not able to connect with port 443 because of firewalls or other policies, they could also use the 2X Secure Client Gateway port (default 80) to connect using SSL.

2X Secure Client Gateway offers the ability to tunnel SSL traffic over port 80.

Generating Certificate Requests

2X Application Server XG offers the possibility to automatically create Certificate Signing Requests (CSR).This helps the Administrators to purchase the correct SSL certificate by providing the correct information.

1. To generate Certificate Signing Requests first you need to enable SSL in the 2X

Secure Client Gateway Properties from the SSL/TLS Configuration window shown above.

2. Press the button Generate certificate request and the following window will pop

up.

Farm 85

Generating New Certificate Requests

3. Select the Key size for the certificate request.

4. Insert the information required into the text boxes as shown above.

5. After inserting all the necessary information, click Save and note that the Certificate

Request is generated as shown below.

View Certificate Request

6. The generated information for the Certificate Request is shown above.

NOTE: You can copy the information to be sent to the Certificate Authority so that the correct certificate is purchased by clicking the Copy button. NOTE: You can cancel the certificate request by clicking the Cancel Request button.

Farm 86

Importing the Public Key

The button Import public key becomes enabled after generating the certificate request.

SSL/TLS Configuration Import public key enabled

To Import the Public Key provided from the Certificate Authority, Click the Import public key and browse for the certificate file containing the public key. After pressing Open the certificate file is read successfully and the name is shown in the Certificate file: read only text box. Press OK after importing the certificate file.

Farm 87

Security

The security tab allows you to filter connections through your gateway by matching MAC addresses. Administrators are able to block out MAC addresses or allow only the specified entries to run published applications.

Security Tab

There are two options to choose from:

Allow all users except the specified MAC addresses, or:

Allow only the specified MAC addresses. To allow all MAC addresses except the address specified, then select Allow all except: radio button and click on Add

Farm 88

A list of Available clients will appear. Select which client you do not want to allow access to published applications.

You can select any one of the listed MAC addresses or type in a MAC address, and click OK.

Allow all except dialog

As provided by the example below, the selected machine is not allowed to connect and run published applications.

Security Tab with added filtered users

To allow only the selected MAC addresses select Allow only and then click Add

Farm 89

Security Tab

Select one of the listed MAC addresses or type in a pre known MAC address, and click OK.

Allow Only Dialog

Farm 90

Security Tab with added filtered users

Now as you can see in the above dialog box, only one machine is allowed to run published applications.

Farm 91

Wyse

If you are using Wyse ThinClient OS and want to publish applications from 2X ApplicationServer, check the Enable Wyse ThinOS Support box.

The 2X Secure Client Gateway will then act as a Wyse broker.

Wyse Tab for ThinOS Support

Click the Test button to verify your DHCP Server settings. 2X suggests that you enable SSL on this gateway when you enable Wyse ThinOS Support.

Farm 92

Backup Servers

You can add, find and configure the properties of all Backup Servers on the Farm so that if the Master server fails, the next server in the list will take over.

The backup servers can also be used as additional 2X Secure Client Gateways to evenly distribute the load on each gateway.

MS Terminal Server

2X Terminal Server Agent

MS Terminal Server


MS Terminal Server


MS Terminal Server


Windows Machine

2X SecureClientGateway (port 80)

2X Publishing Agent

SSL Enabled over port 80/443

Windows Machine

2X Backup Publishing Agent

Redundant ApplicationServer

Backup Servers

Farm 93

Adding 2X Backup Servers

To add 2X Backup Servers click the Find button. A new dialog will show the available servers in the local domain which can be used as Backup Servers.

Find 2X Backup Servers

When the state of the selected server is Agent Not Found it means that the 2X Publishing Agent is not installed on the selected server. Therefore you would need to install this service. If you choose a backup server that does not have the agent installed, the Take Over button changes to the Install Agent button. If a 2X Publishing Agent is already in use it means that the particular server is already configured as a master server in another farm. Taking over this server will override any settings currently configured on the particular machine.

Farm 94

Installing 2X Backup Server

Enter administrative credentials to be able to install the 2X Publishing Agent on the selected server which will be used as a backup server.

Click Install or Take Over after youve entered the administrative credentials. You should note that the service has been installed successfully if the installation is completed. Click Done when finished. When 2X Publishing Agent is already in use one can Take Over the server and use it as a backup server.

Farm 95

You can also use the Add button to manually add 2X Backup Server. Enter the name or the IP address of the server to be used as a backup server and click Next.

Add 2X Backup Server

A status information message will guide you on what to do next. Most often you will have to install the 2X Backup Server by clicking the Install button. Then proceed with the following dialog boxes If an older version of the 2X Backup Server is already installed you would have to update the server by clicking the Update button.

2X Backup Server Properties

NOTE: The Install button changes according to the status of the selected server. It will change to Update if an older version of the 2X Backup Server is found, while it will change to Take Over if the selected server is already configured with a 2X Publishing Agent configured as the master server.

Farm 96

Modifying 2X Backup Servers

To change the properties of each backup server, select the particular server and click Properties. You can enable or disable the selected backup server and you can also install, update or uninstall the backup server from the properties dialog box. To delete a particular backup server, select the required server from the Backup Servers list and click Delete. Each backup server in the list is given a priority. By default the local 2X Publishing Agent is given the Master priority and this cannot be changed. You can change the priority of the backup server. To assign a higher priority in the backup list select the required backup server from the list and click Move up. To assign a lower priority in the backup list select the required backup server from the list and click Move Down. The Backup Server with priority configured as Backup Server 1 will be the first backup server to take over in case the Master Server is not available. Additional backup servers will take over in case Backup Server 1 is also not available according to their priority.

Promoting a Backup server to Master Server

When the primary server cannot be recovered due to various reasons such as hardware failure or OS startup failure, you can easily promote a 2X Backup Server to a Master server. First launch the 2X Console located on the backup server. NOTE: When you add and install 2X Backup Servers, all the required files are automatically installed remotely on each backup server. Therefore to launch the 2X Console of a backup server, you can easily launch the 2X Console located at: C:\Program Files\2X\ApplicationServer\2XConsole.exe.

Farm 97

Promote a 2X Backup Server to a Master

Secondly, click Promote to Master button to promote the current backup server as a Master Server. Promotion to a Master server requires a reactivation of the products which is done automatically and requires an Internet connection. The 2X Terminal Server Agents will use this server (previously used as a 2X Backup server) as the new Master server.

Solution Guide

The 2X Server Based Computing Guide will help you find the tailor-made solution for your company's IT infrastructure. Click here for a complete list of scenarios and more information on server based computing.

Load Balancing 98

LOAD BALANCING

Load Balancing

To configure the 2X LoadBalancer, click on Load Balancing in the Navigation bar in the 2X Console. On the Load Balancing tab you can choose the load balancing method to be used, which counters to be used for the selected method and you can choose to enable a reconnection to a disconnected session or reconnect to same user sessions.

Configure load balancing properties

Resource Based Load Balancing: in this method, 2X LoadBalancer will retrieve the load information for all terminal servers in the farm and, based on the counters chosen, will determine the terminal server that will handle the incoming connection. Three different counters are available: Round Robin Load Balancing: in this method, 2X LoadBalancer will identify the next available terminal server and forward the incoming connection accordingly, regardless of available resources on the server.

Load Balancing 99

Counters

User Sessions: This option will redirect users to the server with the least number of sessions in use.

Memory: This option will redirect users to the server with the best free/used RAM ratio.

CPU Utilization: This option will redirect users to the server with the best free/used CPU time ratio. If more than one option is selected for load balancing, the 2X LoadBalancer will add the counter ratios together, and redirect the session to the server with the most favorable combined ratio. The recommended setting is to enable all three options, unless there is a particular need for one of the options available. NOTE: It will be necessary to install 2X Terminal Server Agent on all terminal servers and Citrix servers and/or 2X VDI Agent on all Virtual Desktop Hosts before each server can successfully participate in a load-balanced farm. The Reconnect to disconnected sessions option allows the 2X Publishing Agent to redirect an incoming user session to a previously disconnected session owned by the same user. The Reconnect sessions using clients IP address only checkbox will need to be checked if reconnect is by IP address. You may also choose to reconnect active sessions by selecting Limit User to one session per desktop. Therefore if a user re-connects to a Terminal Server with an active session started by the same user, the user will be connected to the active session.

NOTE: To limit users to one session per desktop, make sure that the setting Restrict each user to one session is enabled at Terminal Servers>Terminal Services>configurations>Connections.

Load Balancing 100

Advanced Settings

Click on the Configure button. You can change the default timeouts for the Terminal Server Agents. In normal scenarios, you should use the default settings

Advanced Load Balancer Settings

Declare TS Agent dead This option is the amount of time that the 2X Publishing Agent should wait for each 2X Terminal Server Agent before declaring that particular Agent as dead. TS Agent Refresh Time This option is the amount of time that the 2X Publishing Agent should re-check the connection with each 2X Terminal Server Agent. Enable CPU Load Balancer The CPU Load Balancer setting plays an important role in the 2X Terminal Server Agent. When enabled it controls the processes that are using the most CPU resources. The 2X Terminal Server Agent is given a High base priority. If the terminal server CPU resources begin to exceed 95%, the processes that are using the most CPU resources are given a low priority, yet all other applications continue to operate normally.

Click on the Exclude List button and another dialog box will open that allows you to add Processes that will be excluded from load balancing.

Load Balancing 101

Tunneling Policies

On the Tunneling Policies tab you can set specific filters so that native RDP & ICA connections can be redirected to specific terminal server(s). Load balancing rules are useful when assigning a group of terminal servers or a specific terminal server with a 2X Secure Client Gateway IP. Therefore connections initiated from that particular IP will be load balanced to a corresponding group or a particular terminal server.

NOTE: Load Balancing Rules are applicable only to non-published desktop sessions.

Tunneling Policies Tab

Default Rule

The rule is pre-configured as the last rule which will catch all non configured gateway IPs. By default, this rule is configured to load balance the sessions between all servers in the farm. However, you can change the properties of this rule by selecting the default rule and clicking on Properties.

Load Balancing 102

Add a New Rule To add a native RDP & ICA Load Balancing Rule, click the Add button. This will open a new dialog as shown below. First select the IP Address for which you would like to create the rule, then choose All Servers in Farm, Server Groups, Individual Server or None.

Rules Properties

All Servers in Farm All connections initiated through this interface will be load balanced between all servers in the farm. One should note that the default rule is already pre-configured to load balance native RDP & ICA sessions between all servers in the farm. Server Groups All connections initiated through this interface will be load balanced with the selected group. One can select one or more groups to be associated with this interface as shown

2 x application server

Documents