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

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

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

Select 2X ApplicationServer XG  for complete product installation.

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.

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

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.

From the Start menu > Administrative Tools>Terminal Services Configuration

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.

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

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.

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.