Terminal Services Execution
When a user tries to access a terminal services resource, the
device completes the steps in the page to initiate and intermediate
the terminal services session as described in Table 1.
Table 1: Terminal Services User
Experience
| Options |
Your Action |
The device checks for a Java client
|
Ensure that you have an RDP client on the system (to
access a Windows terminal server) or an ICA client (to access a Citrix
Metaframe server or server farm). This enables a terminal service
session. The RDP clients come in both Windows and Java versions and
enables you to run an application on the server while only transmitting
keyboard, mouse, and display information over the network.
The device enables to upload a Java version of the RDP or ICA
client through a terminal service resource profile (but not role).
If you have uploaded a client to the device and specified that the
device always use it to run your users’ terminal sessions, the
device launches the specified Java client.
|
If necessary, the device checks for a Windows client
(Citrix only)
|
Ensure that you have uploaded a Java client to the device,
else the device checks for a Windows version of the ICA client. If
the device cannot find a Windows ICA client, it installs the version
you specified in the Users > User Roles > Role >Terminal Services > Options page.
|
The device checks for the terminal services proxy
|
Ensure that you have a Juniper Windows Terminal Services
proxy on your system or a Juniper Networks Citrix Terminal Services
proxy, to intermediate a Windows or Citrix session. The device checks
for the appropriate proxy on the user’s computer, and if it
cannot find it, the system installs a new one. Depending on the user’s
rights, the device either uses an ActiveX component or Java component
to install the proxy.
|
The proxy tries to invoke the Windows client
|
Ensure that the device has confirmed that a proxy is
installed on the user’s computer. This enables the proxy to
attempt to invoke the Windows RDP or ICA client. If successful, the
client initiates the user’s terminal services session and the
proxy intermediates the session traffic.
|
The proxy tries to invoke the Java client
|
Ensure that you have uploaded a Windows client to the
device through the terminal services resource profile. If the Windows
client is not present on the user’s machine (for instance, because
it was deleted or because the user does not have the proper privileges
to install it), the device uses the uploaded Java applet to launch
the session.
As part of the installation, the device prompts you whether
if the you want to always use the Java client or only for this session.
The device then stores the user’s preference as a persistent
cookie. Once the Java client is installed, the client initiates the
user’s terminal services session and the proxy intermediates
the session traffic.
|
 |
Note:
The following options in the New Terminal Services Sessions
window do not apply to remote desktops launched in the following order:
- Client port
- Authentication settings
- Start application settings
- Connect Devices settings
- Display Settings
|
Published: 2009-08-20