The Farm category is offered in all the installation option. The difference is that in the Small to Medium Business Edition you can only use one (1) server and in Enterprise Edition and 2X VirtualDesktopServer you can add multiple Terminal Servers or Citrix Servers or Virtual Hosts (only in 2X VirtualDesktopServer) to the farm. Small to Medium Business Edition does not support Citrix Servers.

Figure 37 – Terminal Server Tab – Small to Medium Business Edition

To change the Server name or IP address of a particular Terminal Server use the ‘Server’ field.

Next you can type the maximum number of sessions you want this server to accept. You also have to specify the RDP port that will be used to connect a session.

In the RDP settings one can configure the direct address by checking ‘Change Direct Address’ checkbox and type a new direct address. This address is used in Direct Connection mode only (this is an internal or external IP address) depending where the clients will be. If external, these IP address must be assigned at your firewall to your servers).

Figure 38 – Printer Settings with Redirected Printer

2X ApplicationServer offers the feature to remover either the client name, session number or both. This is done by checking “Remove session number from printer name” and “Remove client name from printer name”.

Figure 39 – Printer Settings with Redirected Printer, Removed Client Name and Session Number

You can also check the agent status through the Terminal Server tab. This is used to check out your agent information. You can accomplish this by clicking the “Check Agent” button. A dialog with the agent information will pop up.

Figure 40 – Agent Information Dialog

The publishing session timeout is the amount of time that each session will stay connected in the background after the user has closed all the published applications before disconnecting from the server. This is done to avoid unnecessary reconnection with the server.

One can also choose to allow URL/Mail redirection on the client. This option provides that ability that http and mailto links will be opened using local applications instead of using the resources on the Terminal Server.

The security feature provided is that to only allow 2X ApplictaionServer Clients to connect to the server, this will switch off RDP and only allow 2X ApplicationServer Client connections. You can enable security by checking the “Allow only 2X ApplicationServer Client to connect to this server.

The advanced settings let you change the default timeouts for the Terminal Server Agents, to access the advanced settings just click “Advanced...”

This option is the amount of time that the 2X Publishing Agent should wait without a reply from each 2X Terminal Server Agent before declaring that particular Agent as dead.

This option is the amount of time that the 2X Publishing Agent should re-check the connection with each 2X Terminal Server Agent.

The CPU Load Balancer has an important role in the 2X Terminal Server Agent as when enabled it can control those processes that are using the most CPU. This can be done as the 2X Terminal Server Agent (2XAgent.exe) is given a High base priority and when the Terminal Server CPU exceeds 95%, the process that is using most CPU is given a low priority. With this option enabled, when the CPU is over 95%, other sessions and other applications will continue to operate normally.

In 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 manually add the Terminal Servers or Citrix Servers.

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

Click the ‘Find...’ button to automatically search for available Terminal Servers and Citrix 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 commit changes.

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

To manually 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 & LoadBalancer will check whether 2X Terminal Server Agent is installed. Check the status and if the status states that the Agent did not reply or service is not installed, click the ‘Install...’ button. Please refer to the chapter entitled “Installing the 2X Terminal Server Agent remotely from 2X Console” - for more information about how to install the 2X Terminal Server Agent.

Click ‘Add’ if the status states that the Agent is already installed.

To edit the configuration of each Server, select the particular Server and click the ‘Properties...’ button. You can also double click each Server to edit its configuration.

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.

Next you can type the maximum number of sessions you want this server to accept. To enable this server in the farm, make sure that ‘Enable Server in farm’ checkbox is checked.

Default RDP port is 3389, however this port can be changed according to the actual RDP port of the configured Terminal Server. This port will be used by the 2X Client Gateway when a connection is created in a gateway mode. This port may also be used from the clients directly if the connection is created in a direct mode.

In the RDP settings one can configure the direct address by checking ‘Change Direct Address’ checkbox and type a new direct address. This address is used in Direct Connection mode only (this is an internal or external IP address) depending where the clients will be. If external, these IP address must be assigned at your firewall to your servers).

The publishing session timeout is the amount of time that each session will stay connected in the background after the user has closed all the published applications before disconnecting from the server. This is done to avoid unnecessary reconnection with the server.

One can also choose to allow URL/Mail redirection on the client. This option provides that ability that http and mailto links will be opened using local applications instead of using the resources on the Terminal Server.

Figure 48 – Printer Settings with Redirected Printer

When redirecting a printer to be used with a published application, the name of the printer in the printer properties will show as the printer name, client name and session number.

2X ApplicationServer offers the feature to remover either the client name, session number or both. This is done by checking “Remove session number from printer name” and “Remove client name from printer name”.

Figure 49 – Printer Settings with Redirected Printer, Removed Client Name and Session Number

In the ICA Settings, one can change the ICA port which by default would be listening on port 1494.

When finished click ‘OK’.

To delete a 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.

Once you have finished adding your Terminal Servers or Citrix Servers select a terminal server (one at a time) and click the ‘Check Agent’ button. If the 2X Publishing Agent can communicate with the 2X Terminal Server Agent running on the Terminal Server, you will receive this message:

NOTE: Make sure that 2X Terminal Server Agent is installed on each Terminal Server added to the farm. 2X Terminal Server Agent collects the information required by 2X Publishing Agent to be able to load balance each session according to available resources.

To organize your Terminal Servers in groups, click the ‘Add...’ button in the Server Groups Panel. Type the name that you want to give to the new group and select the Terminal Servers which are going to be bind within 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 whole farm. Therefore you can group the MS Terminal Servers which hosts that particular application and then select that group in the ‘Publish From’ tab when publishing applications. One can also use groups to configure specific filters so that connections to non published desktops can be redirected to specific groups (please refer to Advanced Load balancing section for more information).

Delegation will allow users that are not administrators to access 2X console and have just enough rights to publish applications.

To add users to the delegation list, simply click “Add...”

In the above example user1, user2 and user3 now have rights to publish applications.

NOTE: The user that is added to delegation needs write access to HKEY_LOCAL_MACHINE\SOFTWARE\2X.

The security page allows you to filter connections through your gateway by matching MAC addresses. It is possible to block out MAC addressed or else only allow the specified entries to run published applications.

There are two (2) options that you can use; the first is to allow all users except the specified MAC addresses, or the second were you only allow the specified MAC addresses.

To allow all MAC addresses except the specified ones, select “Allow all except”, and then click “Add...”

You can select any 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 2 machines are not allowed to connect and run published applications.

Figure 58 – Security Tab with added filtered users

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

Figure 59 – Allow Only Dialog

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

Figure 60 – Security Tab with added filtered users

Now as you can see in the above dialog only the 2 specified machines are allowed to run published applications.

In 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 manually add the Terminal Servers or Citrix Servers.

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

Click the ‘Find...’ button to automatically search for available Terminal Servers and Citrix 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 commit changes.

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

To manually 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 VirtualDesktopServer will check whether 2X Terminal Server Agent is installed. Check the status and if the status states that the Agent did not reply or service is not installed, click the ‘Install...’ button. Please refer to the chapter entitled “Installing the 2X Terminal Server Agent remotely from 2X Console” - for more information about how to install the 2X Terminal Server Agent.

Click ‘Add’ if the status states that the Agent is already installed.

To edit the configuration of each Server, select the particular Server and click the ‘Properties...’ button. You can also double click each Server to edit its configuration.

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.

Next you can type the maximum number of sessions you want this server to accept. To enable this server in the farm, make sure that ‘Enable Server in farm’ checkbox is checked.

Default RDP port is 3389, however this port can be changed according to the actual RDP port of the configured Terminal Server. This port will be used by the 2X Client Gateway when a connection is created in a gateway mode. This port may also be used from the clients directly if the connection is created in a direct mode.

In the RDP settings one can configure the direct address by checking ‘Change Direct Address’ checkbox and type a new direct address. This address is used in Direct Connection mode only (this is an internal or external IP address) depending where the clients will be. If external, these IP address must be assigned at your firewall to your servers).

The publishing session timeout is the amount of time that each session will stay connected in the background after the user has closed all the published applications before disconnecting from the server. This is done to avoid unnecessary reconnection with the server.

One can also choose to allow URL/Mail redirection on the client. This option provides that ability that http and mailto links will be opened using local applications instead of using the resources on the Terminal Server.

Figure 48 – Printer Settings with Redirected Printer

When redirecting a printer to be used with a published application, the name of the printer in the printer properties will show as the printer name, client name and session number.

2X ApplicationServer offers the feature to remover either the client name, session number or both. This is done by checking “Remove session number from printer name” and “Remove client name from printer name”.

Figure 49 – Printer Settings with Redirected Printer, Removed Client Name and Session Number

In the ICA Settings, one can change the ICA port which by default would be listening on port 1494.

When finished click ‘OK’.

To delete a 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.

Once you have finished adding your Terminal Servers or Citrix Servers select a terminal server (one at a time) and click the ‘Check Agent’ button. If the 2X Publishing Agent can communicate with the 2X Terminal Server Agent running on the Terminal Server, you will receive this message:

NOTE: Make sure that 2X Terminal Server Agent is installed on each Terminal Server added to the farm. 2X Terminal Server Agent collects the information required by 2X Publishing Agent to be able to load balance each session according to available resources.

To organize your Terminal Servers in groups, click the ‘Add...’ button in the Server Groups Panel. Type the name that you want to give to the new group and select the Terminal Servers which are going to be bind within 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 whole farm. Therefore you can group the MS Terminal Servers which hosts that particular application and then select that group in the ‘Publish From’ tab when publishing applications. One can also use groups to configure specific filters so that connections to non published desktops can be redirected to specific groups (please refer to Advanced Load balancing section for more information).

In this page you can add VDS Hosts (VMWare, Microsoft Virtual Server, Virtual Box). You have two options to add Servers to the farm. You can either automatically search for available VDS Hosts within your domain by clicking the ‘Find...’ button or you can click on the ‘Add...’ button to manually add the VDS Hosts.

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

Click the ‘Find...’ button to automatically search for available Virtual Hosts.

All Virtual Hosts within your domain will appear on the list of available servers to your farm, also identifying host type. To add a server to the farm, enable the checkbox in front of the server name. Click the ‘OK’ button to commit changes.

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

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

2X VirtualDesktopServer will check whether 2X VDS Agent is installed. Check the status and if the status states that the Agent did not reply or service is not installed, click the ‘Install...’ button. Please refer to the chapter entitled “Installing the 2X VDS Agent remotely from 2X Console” for more information about how to install the 2X VDS Agent.

Click ‘Add’ if the status states that the Agent is already installed.

To edit the configuration of each Host, select the particular Host and click the ‘Properties...’ button. You can also double click each Host to edit its configuration.

To change the Host name or IP address of a particular VDS Host use the ‘Machine’ field. Select the VDI provider of the Host from the ‘Type’ field and the version that you are using.

Next you can type the maximum number of guests you want this host to accept. To enable this host in the farm, make sure that ‘Enable Host in farm’ checkbox is checked.

One can configure the direct address by checking ‘Change Direct Address’ checkbox and type a new direct address. This address is used in Direct Connection mode only (this is an internal or external IP address) depending where the clients will be. If external, these IP address must be assigned at your firewall to your servers).

To start using the new host, please enter the username and password of the host. Click on ‘Check Credentials’ if you would like to test the username and password before clicking ‘OK’.

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.

Once you have finished adding your Virtual Desktop Hosts select a terminal server (one at a time) and click the ‘Check Agent’ button. If the 2X Publishing Agent can communicate with the 2X VDS Agent running on the Host, you will receive this message:

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

To organize your Hosts in groups, click the 'Add...' button in the Host Groups Panel. Type the name that you want to give to the new group and select the Hosts which are going to be used within that group.

Host Groups are useful when you want to publish a virtual desktop which is located on a number of VDS Hosts but not in the whole farm. Therefore when publishing a virtual desktop you can select the group of VDS Hosts which may hosts the virtual desktop from the 'Publish From' tab.

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

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

Enable ‘Do not use this guest’ for the system to ignore 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 will contain the port number that the system will use to connect to the Virtual Guest.

The ‘Connection Timeout’ is the time limit set on the attempt for the 2X VirtualDesktopServer to connect to the particular Virtual Guest.

‘Protocol’ is the method use for 2X VirtualDesktopServer to communicate with the Virtual Guest.

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

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

Delegation will allow users that are not administrators to access 2X Console and have just enough rights to publish virtual desktops.

To add users to the delegation list, simply click “Add...”

In the above example user1, user2 and user3 now have rights to publish applications.

NOTE: The user that is added to delegation needs write access to HKEY_LOCAL_MACHINE\SOFTWARE\2X.

The security page allows you to filter connections through your gateway by matching MAC addresses. It is possible to block out MAC addressed or else only allow the specified entries to run published applications.

There are two (2) options that you can use; the first is to allow all users except the specified MAC addresses, or the second were you only allow the specified MAC addresses.

To allow all MAC addresses except the specified ones, select “Allow all except”, and then click “Add...”

You can select any 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 2 machines are not allowed to connect and run published applications.

Figure 58 – Security Tab with added filtered users

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

Figure 59 – Allow Only Dialog

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

Figure 60 – Security Tab with added filtered users

Now as you can see in the above dialog only the 2 specified machines are allowed to run published applications.

Farm

Farm – ASLB Small to Medium Business Edition

Terminal Server

Properties

Status

Advanced

Publish Settings

Security

Advanced

Declare TS Agent dead.

TS Agent Refresh Time

Enable CPU Load Balancer

Farm – ASLB Enterprise Edition

Terminal Servers

Find

Add /Edit/Delete

Server Properties

RDP Settings

ICA Settings

Check Agent

Server Groups

Delegation

Security

Farm – VDS Edition

Terminal Servers

Find

Add /Edit/Delete

Server Properties

RDP Settings

ICA Settings

Check Agent

Server Groups

Virtual Hosts

Find

Add /Edit/Delete

Host Properties

Check Agent

Host Groups

Virtual Guests

Delegation

Security