Administrator Guide

The following are valid working conditions for multiple audio:
• Using Citrix HDX generic audio
1. Select the audio device as PC Mic and Speaker.
2. Configure the speaker or microphone.
3. For secondary ringer, select the audio devices excluding the devices that are already selected.
• Using Citrix RealTime Multimedia Engine (RTME)
1. Select the audio device as HID headset with PC Mic and Speaker.
2. Set PC Mic and Speaker to configure the speaker or microphone.
3. For secondary ringer, select the audio devices excluding the devices that are already selected.
The following scenarios must be considered during multiple audio settings:
• ThinOS default audio is set to the latest plug-in audio device.
• Session default audio is set to the ThinOS default audio. However, this option can be changed.
• Restart Skype for Business/Lync client after you plug in and remove the device.
• ICA RTP audio is supported with multiple audio connections.
• During a call, the audio device settings can be switched without plugging in or plugging out the device.
• Multiple audio can be shared across sessions.
Configure ICA connections
To configure the 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:
a) Server or Published Application—Select the type of connection to which the settings apply.
b) Connection Description—Enter the descriptive name that is to be displayed in the connection list (38 characters maximum).
c) Browser Servers—Enter a delimited (comma or semicolon) list of IP addresses or DNS-registered names of ICA servers that
contain the master browsers list, or that can direct 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 that is 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.
d) Host Name or Application Name (title depends on the Server or Published Application option that is 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 that are 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. However, it tries to resolve the name without using the default value.
e) 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 enables 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.
70 Configuring the connection brokers