Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING SECURE ACCESS DEVICES GUIDE REV 01 Manual page 81

Table 14: Terminal Services User Experience (continued)
Options
The proxy tries to invoke the
Java client
Related
Documentation
Copyright © 2010, Juniper Networks, Inc.
Chapter 7: Configuring Terminal Services Using Remote Access Mechanism
Your Action
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
Terminal Services User Experience on page 61
Configuring Terminal Services on a Secure Access Device User Role (NSM Procedure)
on page 52
63