2XApplication Server XG v10.1

(1)

(2)

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.

(3)

I

NTRODUCTION

What is 2X ApplicationServer and How Does it Work?

2X ApplicationServer is an application that provides vendor independent virtual desktops and applications. Accessible from anywhere. 2X

ApplicationServer allows you to publish full desktops and applications within a virtual environment, improving desktop manageability, security and performance.

2X ApplicationServer extends Windows Terminal Services by using a customized shell and virtual channel applications using the Microsoft RDP protocol.

2X ApplicationServer supports a number of different technologies, including Microsoft Terminal Server , VMware, Oracle VirtualBox, Microsoft Virtual Server, Microsoft Hyper-V, Virtual Iron, and Parallels, to allow the publishing of virtual applications and desktops to the 2X Client. Virtual objects are load balanced over all available machines while automatically releasing unused resources.

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.

(7)

2X ApplicationServer System Requirements

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

2X Terminal Server Agent must be installed on Windows

2008/R2Server/Enterprise Server with Terminal Services enabled; Windows 2003 Server/Enterprise Server with Terminal Services enabled; Windows 2000 Server/Advanced Server with Terminal Services enabled.

2X Client is approved for the following operating systems: Windows 2000, Windows 2003, Windows XP, Windows Vista, Windows 7, Windows CE, Windows Embedded, Mac 10.5.x and above. 2X Client is now available for iOS (iPhone and iPad) and for Android.

The 2X Client is also approved for the following 32-bit Linux distributions: Ubuntu 8.04, Ubuntu 8.10, Ubuntu 9.04, Ubuntu 9.10, OpenSuse 11.1, Fedora Core 9, Fedora Core 11, CentOs 5.2, VectorLinux 6.0.

(8)

Installing 2X ApplicationServer• 8

I

NSTALLING

2X

A

PPLICATION

S

ERVER

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

(9)

The License Agreement.

(10)

Choose Your Installation type Setup Wizard installs 2X ApplicationServer

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

(11)

(12)

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

(13)

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.

(14)

Connection Settings

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

Logon Settings Tab

Logon Settings

(15)

Environment Tab

Environment

(16)

Configuring 2X ApplicationServer• 16

C

ONFIGURING

2X

A

PPLICATION

S

ERVER

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:

(17)

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

(18)

Console Environment

Console Environment/Publishing

1

1 .

.

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.

2

2 .

.

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

3

3 .

.

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.

4

4 .

.

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.

5

(19)

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.

(20)

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.

(21)

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.

(22)

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.

(23)

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.

(24)

2X Startup Wizard• 24

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

(25)

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.

(26)

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.

(27)

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

(28)

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

(29)

F

ARM

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 PC‟s, Terminal Servers, VDI Hosts, VDI Pools and 2X Templates (not shown) in the information panel.

(30)

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 (See section „Add a Terminal Server‟)

 VDI Host  Remote PC  Gateway  Backup Server

(31)

The Infrastructure design may be printed by clicking ‘Print’ button in the header. Doing so would pop up the following window:

2X Farm Design - Print

Adjust the printing parameters accordingly. Select the „Printer‟ you would like to print from. Finally press OK to print.

If the „Printer‟ button is not available (as shown in the following screenshot below), press Ok and the Infrastructure design will be printed on the default printer.

(32)

Farm• 32

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

(33)

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.

(34)

Farm• 34

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

(35)

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

(36)

Farm• 36

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.

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.

(37)

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:

(38)

Farm• 38 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.

(39)

Scheduler Tab

Scheduler

(40)

Farm• 40 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.

(41)

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

(42)

Farm• 42

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

(43)

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

(44)

Farm• 44 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.

(45)

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.

(46)

Farm• 46

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 server‟s 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.

(47)

RDP Printer Tab

RDP Printer Tab

(48)

Farm• 48 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.

(49)

Scheduler Tab

Scheduler Tab

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

(50)

Farm• 50 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 server‟s 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

(51)

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’

(52)

Farm• 52

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.

(53)

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.

(54)

Farm• 54

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

(55)

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.

(56)

Farm• 56

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

(57)

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.

(58)

Farm• 58

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.

(59)

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

(60)

Farm• 60 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

(61)

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.

(62)

Farm• 62

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.

(63)

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.

(64)

Farm• 64

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 organization‟s 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

(65)

License Keys Tab

The License Keys tab allows you to add the licensing information of the Guest‟s operating system.

License Keys Tab

(66)

Farm• 66

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‟.

(67)

Remote PCs

With Remote PCs, a physical machine‟s 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 PC’s

(68)

Farm• 68

Find Remote PC’s

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

Find available Remote PCs

All available PC‟s 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.

(69)

Add /Delete Remote PC’s

To add a PC to your farm click the ‘Add…‟ button. Enter the remote PC‟s name or IP address.

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

(70)

Farm• 70

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.

(71)

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.

(72)

Farm• 72

RDP Printer Tab

 P

rintername (from Computername) in Session no.

 S

ession no. (computername from) Printername

 P

rintername (redirected Session no)

(73)

Printer Settings with Client Name and Session Number

(74)

Farm• 74

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‟.

(75)

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.

(76)

Farm• 76 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

(77)

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.

(78)

Farm• 78

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 is also 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.

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.

NOTE: If terminal services are enabled on the machine where the 2X SecureClientGateway is installed, the RDP Port cannot be used.

Enable Thin Client PXE booting to allow thin clients on the network to connect to 2X ApplicationServer to boot. This will enable the thin client user to download a version of 2X ThinClientOS and install it on the thin client. You can set the TFTP Port and TFTP timeout. TFTP is used to transfer the 2X ThinClientOS from the server to the client.

(79)

Advanced Tab

2X Secure Client Gateway tunnels all 2X traffic needed by 2X applications on a single port. This gateway service gives the System Administrator the ability to tunnel the Terminal Servers (RDP), HTTP Server (81) and 2X Publishing (20002) over one port which by default is configured to port 80.

To configure the Advanced 2X Secure Client Gateway Setting, you‟ll need to assign a port number in the „2X Secure Client Gateway port‟ which by default is configured to port 80 (make sure that this port is not being used by another service) and then select the „Advanced’ tab (shown below) to configure the HTTP Server, and 2X Publishing Agent.

Advanced 2X Secure Client Gateway Settings

(80)

Farm• 80

Advanced 2X Secure Client Gateway (Multiple 2X Secure Client Gateways)

2X offers the solution of installing multiple 2X Secure Client Gateways. These solutions offer quite a bit of flexibility to Administrators.

As displayed in the diagram below, both 2X Secure Client Gateways are configured to forward requests to the same 2X Publishing Agent.

MS Terminal Server 2X Terminal Server Agent

2X Publishing Agent LAN WAN / INTERNET 2X SecureClientGateway Public 2X SecureClientGateway Private

(81)

The Advanced tab is where you can configure each 2X Secure Client Gateway and configure the 2X Publishing Agent.

Advanced 2X Secure Client Gateway Settings

(82)

Farm• 82 The first publishing agent in the Servers list will be used by default. In the event that the first

2X Publishing Agent fails to respond, the next 2X Publishing Agent will be used.

NOTE: 2X Terminal Server Agents cannot be assigned to multiple 2X Publishing Agents. Therefore each 2X Publishing Agent should have a unique group of terminal servers. For more advanced and alternative scenarios and solutions please read 2X Server Based

Computing Guide.

Advanced 2X Secure Client Gateway (Forwarding Mode)

2X Secure Client Gateway can forward requests to the next 2X Secure Client Gateway in the chain (Cascading Firewall).

With this option enabled the 2X Secure Client Gateway installed on this machine [GATEWAY 1] (port:80 by default) will forward the requests to the next 2X Secure Client Gateway

[GATEWAY 2] configured in the 'Forwarding 2X Secure Client Gateway(s) list.

WAN / INTENRET

LAN

MS Windows Machine 2X SecureClientGateway SSL Enabled (443/80) MS Windows Machine 2X Publishing Agent 2X SecureClientGateway SSL Enabled (443/80) GATEWAY 2 GATEWAY 1

(83)

Forwarding requests to next 2X Secure Client Gateway in chain

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.

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.

(84)

Farm• 84

Bind Gateway to an IP Address

On the Advanced tab in the 2X Secure Client Gateway settings, 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 port (default port 80) for certain IP address instead of opening 2X Secure Client Gateway port on all available addresses.

Enabling the ‘RDP DOS Attack Filter’ checkbox protects the Gateway from „Denial of Service‟.

(85)

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.

(86)

Farm• 86 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.

(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.

(88)

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

(89)

Security Tab

(90)

Farm• 90 Security Tab with added filtered users

(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

(92)

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 Windows Machine

2X SecureClientGateway (port 80) 2X Publishing Agent SSL Enabled over port 80/443

Windows Machine 2X Backup Publishing Agent

Redundant ApplicationServer

(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.

(94)

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 you‟ve entered the administrative credentials. You should note that the service has been installed successfully if the installation is completed. Click „Done’ when finished.

(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

(96)

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

(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

(98)

Load Balancing• 98

L

OAD

B

ALANCING

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

(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 client’s 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

(100)

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.

(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

2XApplication Server XG v10.1

Contents

Introduction

6

Installing 2X ApplicationServer

8

Configuring 2X ApplicationServer

16

2X Startup Wizard

23

Farm

29

Load Balancing

98

Publishing

104

2X Universal Printing

153

2X Universal Scanning

156

Connection Settings

159

Client

169

Information

177

Reporting

185

Licensing

189

Available 2X Clients

191

Installing the 2X Terminal Server Agent Manually

192

Installing the 2X Gateway Manually

203

Installing the 2X Guest Agent Manually

208

Installing the 2X PC Agent Manually

213

2X Additional Utilities

218

Features

220

Troubleshooting and Support

223

I

NTRODUCTION

What is 2X ApplicationServer and How Does it Work?

How Does it Work?

2X ApplicationServer System Requirements

I

NSTALLING

2X

A

PPLICATION

S

ERVER

2X ApplicationServer Services

Pre- Configuration MS Terminal Server Settings

Server Settings

Connection Settings

Logon Settings Tab

Environment Tab

C

ONFIGURING

2X

A

PPLICATION

S

ERVER

Introduction to the Configuration of ApplicationServer

2X ApplicationServer Console Environment & Components

Components of the Navigation Bar











