2X ApplicationServer & LoadBalancer & VirtualDesktopServer Manual 2X VirtualDesktopServer Contents • 1
URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of 2X SOFTWARE Ltd. 2X VirtualDesktopServer, 2X ApplicationServer and LoadBalancer are copyright of 2X SOFTWARE Ltd. 1999-2009 2X SOFTWARE Ltd.
Contents Introduction 6 What is 2X ApplicationServer & LoadBalancer? ............................................................ 6 What is 2X VirtualDesktopServer?................................................................................. 6 Features ......................................................................................................................... 6 How does 2X ApplicationServer work? ..........................................................................
Terminal Servers ............................................................................................. 57 Gateway .......................................................................................................... 68 Backup Servers ............................................................................................... 78 Farm – VDS Edition ..................................................................................................... 84 Terminal Servers .........................
Installing the 2X Client silently ................................................................................... 187 Using Active Directory ................................................................................... 187 Detailed explanation of 2X Client options ..................................................... 189 Using ORCA to change the MSI ................................................................... 199 Using 2X Client for Windows 201 Introduction ..............................
INTRODUCTION What is 2X ApplicationServer & LoadBalancer? 2X ApplicationServer & LoadBalancer Console is an easy-to-use centralized GUI Application that allows configuration of 2X ApplicationServer and 2X LoadBalancer.
Native RDP Connections Using the 2X VirtualDesktopServer Client you can now connected to a machine running Microsoft Terminal Server using a Remote Desktop Protocol connection. Administrators can easily configure desktop connections and publish applications using one tool. Embedded Desktops With your 2X VirtualDesktopServer Client you can now use Embedded Desktops. This allows you to load a number of different Virtual Desktops inside one application.
Increased Terminal Services performance During the login sequence, the user (using default settings) connection request is forwarded to the terminal server reporting the best performance index. This ensures that the users will never be connected to a terminal server that is using all its resources (CPU, memory, etc), optimizing user experience across the terminal server farm. Enhanced Security When used in SSL Gateway mode, the 2X LoadBalancer provides end-to-end SSL encryption to your terminal servers.
How does 2X ApplicationServer work? 2X ApplicationServer extends Windows Terminal Services by using a customized shell and virtual channel applications using the Microsoft RDP protocol. Due to these extensions, a new Client is required (although it uses the same RDP protocol as mentioned above) on all computers that will be accessing the 2X ApplicationServer.
INSTALLING 2X VIRTUALDESKTOPSERVER 2X ApplicationServer & LoadBalancer & VirtualDesktopServer System requirements Windows 2000 Server, 2003 Server or 2008 Server or Advanced Server with Terminal Services enabled (in Application Mode if using Windows 2000 Server) when publishing applications and load balancing Terminal Servers. The same hardware requirements as specified by Microsoft when deploying a terminal server apply.
Figure 1 - 2X VirtualDesktopServer Setup Program welcome screen. 2. Accept the license agreement by enabling ‘I accept the terms in the License Agreement’ checkbox. Figure 2 - The License Agreement.
3. Select the location where you want to install the 2X VirtualDesktopServer and click ‘Next’. Figure 3 - Choosing the location where 2X VirtualDesktopServer will be installed. 4. Select the desired installation type. You can select either ‘2X VirtualDesktopServer’ or ‘2X ApplicationServer and LoadBalancer Enterprise’ or ‘2X ApplicationServer and LoadBalancer SMB’ (Small to Medium Business) or ‘Custom’.
4.1 Small to Medium Business Edition For a single terminal server just select the ‘Small to Medium Business Edition’ radio button and this feature will install all necessary components to publish application and desktops from a Single Terminal Server. This scenario is typically used when you have one Terminal Server and you need to offer published, seamless applications to your clients. Figure 4 - Single Terminal Server scenario to publish applications and desktops from a single Terminal Server.
4.2 Enterprise Edition Figure 6 - Installation type – Enterprise Edition You have to choose what to install according to your needs and your requirements. Two common scenarios are the ‘regular gateway scenario’ and the ‘direct mode scenario’. Please follow the below instructions how to setup such scenarios (4.2.1 or 4.2.2). For more advanced and alternative scenarios and solutions please read 2X Server Based Computing Guide.
Explanation of 2X Components 2X VirtualDesktopServer – Consists of 2X Publishing Agent service and 2X Management Console.* The service provides load balanced applications and desktop publishing. 2X Terminal Server Agent – Consists of 2X Terminal Server Agent service and 2X shell component. The service collects resource information from the Terminal Server(s) and forwards the information to the 2X LoadBalancer. 2X Client Gateway – Consists of 2X Client Gateway service and 2X Management Console.
4.2.1 Enterprise Edition (Custom Installation) – Regular Gateway Scenario This solution is ideal for secure environments. Clients can connect using Gateway with the 2X Client Gateway machine. This machine will listen for RDP and will forward traffic to the MS Terminal Server according to their load status. Figure 7 - Enterprise Edition - Multiple Terminal Servers - Regular Gateway Scenario (4.2.
A regular gateway solution is ideally used when you require a server to act as a load balancer which will only listen for RDP and forward traffic to the MS Terminal Server according to their load status. For this you will need to select ‘2X Publishing Agent’ and ‘2X Client Gateway’ only. Figure 8 - Installation type – Custom (Regular Gateway scenario) On each Terminal Server you need to install the 2X Terminal Server Agent.
4.2.2 Enterprise Edition (Custom Installation) – Direct Mode Scenario This solution is ideal for LAN environments. Clients can connect using the direct mode with any MS Terminal Server. Clients will first ask the 2X Publishing Agent for the best available Terminal Server and they will connect directly to the preferred MS Terminal Server. Figure 9 - Enterprise Edition – Multiple Terminal Servers - Direct Mode Scenario (4.2.
In this scenario you would need to select ‘2X Publishing Agent’, ‘2X Terminal Server Agent’ and ‘2X Client Gateway’ if this server is going to act as a terminal server. Figure 10 - Installation type – Custom (Direct Mode Solution) For the additional Terminal Servers, you would need to select ‘2X Terminal Server Agent’ only. You may also install the 2X Terminal Server Agents remotely from 2X Console.
4. Important Notice about 2X Client Gateway tunneling. (applicable only when 2X Client Gateway is installed) To be able to tunnel all traffic through port 80, make sure that other services like web servers are running on another port (e.g. 81). You will be able to tunnel web traffic to local host (e.g. 81) by changing the 2X Client Gateway port in the ‘Connection Settings’ page.
6. Click ‘Install’ to begin the installation - Setup will copy the required files and will create the service on the machine. Figure 12 - Ready to install 2X VirtualDesktopServer 7. After the 2X VirtualDesktopServer is installed, you should see the 2X Client Gateway, 2X Publishing Agent, 2X Redundancy Service, 2X Terminal Server Agent and 2X VDI Agent services listed under ‘Services’. However this depends on which components you have installed.
INSTALLING THE 2X TERMINAL SERVER AGENT 2X Terminal Server Agent System requirements • Windows 2000 Server, 2003 Server or 2008 Server or Advanced Server with Terminal Services enabled (in Application Mode if using Windows 2000 Server). • The same hardware requirements as specified by Microsoft when deploying a terminal services environment will apply.
1. Launch the 2X VirtualDesktopServer Console and select the Terminal Servers category. If 2X VirtualDesktopServer Console detects that a number of Terminal Server Agents are not installed or need to be upgraded, it will inform you and allow you to install/update them all at once. Figure 14 - Terminal Server page to add additional Terminal Server agents 2. Click the ‘Find…’ button to find the available Terminal Servers or Citrix Servers.
Figure 15 - Choose a Terminal Server to install agent 3. Select the Terminal Server where you would like to install the 2X Terminal Server Agent and click ‘Install Agent’. 4. Enter administrative credentials to access the remote server.
5. Click ‘Install’ after you’ve entered the administrative credentials. You should note that service is installed successfully if the installation is done completely. Figure 17 - 2X Terminal Server agent Installation process 6. Click ‘Done’ when finished. Installing the 2X Terminal Server Agent Manually Before starting the installation procedure, please make sure that you are logged on with administrator rights, and that the system requirements are met. 1.
Figure 18 - 2X Terminal Server Agent Setup Program welcome screen.
3. Accept the License Agreement and click ‘Next’. Figure 19 - The EULA. 4. Select the location where you want to install the 2X Terminal Server Agent and click ‘Next’. Figure 20 - Choosing the location where 2X Terminal Server Agent will be installed.
5. First select the ‘Custom’ radio button as the Installation type. Figure 21 - Select Installation type: Custom. 6. Select ‘2X Terminal Server Agent’ only as shown in the figure below and click ‘Next’. Figure 22 - Select Installation type: Custom - 2X Terminal Server Agent.
7. To start the actual installation process, simply click ‘Install’. Figure 23 - Starting the installation program. 8. Setup will copy the required files and will create the service on the machine. After finishing you will see the status screen. Figure 24 - Post-Installation status screen.
After the installation is complete (remotely or manual), you should see the ‘2X Terminal Server Agent’ service listed under ‘Services’ on the server where the agent has been installed. Figure 25 -The 2X Terminal Server Agent Service NOTE: The terminal servers do not require configuration. The agent will collect the information required by the 2X Publishing Agent. Subsequently, the 2X Terminal Server Agent will forward the necessary information to the 2X Publishing Agent using the information collected.
INSTALLING THE 2X VDI AGENT 2X VDI Agent System requirements • Windows XP, Windows Vista, Windows 2000 Server, Windows 2003 Server or Windows 2008 Server or Advanced Server. • The same hardware requirements as specified by your virtualization software will apply. • One of the supported virtualization software technology. • If you are planning to use VMware on Windows, make sure the VMware VmCOM Scripting API is installed.
1. Launch the 2X VirtualDesktopServer Console and select the Virtual Desktop Hosts tab. Figure 27 - Virtual Hosts page to add VDI Agents 2. You can use a similar method to that of installing the 2X Terminal Server Agent or you can click on ‘Check Agent’ where a new dialog will load showing you the information about the 2X VDI Agent on the host you selected. Figure 28 - 2X VDI Agent Information 3. Click ‘Install’ to start installing the 2X VDI Agent on the selected host. 4.
Figure 29 - Enter administrative credentials to install the 2X VDI Agent 5. Click ‘Install’ after you’ve administrative credentials. checked and possibly entered the 6. Click ‘Done’ when finished. Installing the 2X VDI Agent Manually Before starting the installation procedure, please make sure that you are logged on with administrator rights, and that the system requirements are met. 1. Log on to the Virtual Host 2. Run the 2X VirtualDesktopServer setup program by double clicking on the ‘2XVDS.
Figure 30 - 2X VirtualDesktopServer Setup Program welcome screen. 3. Accept the License Agreement and click ‘Next’ Figure 31 - The EULA. 4. Select the location where you want to install the 2X VDI Agent and click ‘Next’.
Figure 32 - Choosing the location where 2X VDI Agent will be installed. 5. First select the ‘Custom’ radio button as the Installation type. Figure 33 - Select Installation type: Custom. 6. Select ‘2X VDI Agent’ only as shown in the figure below and click ‘Next’.
Figure 34 - Select only the 2X VDI Agent for installation. 7. To start the actual installation process, simply click ‘Install’. Figure 35 - Starting the installation program. 8. Setup will copy the required files and will create the service on the machine. After finishing you will see the status screen.
Figure 36 - Post-Installation status screen. After the installation is complete (remotely or manual), you should see the ‘2X VDI Agent’ service listed under ‘Services’ on the server where the agent has been installed. Figure 37 - The 2X VDI Agent Service NOTE: The Virtual Desktop Hosts do not require configuration. The agent will collect the information required by the 2X Publishing Agent.
Figure 38 - Checking for 2X VDI Agent on a Virtual Desktop Host.
CONFIGURING 2X VIRTUALDESKTOPSERVER Introduction to the configuration After you have installed 2X VirtualDesktopServer Console, you can now launch the Console GUI and further configure it. If you have installed 2X ApplicationServer & LoadBalancer use the following instructions to configure it. You might not see certain options concerning the Virtual Desktop Infrastructure which are only available with the 2X VirtualDesktopServer installation.
Understanding the Console Environment The 2X VirtualDesktopServer Console is a completely self-contained environment for publishing seamless applications, load balancing published desktop sessions, load balancing seamless applications, and load balancing Virtual Desktop Hosts, Terminal Server and/or Citrix sessions. Components of the System Farm In this page you can add Virtual Desktop Hosts, Microsoft Terminal Servers and Citrix Servers to the farm.
Console Environment – Publishing page Figure 40 - Console Environment The area to the left in above figure is the Navigation Bar, the right area shows the Published Applications Properties, the area in between represents the Published Applications Explorer while the area at the bottom represents the Publishing Tools. 41 • Configuring 2X VirtualDesktopServer The Navigation Bar enables you to navigate through the main features offered by 2X VirtualDesktopServer Console.
this are you also have the possibility to publish your applications to the web. 2X VirtualDesktopServer 2X VirtualDesktopServer • 42 The Toolbar consists of a set of tools grouped together to provide quick and convenient access to commonlyperformed operations.
Console Environment – Farm, Load Balancing, Universal Printing, Connection Settings, Information and Licensing pages. Figure 41 - Console Environment – Farm, Load Balancing, Universal Printing, Connection Settings, Information and Licensing pages The area to the left in the above figure is the Navigation Bar, the right area show the Information Pane, while the area in between represents the Properties Pane.
Main 2X VirtualDesktopServer Console Settings Backup & Restore 2X VirtualDesktopServer gives you the ability to backup and restore the configuration. The entire configuration is saved to a ‘.dat’ file in XML format. This can be useful to backup the configuration or distribute the same settings across other 2X Consoles. Figure 42 - File – Import Settings and Export Settings To backup settings – Click File and ‘Export Settings…’ and save the .dat file in a safe place.
View The View Menu enables you to navigate through the main features offered by 2X VirtualDesktopServer Console. One can also choose to view or not to view the toolbar from this menu. Language To change the Language to your preferred language, click on ‘Language’ from the Main Menu. This function allows you to change the language that is displayed in your 2X Console interface. The default language will use the language that is configured in the Regional and Language Options.
Toolbar Settings To customize the toolbar, right click in the Toolbar area and select ‘Customize…’. One can customize the button and icon view according to his likes.
GENERAL TERMINAL SERVICES CONFIGURATION 2X VirtualDesktopServer Services To start, stop and configure 2X VirtualDesktopServer Services, run the Microsoft Management Console ‘Services.msc’. 2X VirtualDesktopServer services are configured to start automatically when the system starts. The services installed depend on the installation you selected.
MS Terminal Server settings With Terminal Services Configuration, you can reconfigure the properties of the RDP-TCP connection, which includes 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. Some connection properties can also be configured on a per-user basis using Terminal Services Group Policies or the Terminal Services extension to Local Users and Groups.
Logon Settings Figure 46 - Logon Settings Ensure your Terminal Server is set to NOT prompt for a password on the RDP-TCP listener otherwise clients will not be able to launch the applications using the credentials saved on the 2X Client, forcing unnecessary repeated authentication cycles. Select “Connections” and double-click the “RDP-TCP” option. In the “Logon Settings” tab make sure that the checkbox “Always prompt for password” is unchecked.
Environment Figure 47 - Environment To be able to launch the seamless published applications from the 2X VirtualDesktopServer, select “Connections” and double-click the “RDP-TCP” option. In the “Environment” tab make sure that the option “Run initial program specified by user profile and Remote Desktop Connection or Terminal Services Client” is ENABLED.
FARM 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.
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 addresses must be assigned at your firewall to your servers). Status You can also check the agent status through the Terminal Server tab. This is used to check out your agent information.
Advanced Figure 50 - Agent Information Dialog Publish Settings 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.
RDP Printer Figure 51 - Printer Settings with Redirected Printer Using the ‘RDP Printer Name Format’ you can choose the format of the printer name displayed on the Terminal Server. 2X VirtualDesktopServer offers the feature to remove 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 52 - Printer Settings with Redirected Printer, Removed Client Name and Session Number Advanced The advanced settings let you change the default timeouts for the Terminal Server Agents, to access the advanced settings just click “Advanced…” Figure 53 - Advanced Load Balancer Settings Declare TS Agent dead. 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.
TS Agent Refresh Time This option is the amount of time that the 2X Publishing Agent should recheck the connection with each 2X Terminal Server Agent. Enable CPU Load Balancer 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.
Farm – ASLB Enterprise Edition Terminal Servers 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.
Find Click the ‘Find…’ button to automatically search for available Terminal Servers and Citrix Servers. Figure 55 - 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.
Add a Terminal Server 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’. Figure 56 - Configure each server properties 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.
Edit a Terminal Server 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. Figure 58 - Terminal Server Tab – Small to Medium Business Edition Properties You can enable of 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.
RDP Settings Figure 59 - RDP Settings Enter 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 addresses must be assigned at your firewall to your servers).
Figure 60 - RDP Printer Settings Using the ‘RDP Printer Name Format’ you can choose the format of the printer name displayed on the Terminal Server. 2X VirtualDesktopServer offers the feature to remove 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 61 - Printer Settings with Redirected Printer Figure 62 - Printer Settings with Redirected Printer, Removed Client Name and Session Number 63 • Farm 2X VirtualDesktopServer
Scheduler Figure 63 - Scheduler Using the Scheduler, you can set your Terminal Server not to accept connections between a set time. To add a Scheduler Entry simply click ‘Add’ and then start by entering the date and time you want to restrict you Terminal Server. Select the duration of the schedule entry. The ‘Duration’ field accepts time in days, hours, minutes, seconds or any combination. Example: 3 days,, 5 hours, 45 minutes, 30 seconds. The entry can be set to be repeated.
The Scheduler tab will be available when editing the Terminal Server’s properties. ‘On disable’ will allow you to choose the action taken on the current sessions by 2X VirtualDesktopServer once a Terminal Server is disabled while a scheduled entry is active. NOTE: Make sure that 2X Terminal Server Agent is installed on each Terminal Server added to the farm.
Delegation Delegation will allow users that are not administrators to access 2X console and have just enough rights to publish applications.
Figure 68 - Delegation Tab with selected users 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.
Gateway In this page you may configure which port to use for 2X Client Gateway service while you may also enable or disable RDP and Citrix services. The 2X Client Gateway Port (default TCP 80) is used to tunnel all 2X traffic over this port. The traffic that can be tunneled through this port include the 2X Publishing Agent traffic (load balanced application and desktop publishing), HTTP Server and RDP traffic. 2X Client Gateway Port is also used to tunnel secure connections (SSL) over the same port.
NOTE: You can change the port to any number you may want, as long as it does NOT conflict with any other application using the same port you choose. Security 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.
Figure 71 - Allow all except dialog You can select any one of the listed MAC addresses or type in a pre known MAC address, and click “OK”. Figure 72 - Security Tab with added filtered users Now as you can see in the above dialog 2 machines are not allowed to connect and run published applications.
Figure 73 - Security Tab To allow only the selected MAC addresses select “Allow only” and then click “Add…” Figure 74 - 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 75 - 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. Advanced Client Gateway Settings 2X Client Gateway tunnels all 2X traffic needed by 2X applications on a single port. This gateway service gives the ability to the System Administrator to tunnel the Terminal Servers (RDP), HTTP Server (81) and 2X Publishing (20002) over one port which by default is configured to port 80.
This Advanced dialog allows you configure where is the HTTP server and the 2X Publishing Agent. These services may be running on other Servers, and in this case you’ll have to configure each setting with the correspondent IP address or computer name. E.g. HTTP Server: webserver.internal.mycompany:81 Advanced Client Gateway (Multiple 2X Client Gateways) 2X offers the solution to install multiple 2X Client Gateways.
Figure 78 - Advanced Client Gateway Settings One may also add additional 2X Publishing Agents by separating them with a semi colon or click on the drop down arrow ‘ ’ which will open up a new window to allow you to enter more 2X Publishing Agents as displayed in the figure below. Figure 79 - Add 2X Publishing Agents list 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.
Please refer to the chapter entitled “Installing 2X VirtualDesktopServer Console” for more information about how to install the 2X Client Gateway. Advanced Client Gateway (Forwarding Mode) 2X Client Gateway can forward requests to next Client Gateway in chain (Cascaded Firewall).
forward the requests to 2X 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 Client Gateway, select ‘Multiple Terminal Server’ in the Installation Type and check ‘2X Client Gateway’ option. Please refer to the chapter entitled “Installing 2X VirtualDesktopServer” for more information about how to install the 2X Client Gateway.
If you want your clients to connect to the 2X Client Gateway using SSL, make sure you click on ‘Use SSL’. In this case a certificate and private key must be provided. You can use your own or simply click on ‘Create a new certificate…’ to create them. Enter all your information and the FQDN of your 2X VirtualDesktopServer (Common name) and click ‘Generate new certificate…’.
Backup Servers In this page one can add Backup Servers so that if the Master server fails, the next server in the list takes over. The backup servers can also be used as additional Client Gateways to distribute the load on the gateways. Figure 84 - Redundant VirtualDesktopServer Figure 85 - Backup Servers Adding 2X Backup Servers 1. To add ‘2X Backup Servers’ click the ‘Find…’ button.
Backup Servers. Figure 86 - Find 2X Backup Servers 2. When the state of selected server is ‘Agent Not Found’ it means that 2X Publishing Agent is not installed on the selected server. Therefore you would need to install this service by clicking the ‘Install Agent…’ button. 3. Enter administrative credentials to be able to install the 2X Publishing Agent on the selected server which will be used as a backup server.
Figure 87 - Installing 2X Backup Server 4. Click ‘Install’ after you’ve entered the administrative credentials. You should note that service is installed successfully if the installation is done completely. 5. 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. NOTE: 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.
Figure 88 - Add 2X Backup Server A status information message will give you guide what to do next. Usually you’ll have to install the 2X Backup Server by clicking the ‘Install…’ button. Then proceed with steps 3 – 5 done in the previous section. If an old version of 2X backup server is already installed one would have to update the server by clicking the ‘Update’ button. Figure 89 - 2X Backup Server Properties NOTE: The ‘Install…’ button change according to the status of the selected server.
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. One 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 products but this is done automatically and it requires an Internet connection. Finally the 2X Terminal Server Agents will use this server (previously used as a 2X Backup server) as their Master server.
Farm – VDS Edition Terminal Servers 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.
Find a Terminal Server Click the ‘Find…’ button to automatically search for available Terminal Servers and Citrix Servers. Figure 92 - 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.
Add a Terminal Server 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’. Figure 93 - Configure each server properties 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.
Edit a Terminal Server 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. Figure 95 - Server Properties Properties You can enable of 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.
RDP Settings Figure 96 - RDP Settings Enter 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 addresses must be assigned at your firewall to your servers).
Figure 97 - RDP Printer Settings Using the ‘RDP Printer Name Format’ you can choose the format of the printer name displayed on the Terminal Server. 2X VirtualDesktopServer offers the feature to remove 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 98 - Printer Settings with Redirected Printer Figure 99 - Printer Settings with Redirected Printer, Removed Client Name and Session Number 2X VirtualDesktopServer Farm • 90
Scheduler Figure 100 - Scheduler Using the Scheduler, you can set your Terminal Server not to accept connections between a set time. To add a Scheduler Entry simply click ‘Add’ and then start by entering the date and time you want to restrict you Terminal Server. Select the duration of the schedule entry. The ‘Duration’ field accepts time in days, hours, minutes, seconds or any combination. Example: 3 days,, 5 hours, 45 minutes, 30 seconds. The entry can be set to be repeated.
Figure 101 - Add Scheduler Entry 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. 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.
Figure 102 - Group Properties 93 • Farm 2X VirtualDesktopServer
Virtual Hosts In this page you can add VDI Hosts (VMware, Microsoft Virtual Server, Sun VirtualBox, Virtual Iron). You have two ways to add Servers to the farm. You can either automatically search for available VDI Hosts within your domain by clicking the ‘Find…’ button or you can click on the ‘Add…’ button to manually add the VDI Hosts. Figure 103 - Add VDI Hosts to the farm –VDS Edition NOTE: The checkbox next to the server name indicates the particular server is available to users on this farm.
Find a Virtual Host Click the ‘Find…’ button to automatically search for available Virtual Hosts. Figure 104 - Find available VDI Hosts All Virtual Hosts within your domain will appear on the list of available servers to your farm, also identifying the host type. To add a server to the farm, enable the checkbox in front of the server name. Click the ‘OK’ button.
Figure 105 - Configure each Host properties Host Properties To enable this host in the farm, make sure that the ‘Enable Host in farm’ checkbox is checked. Select the VDI provider of the host from the ‘VDI Type’ field and the version that you are using from the ‘VDI Version’ field. To change the Host name or IP address of a particular VDI host, use the ‘VDI Host’ field. Appliance settings can only be used with certain servers.
Host Settings Figure 106 - Configure the VDI Agent Settings You 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 on where the clients will be. If external, these IP addresses must be assigned at your firewall to your servers). A ‘Description’ can be given to the host which can be used to easily identify different server from one another.
Add a Virtual Host To manually add a Host to your farm click the ‘Add…’ button and then choose a ‘VDI Type’ and 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.
Figure 108 - VDI Agent Information Figure 109 - Configure each Host properties Host Properties To enable this host in the farm, make sure that the ‘Enable Host in farm’ checkbox is checked.
Select the VDI provider of the host from the ‘VDI Type’ field and the version that you are using from the ‘VDI Version’ field. To change the Host name or IP address of a particular VDI host, use the ‘VDI Host’ 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.
A ‘Description’ can be given to the host which can be used to easily identify different server from one another. Next you can type the maximum number of powered-on guests you want this host to accept. 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 each Host to edit its configuration.
Figure 112 - Add Scheduler Entry The Scheduler tab will be available when editing the Terminal Server’s properties. ‘On disable’ will allow you to choose the action taken on the current sessions by 2X VirtualDesktopServer once a Terminal Server is disabled while a scheduled entry is active. 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.
NOTE: Make sure that 2X VDI Agent is installed on each Virtual Desktop Host added to the farm. 2X VDI Agent collects the information required by 2X Publishing Agent to be able to load balance each session according to available resources. Host Groups 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.
Figure 115 - Virtual Guest List To view the advanced settings of the selected Virtual Guest click on ‘Properties..’. Figure 116 - Virtual Guest Advanced Settings 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.
Personal Computers With PCs , a physical machine’s desktop can be published (after adding it to the Farm). This will enable 2X Clients connected to 2X VirtualDesktopServer to open RDP connections directly to a physical computer as opposed to a virtual desktop or a Terminal Server session. You can either automatically search for available PCs within your domain by clicking the ‘Find…’ button or you can click on the ‘Add…’ button to manually add the PCs.
Find Click the ‘Find…’ button to automatically search for available Personal Computers. 09 Figure 118 - Find available PCs All Personal Computers within your domain will appear on the list of available servers to your farm, also identifying the MAC Address. To add a PC to the farm, enable the checkbox in front of the PC name. Click the ‘OK’ button to commit changes.
Figure 119 - Configure the PC's properties Personal Computer Properties Make sure that ‘Enable Personal Computer’ is enabled if you want the new PC to be enabled in your Farm. Enter the name or IP of the PC you would like to add. The default RDP port is 3389 but you can change it to match the RDP port used by the PC. Enter the MAC Address of the PC you would like to add. Use the ‘Get MAC’ button, in case you are adding your local machine, to easily get the MAC Address of the machine you are using.
The ‘Test Wake on LAN’ button will send a packet to the selected PC. Make sure that the PC is on the same subnet as the 2X Publishing Agent. If the PC supports ‘Wake on LAN’ and the packet is successfully received, the PC will boot up. To edit the configuration of each PC, select the particular PC and click the ‘Properties…’ button. You can also double click each PC to edit its configuration. To delete a PC from the farm, select the particular PC and click the ‘Delete’ button.
Gateway In this page you may configure which port to use for 2X Client Gateway service while you may also enable or disable RDP and Citrix services. The 2X Client Gateway Port (default TCP 80) is used to tunnel all 2X traffic over this port. The traffic that can be tunneled through this port include the 2X Publishing Agent traffic (load balanced application and desktop publishing), HTTP Server and RDP traffic. 2X Client Gateway Port is also used to tunnel secure connections (SSL) over the same port.
NOTE: You can change the port to any number you may want, as long as it does NOT conflict with any other application using the same port you choose. Security 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.
Figure 122 - Allow all except dialog You can select any one of the listed MAC addresses or type in a pre known MAC address, and click “OK”. Figure 123 - Security Tab with added filtered users Now as you can see in the above dialog 2 machines are not allowed to connect and run published applications.
Figure 124 - Security Tab To allow only the selected MAC addresses select “Allow only” and then click “Add…” Figure 125 - 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 126 - 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. Advanced Client Gateway Settings 2X Client Gateway tunnels all 2X traffic needed by 2X applications on a single port. This gateway service gives the ability to the System Administrator to tunnel the Terminal Servers (RDP), HTTP Server (81) and 2X Publishing (20002) over one port which by default is configured to port 80.
This Advanced dialog allows you configure where is the HTTP server and the 2X Publishing Agent. These services may be running on other Servers, and in this case you’ll have to configure each setting with the correspondent IP address or computer name. E.g. HTTP Server: webserver.internal.mycompany:81 Advanced Client Gateway (Multiple 2X Client Gateways) 2X offers the solution to install multiple 2X Client Gateways.
Figure 129 - Advanced Client Gateway Settings One may also add additional 2X Publishing Agents by separating them with a semi colon or click on the drop down arrow ‘ ’ which will open up a new window to allow you to enter more 2X Publishing Agents as displayed in the figure below. Figure 130 - Add 2X Publishing Agents list 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.
Please refer to the chapter entitled “Installing 2X VirtualDesktopServer Console” for more information about how to install the 2X Client Gateway. Advanced Client Gateway (Forwarding Mode) 2X Client Gateway can forward requests to next Client Gateway in chain (Cascaded Firewall).
forward the requests to 2X 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 Client Gateway, select ‘Multiple Terminal Server’ in the Installation Type and check ‘2X Client Gateway’ option. Please refer to the chapter entitled “Installing 2X VirtualDesktopServer” for more information about how to install the 2X Client Gateway.
If you want your clients to connect to the 2X Client Gateway using SSL, make sure you click on ‘Use SSL’. In this case a certificate and private key must be provided. You can use your own or simply click on ‘Create a new certificate…’ to create them. Enter all your information and the FQDN of your 2X VirtualDesktopServer (Common name) and click ‘Generate new certificate…’.
Backup Servers In this page one can add Backup Servers so that if the Master server fails, the next server in the list takes over. The backup servers can also be used as additional Client Gateways to distribute the load on the gateways. Figure 135 - Redundant VirtualDesktopServer Figure 136 - Backup Servers Adding 2X Backup Servers 1. 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.
Figure 137 - Find 2X Backup Servers 2. When the state of selected server is ‘Agent Not Found’ it means that 2X Publishing Agent is not installed on the selected server. Therefore you would need to install this service by clicking the ‘Install Agent…’ button. 3. Enter administrative credentials to be able to install the 2X Publishing Agent on the selected server which will be used as a backup server.
4. Click ‘Install’ after you’ve entered the administrative credentials. You should note that service is installed successfully if the installation is done completely. 5. 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. NOTE: 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.
Figure 140 - 2X Backup Server Properties NOTE: The ‘Install…’ button change according to the status of the selected server. In fact it will change to ‘Update…’ if an old 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 a master server. Modifying 2X Backup Servers To change the properties of each backup server, select the particular server and click ‘Properties’.
First launch the 2X VirtualDesktopServer Console located in 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, one can easily launch 2X Console located at “C:\Program Files\2X\VDS\2XConsole.exe”. Figure 141 - Promote a 2X Backup Server to a Master Secondly click ‘Promote to Master’ button to promote the current backup server as a Master Server.
LOAD BALANCING To configure 2X LoadBalancer click on ‘Load Balancing’ in the Navigation bar in the 2X VirtualDesktopServer Console. This option is available in Enterprise Edition and VDS Edition. Load Balancing In this page you can choose the load balancing method to be used. The 2X LoadBalancer has two possible methods to load balance incoming connections.
on the counters chosen, will determine the terminal server that will handle the incoming connection. Three different counters are available: Sessions: the connection is redirected to the server with the least number of sessions in use. Memory Utilization: the connection is redirected to the server with the best free/used RAM ratio. CPU Utilization: the connection is redirected to the server with the best free/used CPU time ratio.
Advanced Settings From the Advanced Settings one can change the default timeouts for the Terminal Server Agents. Advanced settings should be configured using the default settings in normal scenarios. Declare TS Agent dead. 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.
Rules In this page one can set specific filters so that native RDP & ICA connections can be redirected to specific terminal server(s). Load balancing rules are useful to assign a group of terminal servers or a specific terminal server with a specific 2X Client Gateway IP. Therefore connections initiated from that particular IP will be load balanced to correspondent group or particular terminal server. NOTE: Load Balancing Rules are applicable only to non published desktop sessions.
Add a new rule To add a native RDP & ICA Load Balancing Rule, click the ‘Add…’ button. This will open a new dialog as shown below. First select the interface for which you would like to create the rule. Secondly you have to select between ‘All Servers in Farm’, ‘Server Groups’, ‘Individual Server’ or ‘None’. Rules Properties All Servers in Farm All connections initiated through this interface will be load balanced between all servers in the farm.
Individual Server All connections initiated through this interface will be load balanced with the selected individual servers. Therefore one can select particular individual servers and connections initiated from the selected interface will be load balanced with the selected Terminal Server. With this option one can also configure an IP to be associated with only one single server. None All connections initiated through this IP will be denied.
Figure 147 - Load Balancing Rules NOTE: One can create only one rule for each gateway IP.
PUBLISHING 2X Publishing Wizard To start publishing the applications, select ‘Publishing’ from the Navigation bar and click the ‘Add…’ button from the Publishing tools. Figure 148 - Publishing Tools A new dialog ‘Select Type’ as shown in the figure below will ask you what you want to publish.
Application One of the most useful features available on 2X VirtualDesktopServer is the ability to publish individual (seamless) applications to your users. This means users will see only the applications you give them access to and not full terminal services desktop (when using terminal services only). To publish an application, follow these steps: 1. Choose Application and click ‘Next >’ 2.
NOTE: If only one server is listed in the Terminal Server list, the wizard will skip step 1 (Publish From) and continue with the Application Settings (step 2). 1. In the ‘Publish From’ dialog as seen in the below figure you can choose from which Terminal Server/s you want to publish the application. You can choose to publish the application from ‘All Server in Farm’ *, from Server Groups or from Individual Terminal Servers.
Figure 152 - Application Settings Application Settings First you may type the Name and Description related with application that you are going to publish, but Name and Description can be left blank and filled automatically when you choose the application from the target. You also have the ability to specify the run mode when the published application is launched. The options are to launch the application in a normal window, in a full screen mode or minimized.
Figure 153 - Application Settings – Change Icon From this dialog you may also change the icon for the published application. Click ‘Change Icon…’ and select a new icon from the executable file itself or from other locations by clicking ‘Browse...’ in the Change Icon dialog box.
Figure 154 - Application Advanced Settings To create shortcuts of this particular application on the desktop on the client side, enable ‘Create shortcut on Desktop’ checkbox. To create shortcuts of this particular application in the Start Menu Folder on the client side, enable ‘Create shortcut in Start Folder’ checkbox. One can specify to create the shortcut under certain folders by using ‘\’ and the name of the folder. E.g.
One can select one or more extensions to be associated with this published application. Add other File extensions To add other non default file extensions, click the ‘Add…’ button and enter the file extensions separated by a semicolon as shown in the figure below. E.g. doc2; txt; wdoc Figure 155 - Advanced Settings – Add File Extensions Disable Session Sharing You can isolate every published application to one (1) session. Every application that is published will have its own session on the server.
Notify administrator and start – this option will notify the administrator that the number of licenses has been exceeded and will still publish the application. Notify user, administrator and start – this option will notify both the user and the administrator that the number of licenses has been exceeded and will still publish the application.
Figure 156 - Select Filtering Type User First check the ‘Allow the following Users:’ checkbox and add the usernames/groups in the dialog ‘Select Users or Groups’ as shown in the figure below. LDAP Check “Use LDAP mode when adding Users & Groups” to add users and groups in LDAP format instead of WinNT format. Administrators can use LDAP format to filter users found in groups within groups.
Figure 157 - User or Group Filtering Client First check the ‘Allow the following Clients:’ and then select or type the Client (computer) name in the dialog ‘Select Client’ as shown in the figure below. For Client names you can use the * character as a wildcard. For example if all your computer names start with CLIENT- simply type CLIENT-*. Figure 158 - Client Filtering IP Address First check the ‘Allow the following IPs:’, then click the ‘Add...’ button.
Figure 159 - IP Address Filtering Click ‘Finish’ to finalize the wizard, and the application you’ve just configured will be generated in the ‘Published Applications Explorer’ area. Now you can re-configure the options by using the tabs in the Published Applications Properties’ area. Publish Installed Applications An application already installed on the server can be published and used by its clients.
Figure 160 - Installed Applications Select which applications you would like to publish from the list of available applications already installed on the server and just click finish when you have selected all the applications to publish. Publish Predefined Applications To publish a predefined application with the wizard, click on ‘Publishing’ in the Navigation bar and click ‘Add…’.
Figure 161 - Publish Predefined Applications From the predefined applications one can publish with ease the Control Panel, certain Control Panel tools, the Printers and Faxes folder or even publish an explorer window. Folder To publish a Folder with the wizard, click on ‘Publishing’ in the Navigation bar and click ‘Add…’. From the ‘Select Type’ dialog choose ‘Folder’.
Figure 162 - Add Application Group You can also enter the description and modify the icon for each application group as shown in the above figure. Application Groups in the 2X Console will be also displayed as application groups on the client side and web. After you click ‘Next’, you can also choose to create certain filtering rules (User, Client, IP address) for the created folder. Published application or desktops listed under this folder will inherit the filtering rules of this folder.
• Virtual Desktop – Publish a desktop from a Virtual Desktop Host • PCs – Publish a desktop from a Personal Computer Publish a Terminal Server Desktop Full Desktop acts like a terminal into an actual server where you can have a remote desktop connection. To publish a Desktop with the wizard, click on ‘Publishing’ in the Navigation bar and click ‘Add…’. From the ‘Select Type’ dialog choose ‘Terminal Server Desktop’.
Desktop In this dialog you can type the Desktop Name and a Description for the published desktop. From this dialog you may also change the icon for the published desktop. Windows 2003 Terminal Services gives the ability to connect to the console (session 0) which is the desktop of the actual server, rather than a terminal server session.
Figure 164 - Choose from which Virtual Hosts you want to publish the application * ‘All Servers in Farm’ is the terminology used to indicate the whole list of Virtual Desktop Hosts which can be configured from the Virtual Desktop Hosts tab in the VDI Hosts page.
Figure 165 - Virtual Desktop Settings Virtual Desktop In this dialog you can type the Desktop Name and a Description for the published desktop. From this dialog you may also change the icon for the published desktop. You can also click ‘Advanced Settings…’ to create shortcuts on client’s desktop or start folder of the particular published desktop. Properties There are 3 different properties which can be used by the Virtual Desktop.
Choose, from the drop down list, the resolution you would like to use. Choose ‘Custom’ to be able to enter your own resolution. Publish Personal Computer Desktop To publish a PC with the wizard, click on ‘Publishing’ in the Navigation bar and click ‘Add…’. From the ‘Select Type’ dialog choose ‘Desktop’. From the ‘Select Desktop Type’ dialog choose ‘Personal Computer Desktop’ and click ‘Next >’.
Personal Computer Select from the list the Personal Computer that you would like to publish. For the Personal Computer to be available, it must first be added to the Farm. Desktop Size Choose, from the drop down list, the resolution you would like to use. Choose ‘Custom’ to be able to enter your own resolution.
User First check the ‘Allow the following Users:’ checkbox and add the usernames/groups in the dialog ‘Select Users or Groups’ as shown in the figure below. LDAP Check “Use LDAP mode when adding Users & Groups” to add users and groups in LDAP format instead of WinNT format. Administrators can use LDAP format to filter users found in groups within groups.
Figure 169 - Client Filtering IP Address First check the ‘Allow the following IPs:’, then click the ‘Add...’ button. You can select to filter a single IP or a range of IPs. Figure 170 - IP Address Filtering Click ‘Finish’ to finalize the wizard, and the application you’ve just configured will be generated in the ‘Published Applications Explorer’ area. Now you can re-configure the options by using the tabs in the Published Applications Properties’ area.
browse for. You may also add custom content types if they’re not listed in the Filters list by listing the custom file extensions separated by semicolon. E.g *.text; *.texts; *.
Publish Applications using Drag and Drop An alternative method to publish applications is to drag an application from the Windows Explorer. This method will capture all data related with the application and will be incorporated in the Application and Startup settings. Then you may opt to configure the ‘Publish From’ and Filtering settings from their respective tabs as by default drag and drop applications will be published to ‘All Farm’ and Filtering is not enabled.
Publish Applications Configuration Figure 173 - Applications Configuration – Information, Publish From, Application and Filtering After you’ve published an ‘Application’, ‘Application Group’, ‘Desktop’, ‘Predefined applications’ or a ‘Virtual Desktop’ using the Wizard or the drag and drop facility, you may choose to re-configure each selected item by using the ‘Published Application Properties’ Area.
2X Startup Wizard Figure 174 - Startup Wizard 2X VirtualDesktopServer now 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 the shortest amount of time. Start by selecting what you want to publish. You can choose from: • Virtual Desktop – Add a new Virtual Host and publish a virtual desktop.
Figure 175 - Choose from where you want to publish from Choosing ‘All Servers in Farm’ will include all the servers that are added to the farm. If only on server is present you will be automatically taken to the ‘Startup Wizard - Publish Virtual Desktop’ Dialog. Choosing ‘Server Groups’ will allow you to choose which group of servers from your farm you would like to use to publish a virtual desktop.
Figure 176 - Publish a Virtual Desktop Virtual Desktop In this dialog you can type the Desktop Name and a Description for the published desktop. From this dialog you may also change the icon for the published desktop. Properties There are 3 different properties which can be used by the virtual desktop. ‘Connect to any guest’ will load any virtual desktop published to any user that logs in. ‘Connect to specific guest’ will load the virtual desktop selected to every user.
Choosing ‘Server Groups’ will allow you to choose which group of servers from your farm you would like to use to publish an application. Choosing ‘Individual Servers’ will allow 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. Choosing ‘New Server’ will allow you to add a new server to the farm and use it to publish an application.
Choosing ‘Server Groups’ will allow you to choose which group of servers from your farm you would like to use to publish a desktop. Choosing ‘Individual Servers’ will allow you to choose the servers you would like to use to publish a desktop one by one by checking the checkbox next to the name of the server. Choosing ‘New Server’ will allow you to add a new server to the farm and use it to publish a desktop.
Setup LoadBalancer Figure 179 - Select the server to be used for load balancing After selecting ‘Setup LoadBalancer’ a new page will load listing all the servers available on the network and the information about their Agent. Select which servers you would like to use for load balancing by checking the check box next to the servers.
2X UNIVERSAL PRINTING 2X Universal Printing is used to solve printer drivers problems. If the client is using a printer which the server does not have a suitable printer driver, the normal printing redirection will not work. Using 2X Universal Printing you do not need to install the specific printer driver on the server. Only one printer is shown on the server irrespective of the number of users and sessions currently in use on the terminal server thus avoiding confusion.
EMF Properties To control if any fonts are embedded within a print job go to the 'EMF Properties' tab and check/uncheck 'Embed Fonts'. By default a number of fonts will already be excluded since these are normally available on standard Windows platforms. If the client selects "Enhanced Meta File" data format for Universal Printing, you can select which fonts are embedded with the print job. To add a new font click on the ‘Add’ button and select the font which you would like to add.
CONNECTION SETTINGS Publishing Agent In this page you may configure which port to use for the publishing agent service. You may also configure the authentication options. Figure 182 - Connection Settings page – Publishing Agent Tab The 2X Publishing Agent Port (default TCP 20002) uses a specific port to pass information about the published applications available to its clients. The default port is TCP 20002.
Authentication To make sure that every single client authenticates against the 2X VirtualDesktopServer to retrieve the list of published applications enable ‘Always require user credentials for application list’ checkbox. To authenticate against a specific domain/workgroup you have to select the ‘domain’ radio button and enter the domain/workgroup required. In case you want to select a new domain for authentication, simply click on ‘…’ button and select the new domain to be used.
Deepnet Unified Authentication Platform To add two-factor authentication to your 2X VirtualDesktopServer you can use Deepnet. Click on ‘Configure’ where a new window will open for you to input your Deepnet server settings. Figure 183 - Deepnet Unified Authentication Platform: Connection Properties Connection First check the ‘Enable Deepnet Unified Authentication Platform’ if you want to use Deepnet. Enter the server name and port that you saved while setting up your Authentication Sever.
Figure 184 - Deepnet Unified Authentication Platform: Application Properties Select the application profile that will use Deepnet to authenticate its users. Figure 185 - Choose 2X VirtualDesktopServer From the above dialog you can choose the application which used by 2X VirtualDesktopServer for authentication. You can also create an application which will be added on the Deepnet server. The ‘Default Domain’ enables you to choose the default domain that your users will use.
Authentication Figure 186 - Deepnet Unified Authentication Platform: Authentication Properties Select how you want your users to be authenticated. ‘Mandatory for all users’ means that every user using the system must log in using two-factor authentication. ‘Create token for Domain Authenticated Users’ will allow 2X VirtualDesktopServer to automatically create software tokens for Domain Authenticated Users. Choose a token type from the drop down list. Note that this option only works with software tokens.
Exclusion Figure 187 - Deepnet Unified Authentication Platform: Exclusion Properties ‘User / Group exclude list’ allows you to add users or groups within your active directory that will be excluded from using Deepnet Authentication. ‘Client IP exclude list’ allows you to add IP addresses or a range of IP addresses that will be excluded from using Deepnet Authentication. ‘Client MAC exclude list’ allows you to add a MAC addresses that will be excluded from using Deepnet Authentication.
INFORMATION Status In this page you can monitor the status of each service, while you can also monitor sessions connected on the Virtual Desktop Host, Terminal Servers or Citrix Servers enabled in the farm. The status is refreshed every minute. You may also use the 'Refresh' button to manually refresh the content.
Notification To be notified when some counters exceed a certain amount, you will need to enable the notification options. In the Notification tab you’ll be notified if some server parameters exceed what you define as appropriate. Figure 189 - Notification You can choose any of the counters monitored by the 2X Terminal Server Agent and set the appropriate number accordingly.
(for example, support@2x.com) and click on ‘Mailbox Setup…’. Figure 190 - Mailbox Setup Type in the sender address you would like to see (for example, support@2x.com) and the SMTP server address to be used. If your SMTP server requires authentication when sending emails through it, make sure you select ‘SMTP Server requires authentication’ and type in the correct username/password to be used. One can also configure different ports for the SMTP server by append ‘:’ port. E.g. mail.company.
Logging The Logging tab allows you to enable logging and to set the location of the log file to be used. You may enable logging by ticking the ‘Enable Logging’ Check Box in the logging tab. You may also enable ‘Log Servers Performance’ and performance counters of each load balanced server will be saved. Then you may also set the location of the log file to be used.
Auditing In this page you can enable auditing and set the location of the auditing file. The auditing log is an important and valuable tool as it can give information about the sessions opened and the total time of each session. Backup Audit File It is recommended to backup the audit file in a compressed file. This could be done by enabling the ‘Backup audit file’ checkbox. Backup can be scheduled on daily, weekly or monthly basis.
Software Update In this page you can set the 2X VirtualDesktopServer Console to check for updates by enabling ‘Check for updates when launching 2X VirtualDesktopServer.’ You may also click the ‘Check Now…’ button to check for the latest updates. In the Modules Information filed you can find information about the modules used by 2X VirtualDesktopServer. This field will give you an overview of what files are installed and their current version.
Support For further technical support queries or further information about 2X products view contact details on this tab. Figure 194 - Information page - Support Tab Click on ‘Send Support Request…’ button to contact 2X Support directly from the console. Fill in the required details, add an attachment if you require and click ‘Send’. You should configure your mail settings in order to contact 2X Support from 2X Console.
Figure 195 - Contact 2X Support You can save your support request information as a Zip file, this way you don’t have to send the email straight away; you can send the Zip file later on from any other machine.
LICENSING The licensing tab will allow you to view licensing details and enter a license key. If you have purchased a new license key, click the ‘Activate…’ button. Fill in the required details in the ‘License Activation’ dialog and click the ‘Activate’ button to activate your license key. 2X VirtualDesktopServer NOTE: If you decide to allow more users to connect to your published applications, exceeding your current license, a new license key will be required.
2X VirtualDesktopServer Licensing • 180
License Activation In order to activate the license key, fill in the required contact details and type the license in the ‘License key’ field and click ‘Activate’ as shown in the figure below. Figure 197 - License Activation When the license key is activated, you should get a dialog which states that the license key is activates successfully. Figure 198 - License Key activated successfully NOTE: ApplicationServer & LoadBalancer version 6 requires a version 6 license.
2X ADDITIONAL UTILITIES 2XA Generator 2XA Generator is a command line utility to create 2xa files. 2xa files contains the required information to launch a published item. To use 2XA Generator, run 2XAGen.exe [c:\Program Files\2X\VDS\2XAGen.exe] in a command prompt and pass the appropriate parameters.
2XA Generator Examples EXAMPLE 1: 2XAGen.exe -s "TSServer1" –p 80 -a "Word" OUTPUT OF EXAMPLE 1: 80 TSServer1 Word EXAMPLE 2: 2XAGen -s "TSServer1" -p 80 -a "Word" -u "Testuser1" –pc "mypassword" -d "mydomain" -ss "TSServer2" –pr"C:\document.doc" -o word.2xa OUTPUT OF EXAMPLE 2: [content of word.
INSTALLING 2X CLIENT FOR WINDOWS 2X Client System requirements • Windows 2000, XP, Vista. • The same hardware requirements as specified by Microsoft when using any of these workstation OSs • Some features (like high color, sound, etc) will only be available if your workstation has the appropriate hardware installed and properly configured. Installing 2X Client Before you run the installation procedure please make sure that you are logged on as Administrator and the system requirements are met. 1.
Figure 201 - The EULA. 3. Select the location where you want to install the 2X Client and click ‘Next’. Figure 202 - Choosing the location where the 2X Client will be installed. 4. To start copying files click ‘Install’.
Figure 203 - Starting the installation program. 5. Click ‘Yes’ to install the ‘Single Sign-On’ component. This component will use your credentials to connect with the 2X VirtualDesktopServer. Figure 204 - Installing Single Sign-On 6. Setup will copy the required files. After finishing you will see the status screen.
Figure 205 - Post-Installation status screen. Installing the 2X Client silently By using the MSI format, administrators can now deploy the 2X Client remotely by using Group Policies or any other deployment tool that accepts the MSI format. This greatly simplifies the amount of work to install the 2X Client on all remote computers and reduces the chances of user error during the installation process.
To assign an application to certain computers simply do the following on your Active Directory: 1. Open the Group Policy Editor. 2. To assign an application to a computer, navigate through the group policy console to Computer Configuration | Software Settings | Software Installation. Now, right click on the Software Installation container and select the New | Package commands from the shortcut menu. Select the appropriate MSI file and click Open.
Detailed explanation of 2X Client options General Settings OVERRIDEUSERSETTINGS: To override the user settings with client MSI settings. 0 – Client settings are not overridden 1 – Client settings are overridden with the new settings of the Client MSI setup. AUTOHIDE: Hide Launcher when application is launched 0 – Auto hide is disabled 1 - Auto hide is enabled ALWAYSONTOP: 2X Client behavior to stay on top of other applications.
CONNTIMEOUT: The amount of time before the client time out the connection if a connection is not successful. The default setting is 20 seconds and the option can be increased for connections with high latency. SSLNOWARNING: Do not warn if server certificate is not verified. 0 – Display warning message 1 – Do not display warning message IGNORERESCHECK: Option to ignore the resolution check.
AUTOADDFARM: Add farm automatically when starting web or shortcut items. 0 – Do not add farm automatically 1 – Add farm automatically MINIMIZETOTRAYONCLOSE: Minimize to tray on close or escape. 0 – Close 2X Client 1 – Minimize 2X Client to tray AUTOREFRESHFARMS: Option to automatically refresh the farms listed in the client.
2 – Prompt during installation 2X VirtualDesktopServer Installing 2X Client for Windows • 192
Farm Settings - Connection CONNECTIONMODE: Connection Mode Settings. 0 - Regular Gateway 1 - Direct Mode 2 - SSL Mode SERVERPORT: TCP port number in use for the 2X VirtualDesktopServer application list retrieval. You must enter the number in use. E.g. 80.
Farm Settings – Advanced Settings USECLIENTCOLORS: Use client system colors. 0 - Do Not Redirect Client Colors 1 - Redirect Client Colors USECLIENTSETTINGS: Use client system settings (border size, fonts, etc).
OVERRIDECOMPUTERNAME: The name that the computer will use during a Terminal Server session 195 • Installing 2X Client for Windows 2X VirtualDesktopServer
Farm Settings – Local Resources KEYBOARD: Where to apply key combinations. 0 – On the local Computer 1 – On the remote Computer 2 – In full screen mode only AUDIOMODE: Options for Remote computer sound. 0 - Bring to this computer 1 - Do not play 2 - Leave at remote computer REDIRECTCOMPORTS: To redirect local serial ports on to the remote computer.
Farm Settings – Experience EXP_DESKTOPBG: Desktop background 0 – Disable 1 – Enable EXP_FONTSMOOTHING: Font smoothing 0 – Disable 1 – Enable EXP_WINDOWMENUANIMATION: Menu and window animation 0 – Disable 1 – Enable EXP_DESKTOPCOMPOSITION: Desktop composition 0 – Disable 1 – Enable EXP_SHOWCONTENT: Show contents of Windows while dragging 0 – Disable 1 – Enable EXP_THEMES: Themes 0 – Disable 1 – Enable EXP_BMPCACHING: Bitmap caching 0 – Disable 1 – Enable
Farm Settings – Proxy PROX_USERNAME: Proxy credential details PROX_HOST: Proxy hostname PROX_PORT: Proxy port PROX_TYPE: Proxy type can be one of the following: 0 – SOCKS4 1 – SOCKS4A 2 – SOCKS5 3 – HTTP 1.1 PROX_USEPROXYSERVER: Enable if you want to use proxy 0 – Disable 1 – Enable PROX_USEAUTHEN: If proxy type is HTTP1.1 or SOCKS5, user can enable authentication. 0 – Disable 1 – Enable CLEARPROXYPASSWORD: Clear password for the user.
Using ORCA to change the MSI After downloading and installing ORCA, all you need to do is launch ORCA and open the ‘2XClient.msi’ package. Once you open the MSI package, on the LEFT hand side (Tables column) you will see ‘Property’. Click on it. Figure 206 - Using ORCA to open the MSI package. Some of the properties (like SERVERPORT for example) may be already available in the MSI package. If a certain property is not available, simply click on ‘Tables’ | ‘Add Row…’. Figure 121– Adding a new row.
Now click on ‘Property’ and type in the name of the property you want to add. After adding the property, click on ‘Value’ and type the value you want. Make sure you enter the right property name and its value. Once you finish click Ok. Figure 207 - Adding a new property/value. After adding all the properties you want simply go to File | Save As… and type a new name for your customized MSI file. This file can now be used with Active Directory to perform a completely silent and automated installation.
USING 2X CLIENT FOR WINDOWS Introduction After you have installed the 2X Client, you can now launch the 2X Client to access your published applications. Figure 208 - Launching the 2X Client To open the 2X Client: 1.
Configuring 2X Client for Windows When launching the 2X Client you will be prompted to configure a new 2X Connection. Please refer to the ‘2X Connection’ section below for more information about how to setup a new 2X Connection Figure 209 - 2X Client Initial Screen. 2X Client for Windows is able to connect with multiple farms where farms is a common term used in remote session computing to refer to a group of Terminal Servers.
2X Connections The first thing you must do is to add a new 2X Connection, by clicking ‘File’ and select ‘Add New 2X Connection…’ or right click on ‘2X Connections’ and click ‘Add New 2X Connection…’. Figure 210 - 2X Client – Add New 2X Connection.
Figure 211 - 2X Client – 2X Connection Properties – Connection tab. Connection Settings In the Connection Settings area, enter the Primary Server name or IP. This should be the name or IP where the 2X Client Gateway resides. If your administrator enabled ‘Broadcast 2X Client Gateway Address’ option on the server, you can click on the browse button ‘…’ and you should see the available 2X Connection/s in your area.
NOTE: In order to connect through the 2X Client Gateway you just need to set the port number that was configured on the Client Gateway Port in the Connection Settings Page. (Default Gateway Port 80) Logon Enable ‘Auto Logon’ to enable the 2X Client connect automatically instead of displaying the logon page every time you need to access the 2X Connection.
Local Resources In case you want to configure how local resources are handled by the terminal server, simply click on the ‘Local Resources’ tab and select the options you want (these are the same options available with the regular Microsoft RDP Client). Figure 212 - 2X Client – 2X Connection Properties – Local Resources tab.
Experience The experience tab allows you to tweak the connection speed to optimize the performance of the connection with the remote host. If you are using a connection to a remote computer in a local network that runs at 100mbit or up, it is usually safe to have all of the experience options turned on. Figure 213 - 2X Client – 2X Connection Properties – Experience tab.
Network In the Network Tab you may configure network settings to be able to connect to 2X VirtualDesktopServer using a proxy. To be able to connect to a Proxy Server, check the Use Proxy Server checkbox. The following are different proxy connection types that can be used: SOCKS4 – Enable this option to transparently use the service of a network firewall. SOCKS4A – Enable this option to allow a client that cannot connect to resolve the destination host’s name to specify it.
Figure 214 - 2X Client – 2X Connection Properties – Network tab.
Advanced Settings Use Client System Colors - Enable this option to use the client system Colors instead those specified on the Terminal Server. Use Client System Settings – Enable this option to use the client system settings instead those specified on the Terminal Server. Create shortcuts configured on server – For each published application, the administrator can configure shortcuts on the clients desktop and start menu folder. With this option one can choose to have or not to have these shortcuts.
Figure 215 - 2X Client – 2X Connection Properties – Advanced Settings 211 • Using 2X Client for Windows 2X VirtualDesktopServer
2X Universal Printing To use the 2X Universal Printing, the Clients will just have to click ‘Print’ while using the published application on the Terminal Server and select ‘2X Universal PDF Printer’.
In the 2X Universal Printing tab the Client can configure to choose: Print to default printer – Use the default printer on the client side. Select printer before printing – Open the dialog to choose the printer before printing. Use the following printer – Click on ‘…’ to select the printer and always use the selected printer when printing through the 2X Universal PDF Printer. View document to print – Use this option to view the printed document using the default PDF viewer instead of printing.
Figure 217 - 2X Client – Options – 2X Universal Printing tab 2X VirtualDesktopServer Using 2X Client for Windows • 214
Advanced Settings In the Advanced Settings tab, you may configure the default behavior of 2X Client. Hide Launcher when application is launched - If this option is enabled, the launcher will get minimized in the system tray after an application is launched. Always on Top - To enable 'Always on Top' feature, highlight the 'Always on Top’ checkbox. With this feature enabled other applications will no longer mask the launcher.
Figure 218 - 2X Client – Options – Advanced Settings tab. In the Advanced Settings tab click ‘Check for updates now …’ to check if there are any available updates for 2X Client. If there are updates available one can click ‘Update’ which will download the latest setup and install the Client or click ‘Download’ which will download the latest setup to a specified location.
Listing of Published Applications After configuring the 2X Client simply click ‘OK’. If you entered a valid username and password and the server IP address and port are correct, you should see the list of published applications available to your username/computer/IP address on the main window. Figure 220 - 2X Client main window with published applications.
Terminal Server Connection 2X Client is able to connect to multiple Terminal Server Desktops using an RDP connection. To connect to a desktop click ‘File’ and select ‘Add New Terminal Server Connection...’ Connection Connection settings In the Connection settings area, type the Primary Connection name or IP. This should be the name or IP of the desktop you want to connect to. The ‘Alias’ will give the connection a display name for better readability.
Figure 221 - 2X Client – Connection Properties – Connection Properties 219 • Using 2X Client for Windows 2X VirtualDesktopServer
Display Remote desktop size Select your preferred resolution by selecting one of the options from the drop down list. You can set the connection to use the available area, a predefined resolution, full screen or a custom resolution. If you select ‘Custom’ you will have to enter the width and the height in the enabled text boxes.
Local Resources In case you want to configure how local resources are handled by the terminal server, simply click on the ‘Local Resources’ tab and select the options you want (these are the same options available with the regular Microsoft RDP Client). Figure 223 - 2X Client – Connection Properties – Local Resources tab.
Programs Start a program Enable ‘Start the following program on connection’ to start an application when a connection to the remote desktop is established. Type the path and file name of the application that you would like to launch in the ‘Program path and file name’ field (Example – “c:\windows\notepad.exe”). You can also set a start folder in the ‘Start in the following folder’ field (Example – “c:\windows”).
Experience The experience tab allows you to tweak the connection speed to optimize the performance of the connection with the remote host. If you are using a connection to a remote computer in a local network that runs at 100mbit or up, it is usually safe to have all of the experience options turned on. Figure 225 - 2X Client – Connection Properties – Experience tab.
Network In the Network Tab you may configure network settings to be able to connect to 2X VirtualDesktopServer using a proxy. To be able to connect to a Proxy Server, check the Use Proxy Server checkbox. The following are different proxy connection types that can be used: SOCKS4 – Enable this option to transparently use the service of a network firewall. SOCKS4A – Enable this option to allow a client that cannot connect to resolve the destination host’s name to specify it.
Figure 226 - 2X Client – Connection Properties – Network tab.
Advanced Settings Connect to console – Enable this option to connect to the console session (session 0) of the Terminal Server Display the connection bar when in fullscreen mode – This will show the RDP connection bar at the top of the page. Reconnect if connection is dropped – Enable this option to automatically reconnect to the Terminal Server if the connection is dropped.
Using Terminal Server Connections After adding a Terminal Server connection, simply double click it or click ‘Open’ to start the connection. You can start multiple connections at once. 2X Client will embed all the connections inside the window and you can switch between one connection and another by clicking on the corresponding tab.
2X Client for U3 U3 is a company producing a propriety method of auto launching applications from specially formatted USB U3 smart drives. The U3 launch pad is a program manager that is preinstalled on every U3 smart drive. You can install U3 2X Client and also launch it from the U3 launch pad. Figure 229 - U3 2X Client Launch Pad As you can see above, 2X Client will run normally without being installed on your local machine, when running on a U3 smart drive.
2X Client for PortableApps.com PortableApps.com is a software solution allowing you to take your favorite software with you. A fully open source and free platform, it works on any portable storage device (USB flash drive, iPod, memory card, portable hard drive, etc). Figure 230 – 2X Client running from PortableApps.com As you can see above, 2X Client will run normally without being installed on your local machine, when running on PortableApps.com. To add 2X Client to PortableApps.
2X ACCESS PORTAL 2X Access Portal allows users to launch published applications and desktops from multiple farms which are accessed through a web portal according to their filter settings. Pre-requisites • Windows 2003/2008 Server • Microsoft .NET Framework II • IIS 6 • 2X VirtualDesktopServer Installation 1. Run the 2X Access Portal setup program by double clicking on the ‘2XWebPortal.msi’ file on an IIS machine to be used as your access point to the published applications from the Web Portal.
2. Accept the license agreement by enabling ‘I accept the terms in the License Agreement’ checkbox.
3. In this screen you’re asked to assign the port on which the 2X Web Service will be installed. By default this 2X Web Portal will be installed on port 81. Please note that 2X Client Gateway by default is installed on port 80 is configured to forward the HTTP requests to localhost on port 81. Therefore the Clients will still be able to access the 2X Web Portal from port 80. However one may choose to install the 2X Web Service on any other port and one may also use an existing port used by other web site.
4. Click ‘Install’ to begin the installation - Setup will copy the required files and will create the service on the machine.
Configuration The first step after installing the 2X Web Portal is to direct the browser to [http://localhost/2XWebPortal/Logon.aspx] and login with a username with administrative rights on the IIS machine.
Add Farm by entering the IP/hostname on the left side and click 'Add Farm'. One can configure how the 2X Web Service will connect with the 2X Client Gateway in the ‘Farm Details’. Figure 236 - Add a new farm In the Farm Details, the Administrator should configure the settings of the 2X Client Gateway for each farm. The 2X Client Gateway Details as shown in the figure below are used from the 2X Web Service to connect with the 2X Client Gateway.
To configure (override) the options how the Client will connect with the 2X Client Gateway, click the 'Advanced Settings' options. These options allow the administrator to override the options that are used in the 2X Client Gateway Details and give the ability to use different settings when 2X Clients are connected with the 2X Client Gateway. Figure 238 - Advanced Settings After you configure the required settings, click ‘Apply Settings’ and log out and log in again to retrieve the applications listing.
Figure 239 - Application Listing To connect in a secure mode one should enable SSL on the 2X VirtualDesktopServer or enable SSL on IIS. Figure 240 - Secure Login One may add more farms by using the above steps again. Click 'Apply Settings' to activate your settings. 2X Client 2X Access Portal is able to identify whether the 2X Client is installed or not. When the 2X Access Portal identifies that the 2X Client is not installed on the client's system, a link to the appropriate client is displayed.
Clients for different Operating systems can be placed in the mentioned folder and file names must be using the following names. Windows Client: 2XClient.msi Mac Client: 2XClient.dmg Linux Client: 2XClient.i386.
INSTALLING 2X CLIENT FOR LINUX 2X Client is approved for the following Linux distributions: Ubuntu 8.04, Ubuntu 8.10, Ubuntu 9.04, OpenSuse 11.1, Fedora Core 9. Installation Procedures (RPM Version) 1. Download the rpm package from http://www.2x.com/virtualdesktop/downloadlinks.html and store it locally. 2. Switch to the root user. 3. To install type: rpm –ivh 2XClient.i386.rpm 4. 2X Client for Linux binaries are now installed under: /opt/2X/applicationserverclient/bin 5.
Installation Procedures (.TAR.BZ2 Version) 1. Download the tar package from http://www.2x.com/virtualdesktop/downloadlinks.html and store it locally. 2. Switch to the root user. 3. Switch to the root foler: cd/ 4. To install type: tar jxvf 2XApplicationServerClient.tar.bz2 5. 2X Client for Linux binaries are now installed under: /opt/2X/applicationserverclient/bin 6. Run the following command to launch 2X Client: /opt/2X/applicationserverclient/bin/WTSClient 7.
User Interface Please refer to “Configuring 2X Client for Windows” for usage instructions.
Command Line Interface 2X Application Server Client. Version 4.3.2083. Copyright (C) 2005-2007 2X Software.
"printername=drivername" to specify driver name also -S: redirect sound, can be "off" to disable sound (default) "local"= quality to bring it to the client with: "normal" for normal quality "good" for good quality (default) "verygood" for very good quality "remote" to leave it on the server Other options: -o: output mode 1 - print return code to stderr 2 - print return message to stderr 3 - print return code and message to stderr -v: print version info -?: to get help information 243 • Installing 2X Client
INSTALLING 2X CLIENT FOR MAC OS X System Requirements • Mac OS X Version 10.3.9 and up Installation Procedures 1. Download the 2XClient.dmg file from http://www.2x.com/virtualdesktop/downloadlinks.html and store it locally 2. Double click on 2XClient.dmg, the installation dialog will come up, then click 2XClient.pkg to continue the installation. Figure 242 - 2X Client for Mac OS X installation 3. Another dialog will show, click “Continue” to continue installing 2X Client.
Figure 243 - 2X Client for Mac OS X installation. 4. Click “Agree” to continue installing 2X Client. Figure 244 - 2X Client for Mac OS X installation. 5. Select the volume where you wish to install the 2X Client.
Figure 245 - 2X Client for Mac OS X installation.
6. When the installation is finished you are now ready to launch the 2X Client.
Usage Instructions Graphical User Interface To launch published applications using Graphical user Interface, follow these steps. 1. Launch the 2X Client 2. Click on File > Add new 2X Connection 3.
Figure 248 - Mac 2X Cclient – Application Browser 4. When you click the ‘OK’ button you will get the Application Browser window where the published applications are listed. 5. Double click on any application to launch it. 6. Execution of the published application as displayed in the figure below.
Command Line 1. Open a Terminal Window Go > Utilities > Terminals 2. Run the following commands to obtain a list of all usage parameters for 2X Client: cd /usr/bin ./appserverclient -?.
APPENDIX Examples how to use command line parameters The following examples illustrate the use of this Client: appserverclient -s -a<"Application Name"> -u appserverclient -s192.168.0.1 -a"Internet Explorer" -uAdministrator In this case you are requested to logon before the application is loaded. appserverclient -s -a<"Application Name"> -u -p appserverclient -s192.168.0.
When using the command line for Terminal Server Connections, using the TSClient, please make sure that the single quotes in the name of the connection are replaced with a double single quote. Example:- s! = ‘se’’ve’’’ 2XA Files TSClient.exe can also be used to launch to connect to a terminal server by using a 2XA file as a parameter. 2XA Generator is a command line utility to create 2xa files. 2xa files contains the required information to launch a published item. To use 2XA Generator, run 2XAGen.
0x0410 Italian (Italy) 0x0411 Japanese (Japan) 0x0412 Korean (Korea) 0x0427 Lithuanian (Latvia) 0x0426 Latvian (Latvia) 0x0413 Dutch (Netherlands) 0x0813 Dutch (Belgium) 0x0414 Norwegian (Norway) 0x0415 Polish (Poland) 0x0416 Portuguese (Brazil) 0x0816 Portuguese (Portugal) 0x0418 Romanian (Romania) 0x0419 Russian (Russia) 0x041A Croatian (Croatia) 0x041B Slovak (Slovakia) 0x041D Swedish (Sweden) 0x041E Thai (Thailand) 0x041F Turkish (Turkey) 0x0424 Slovenian (Slovenia)
TROUBLESHOOTING Introduction The troubleshooting chapter explains how you should go about resolving issues you have. The main sources of information available to users are: • The manual – most issues can be solved by reading the manual. • The 2X support site – accessible from the 2X website. It includes a knowledge base with the most frequently asked questions. • Contacting the support@2x.com • Contacting our support department by telephone.
