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.
î One of the supported virtualization
technology installed (for 2X VirtualDesktopServer only).
Installing
2X VirtualDesktopServer
Before you run the installation procedure please make
sure that you are logged on with administrator rights and that the system
requirements are met.
1. Run the 2X VirtualDesktopServer setup program by
double clicking on the
‘2XAppServer-LoadBalancer.msi’
file on the machine to be used as your access point to your terminal
servers and/or virtual hosts. A welcome dialog box will appear. Close other
Windows programs and click
‘Next’.
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’.
SMB
Edition is appropriate for a Single Terminal
Server environment while Enterprise Edition
is appropriate for a Multiple Terminal Servers environment. The
Custom method of installation will allow you
to choose which components you would like to install on the system.
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.
Figure
5 – Installation type –
Small
to Medium Business Edition
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
ApplicationServer and LoadBalancer – 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.* The gateway service
tunnels all traffic needed by 2X applications on a single port and provides
secure connections.
- 2X
VDS Agent – Consists of 2X VDS Agent service and 2X shell
component. The service collects resource information from the Virtual Host(s)
and forward the information to the 2X
VirtualDesktopServer.
* The 2X Management Console is a centralized GUI
application which provides the ability to configure 2X ApplicationServer &
LoadBalancer & VirtualDesktopServer.
NOTE:
The 2X Management Console will display the appropriate pages according to the
installation type.
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.1)
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. This can be done by either installing the 2X Terminal
Server Agents remotely from 2X Management Console while setting up the Terminal
Servers or by manually installing it on every Terminal Server by running the
same setup and selecting ‘
2X Terminal
Server Agent’ only. Please refer to the chapter entitled "
Installing
the 2X Terminal Server Agent" for more information about how 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.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. Please refer to the chapter entitled “
Installing
the 2X Terminal Server Agent” for more information about how to
install the 2X Terminal Server Agent.
- 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.
Figure 11 - Important Notice to be able to tunnel all
traffic through port 80
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 ApplicationServer
& LoadBalancer
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 VDS Agent services listed under
‘Services’. However this depends on which components you have
installed.
Figure 13 – The 2X Client Gateway, 2X Publishing
Agent, 2X Redundancy Server, 2X Terminal Server Agent Services and 2X VDS
Agent
NOTE:
The 30-day trial version and the full version of the application are the same
program. To re-enable the product after the 30-day trial period has expired, the
only action necessary will be to enter a valid license key in the Licensing
page. Re-installation will not be necessary.
