2X Server Installation Guide

Installing 2X ApplicationServer

Before you run the installation procedure please make sure that you are logged on with administrator rights and that the system requirements are met.

Make sure all other Window programs are closed.

The ‘2XAppServer.msi’ file can be found on our website, www.2X.com, available as a free download.  Run the 2X ApplicationServer setup program on the machine to be used as your access point to your terminal servers and/or virtual hosts.

Choose what to install according to your needs and requirements. Two common scenarios are the ‘regular gateway scenario’ and the ‘direct mode scenario’.

For more advanced and alternative scenarios and solutions please read 2X Server Based Computing Guide.

Double click on the 2XAppServer.msi file and a welcome dialog box will appear.

Click ‘Next’.

2X ApplicationServer  Setup Program welcome screen.

Accept the license agreement by checking the ‘I accept the terms in the License Agreement’ checkbox.

 The License Agreement.

Accept the default location or Browse to where you want to install 2X ApplicationServer and click ‘Next’.

Choosing the location where 2X ApplicationServer will be installed.

Select 2X ApplicationServer XG  for complete product installation.

Choose Your Installation type Setup Wizard installs 2X ApplicationServer

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

Click on Finish to launch the Configuration Utility.  If the utility does not automatically open, go to Start>2X Application Server Console to launch the utility.

Setup Completed 

2X ApplicationServer Services

To start, stop and configure 2X ApplicationServer Services, run the Microsoft Management Console ‘Services.msc’. 2X ApplicationServer  services are configured to start automatically when the system starts. The services installed depend on the installation you selected.

2X Secure Client Gateway, 2X Publishing Agent, 2X Redundancy Service and 2X Terminal Server Agent, 2X VDI Agent

2X Publishing Agent - provides load balanced applications and desktop publishing.

2X Redundancy Service - provides redundancy to 2X ApplicationServer

2X SecureClientGateway - tunnels all traffic needed by 2X applications on a single port and provides secure connections.

2X TerminalServer Agent – provides terminal server information to 2X Publishing Agent

2X VDI Agent – provides VDI host information to the 2X Publishing Agent

NOTE: All users who are connected via the 2X Secure Client Gateway will be disconnected if the 2X Secure Client Gateway service is stopped or restarted. Note that the default port (80) may already be in use (for example, by an HTTP server) – in this case it will be necessary to use a port number not currently in use by other local services.

Pre- Configuration MS Terminal Server Settings

With Terminal Services Configuration, you can reconfigure the properties of the RDP-TCP connection, including limiting the amount of time client sessions can remain active on the server, setting protection levels for encryption, and selecting which permissions you want users and groups to have.

Terminal Services Group Policies or Terminal Services extension to Local Users and Groups are the settings that you use to set connection properties on a per-user basis. You can set different session time limits for each user when you use the Terminal Services extension to Local Users and Groups.

Use Terminal Services Configuration to set the same time limit to all users who log on using the same server connection.

Configuring Terminal Services Connections

From the Start menu > Administrative Tools>Terminal Services Configuration

Server Settings

Click on Server Settings and click the ‘Restrict each user to one session option’.  This enables reconnections to previously disconnected user sessions, conserving server resources.

NOTE: This feature is also configurable in the ‘Load Balancing’ section.

Connection Settings

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

Logon Settings Tab

Logon Settings

Verify that the ‘Always prompt for password’ checkbox is unchecked; allowing clients to launch applications using the credentials that have been saved on the 2X Client.  This will avoid unnecessary repeated authentication cycles.

Environment Tab

Environment

On 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.  Click Ok.

Citrix

What is Citrix ?


A server solution that uses Microsoft Terminal Services software to deliverWindows applications to PCs, Apple Macintosh computers, X terminals and UNIX workstations. This enables users of those systems to access and use those programs which are available to those using the Windows operating system. Citrix servers use two technologies; WinFrame and Independent Computing Architecture (ICA).


What is Microsoft Terminal Services ?


Terminal Services provides the ability to host multiple, simultaneous client sessions on Windows Server 2003. Terminal Services is capable of directly hosting compatible multi-user client desktops running on a variety of Windows-based and non Windows-based computers. Standard Windows-based applications do not need modification to run on the terminal server, and all standard Windows Server 2003-?based management infrastructure and technologies can be used to manage the client desktops. In this way, corporations can take advantage of the rich choice of applications and tools offered by today’s Windows operating system environment.

Terminal Services depends on, or interacts with, the following technologies:

• RDP Protocol - On the server, RDP uses its own video driver to render display output by constructing the rendering information into network packets using RDP protocol and sending them over the network to the client. On the client, RDP receives rendering data and interprets the packets into corresponding Microsoft Win32 graphics device interface API calls. For the input path, client mouse and keyboard events are redirected from the client to the server. On the server, RDP uses its own virtual keyboard and mouse driver to receive these keyboard and mouse events.
• Terminal Server Interactions with RDP
  
  

Terminal Services Architecture

Terminal Services consists of four components: the Windows Server 2003 multi-user kernel, the Remote Desktop client, the Terminal Services Licensing service, and Session Directory Services. Specifically:

Multi-user kernel. The multi-user kernel extensions, originally developed for Windows NT 4.0 Server, Terminal Server Edition, have been enhanced and fully integrated as a standard part of the Windows Server 2003 family kernel. These are resident on the server at all times, regardless of whether Terminal Services is enabled or not.

Remote Desktop client: The client software is an application that establishes and maintains the connection between a client and a server computer running Terminal Services.

Terminal Services Licensing service: This system allows terminal servers to obtain and manage terminal server client access license (TS CAL) tokens for devices and users connecting to a terminal server.

Session Directory Services: The session directory (SD) keeps a list of sessions indexed by user name, and allows a user to reconnect to the terminal server where the user’s disconnected session resides and resume that session.

Terminal Services Architecture

Installtion of Citrix Presentation 4.5 

Citrix Presentation Server 4.5  Installation