Dell Wyse ThinOS Version 8.5 Administrator’s Guide

Configuring ICA connections

1. From the desktop menu, click System Setup, and then click Remote Connections.
   The Remote Connections dialog box is displayed.
2. In the Broker Setup tab, from the drop-down list, select the Broker type as None.
3. Click ICA connection protocol, and click Configure.
   The Default ICA dialog box is displayed.

   NOTE: Default ICA is always used for direct connection to a published application and not for StoreFront or PNAgent.
4. Click the Connection tab.
   To configure the ICA connections, do the following:

   

   1. Server or Published Application—Select the type of connection to which the settings apply.
   2. Connection Description—Enter the descriptive name that is to appear in the connection list (38 characters maximum).
   3. Browser Servers—Enter a delimited (comma or semicolon) list of IP addresses or DNS-registered names of ICA servers that contains the master browsers list, or that could refer to another server that contains the list.

      The master browsers list is generated automatically by a browsing program on one of the ICA servers (selected by negotiation between servers). It is used to provide the information displayed in the Server Name or IP box. No entry is needed if the list is on an ICA server in the same network segment as the thin client. No entry is necessary if the connection is to a server, or if the server name or IP contains the IP address of the server.

   4. Host Name or Application Name (title depends on the Server or Published Application option selected)—You can enter a delimited semicolon or comma-separated list of server host names or IP addresses, or you can select from the list of ICA servers or published applications obtained from the ICA master browser. You can also use Browse next to the box to make the selection you want.
      If you enter a delimited list of servers, the thin client will attempt to connect to the next server on the list if the previous server attempt fails. If you use the list and the selected connection fails, the thin client will attempt to connect to the next one on the list.

      NOTE:The Host Name may be resolved using one of three mechanisms: ICA master browser, DNS or WINS. Master browser is the only mechanism that can resolve a published application unless manual entry is made in DNS for the application. DNS uses the default domain name in the network control panel to attempt to construct an FQDN but will also try to resolve the name without using the default.
   5. Encryption Level—Allows you to select the security level of communications between the thin client and the ICA server.
      Basic (the default option) is the lowest level of security. Basic allows faster communication between the device and the ICA server because it requires less processing than the higher levels of encryption.

      NOTE:The encryption selection applies to the security of communications between the thin client and the ICA server only. It is independent of the security settings of individual applications on the ICA server. For example, most web financial transactions require the thin client to use 128-bit encryption. However, transaction information could be exposed to a lower level of security if the thin client encryption is not also set to 128–bits.
   6. Use HTTP for browsing—When selected, the thin client, by default, uses HTTP when browsing.
   7. Alternate address via firewall—When selected, the thin client uses an alternate IP address returned from the ICA master browser to get through firewalls. Used for the Windows log on when the connection is activated.
   8. Display Resolution—Select the display resolution for this connection.

      If you select the Published Application option, the Connection Display allows you to select the Seamless Display Resolution option.

      Colors — Select the color depth of the ICA session. If High Colors (16 bits) or True Colors is selected and the ICA server does not support this color depth, the thin client renegotiates the color depth to the lower value, for example, 256 Colors [8–bits].

   9. Window mode and Full screen mode—Select the initial view of the application and desktop in a windowed screen or full screen.
   10. Auto-connect on start-up—When selected, automatically connects the session on start-up.
   11. Reconnect after disconnect—When selected, causes the thin client to automatically reconnect to a session after a non operator-initiated disconnect. If selected, the wait interval is that set in the Delay before reconnecting box (enter the number of seconds 1–3600) or the user profile for yes (20 seconds) or seconds. The default is 20 seconds, if there is no INI file description of this connection, or is a Stand-alone user, or simply omitted.
5. Click logon tab, and use the following guidelines:

   

   1. Logging on area—Enter Login User name, Password, Domain name, and Logon Mode.
      If the Login User name, Password, and Domain name boxes are not populated, you can enter the information manually in the ICA server login screen when the connection is made:

      • Login Username—Maximum of 31 characters is allowed.
      • Password—Maximum of 19 characters is allowed.
      • Domain Name — Maximum of 31 characters is allowed.
      • Logon Mode — Select User-specified credentials, Smart Card, or Local User.
   2. Start Command area—Server Connection Option Only — This area is disabled for a Published Application option.
      Application (127 characters maximum) and Working Directory (63 characters maximum)—Enter an initialization string and arguments, including an associated working directory, that you want to start automatically on the server when the connection is made.
6. Click Options tab and use the following guidelines:

   

   1. Autoconnect to local devices—Select any options (Printers, Serials, USB, Smart Cards, and Disks) to have the thin client automatically connect to the devices.
   2. Allow font smoothing—When selected, enables font smoothing (smooth type).
   3. Optimize for low speed link—When selected, allows optimization for low-speed connections, such as reducing audio quality and/or decreasing protocol-specific cache size. Intended for a connection spanning a WAN link or using dialup.
   4. Enable session reliability—When enabled, session reliability allows a user to momentarily lose connection to the server without having to re-authenticate upon regaining a connection. Instead of a user’s connection timing out after X seconds, the session is kept alive on the server and is made available to the client upon regaining connectivity. Session reliability is most relevant for wireless devices.