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.

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.

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

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

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.

Find a Terminal Server

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.

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

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.

Click ‘Add’ if the Agent is already installed.

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

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.

Agent Settings Tab

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:

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.

‘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 server’s 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.

RDP Printer Tab

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:

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

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

Scheduler Tab

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.

The Scheduler tab will be available when editing the terminal server’s 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.

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.

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.

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.

Find a VDI Host

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.

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.

Click ‘Next’ to continue.

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

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.

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.

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

RDP Printer Tab

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:

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.

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

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.

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:

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.

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.

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.

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

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.

The ‘Default’ Pool includes all Guests in the farm.

Adding Pool Members to a Pool

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

Choose from the following types of Guests:

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.

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’

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

Select a Guest within a Pool and click on Properties.

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

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

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

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.

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

2X Template Properties

If you don’t 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.

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 information such as the domain name and the administrative credentials.

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.

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.

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.

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.

Find Remote PC’s

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.

Click on ‘Install Agent’ if the remote PC’s agent is not found or needs to be installed

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.

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.

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.

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.

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.

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.

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:

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.

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

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.

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.

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

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.

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

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

Enable Thin Client Support to allow thin clients on the network to connect to 2X ApplicationServer. This will enable the Thin Client user 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 set the TFTP timeout. TFTP port is used to transfer the 2XOS from the server to the client. DHCP Proxy 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.

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.

This Advanced dialog allows you configure the locations of the HTTP server(s) and the 2X Publishing Agent.

If the services are running on other Servers, you will need to configure each setting with the corresponding IP address or computer name.

(i.e. HTTP Server: webserver.internal.mycompany:81)

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.

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

You can add additional 2X Publishing Agents by separating them with a semi colon or click on the drop down arrow ‘

’ which will allow you to add more 2X Publishing Agents as displayed in the figure below.

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.

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.

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.

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

SSL/TLS Tab

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.

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.

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.

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.

Importing the Public Key

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

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.

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.

There are two options to choose from:

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

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

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

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

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

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.

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.

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.

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.

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.

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.

When 2X Publishing Agent is already in use one can ‘Take Over’ the server and use it as a backup server.

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

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.

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.

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

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.

Farm

Farm Info Tab

Farm Design Tab

Terminal Servers

Find a Terminal Server

Add a Terminal Server

Editing a Terminal Server

Properties Tab

Agent Settings Tab

RDP Printer Tab

Scheduler Tab

Delete a Terminal Server

Server Groups

VDI Hosts

Find a VDI Host

Add a VDI Host

VDI Host Properties

Agent Settings

RDP Printer Tab

Scheduler Tab

Edit a Virtual Host

Delete a Virtual Host

Check Agent

VDI Virtual Guests Settings

Pool Management

Adding Pool Members to a Pool

Wildcard Function

Delete a Pool Member

Pool Guests

2X Templates

Maintenance Mode

2X Template Properties

Persistent Guests

Remote PCs

Find Remote PC’s

Add /Delete Remote PC’s

Edit a Remote PC

Gateways

Installing the 2X Secure Client Gateway Remotely from the 2X Console

2X Secure Client Gateway Properties

Network Tab

Advanced Tab

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

Advanced 2X Secure Client Gateway (Forwarding Mode)

SSL/TLS Tab

Generating Certificate Requests

Importing the Public Key

Security

Backup Servers

Adding 2X Backup Servers

Modifying 2X Backup Servers

Promoting a Backup server to Master Server

Solution Guide