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 depends on the installation you
selected.
Figure 33 - 2X Client Gateway, 2X Publishing Agent, 2X
Redundancy Service and 2X Terminal Server Agent, 2X VDS Agent
2X Publishing Agent
- provides Load Balanced Applications and desktop publishing.
2X Terminal Server Agent
- provides information to 2X ApplicationServer and 2X Load
Balancer.
2X Redundancy
Service - provides redundancy to 2X ApplicationServer and
LoadBalancer.
2X Client Gateway
- tunnels all traffic needed by 2X applications on a single port and
provides secure connections.
2X VDS Agent
– provides information to the 2X VirtualDesktopServer
NOTE:
All users who are connected via the 2X Client Gateway will be disconnected if
the 2X 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 being used by other local
services.
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. For example, you can set different session time limits
for each user when you use the Terminal Services extension to Local Users and
Groups. Using Terminal Services Configuration, you can only set session time
limits on a per-connection basis, which means the same time limit applies to all
users who log on to the server using the connection.
Launch “Terminal Services Configuration” from
the Administrative Tools Submenu (in the Start menu).
Figure 34 –Configuring Terminal Services
Connections
Restrict
each user to one session
To conserve server resources and simplify reconnecting to
disconnected sessions, you can restrict each user to a single session. To change
this attribute select “Server Settings” and double-click the
‘Restrict each user to one session’ option. Ticking the check box in
the resulting dialog will enable the restriction, and therefore enable
reconnections to previously-disconnected user sessions. This feature is
configurable in the “Load Balancing” page in the 2X
ApplicationServer & LoadBalancer Console.
Logon
Settings
Figure 35 - 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 ApplicationServer 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 36 – Environment
To be able to launch the seamless published applications
from the 2X ApplicationServer, 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.