Administrator Guide

3. Select a Bluetooth device that is not connected, and click Connect. If the Bluetooth device is connected successfully, the
status is displayed as Connected in the Bluetooth window. The following are the functions that are available:
● Scan—All Bluetooth devices enter into Page Scan mode. Different Bluetooth devices enter into the Page Scan mode at
different instances such as when a specific button is pressed three times or a specific button is pressed and held until
the LED turns blue.
● Connect—Select a particular Bluetooth enabled device, and click Connect to connect the selected device to the thin
client. If the Bluetooth device is connected successfully, the status is displayed as Connected in the Bluetooth window.
● Remove—Select a particular Bluetooth device, and click Remove to disconnect and remove the device from the list.
● Auto Connect function—The Auto Connect function is designed for HIDs.
○ ThinOS has no HIDs connected such as USB or Bluetooth HIDs.
○ The Bluetooth HIDs are configured as Page Scan mode.
When you start the ThinOS client, the Bluetooth HIDs can connect to ThinOS automatically without scanning or pairing
operations. The Bluetooth HIDs automatically reconnect after you restart the ThinOS client.
● Reconnect function—The Reconnect function is designed for HIDs and headsets.
When you restart the system with the Bluetooth device (HID/headset) that is already paired and connected, the
Bluetooth device automatically reconnects within a few seconds.
For example, you can hover the Bluetooth mouse, and then click a few times for the Bluetooth mouse to reconnect
successfully. The Bluetooth headset reconnects automatically, but might require you to manually close or reopen the
device on certain occasions.
4. Click OK to save your settings.
Secure Digital cards
You can plug in a Secure Digital (SD) card into the Wyse 5470 Thin Client and import a certificate file to the thin client. The SD
card works as a storage device.
Configuring the printer settings
Use the Printer Setup dialog box to configure network printers and local printers that are connected to the thin client. Through
its USB ports, a thin client can support multiple printers. If more than one printer is to be used and another port is not available
on your thin client and the port that is to be used must be shared with a USB modem converter, connect a USB hub to the port.
Based on the Citrix Host Printer Policy settings, ThinOS 9.0 supports the following:
● Device-Specific Printer Driver support—This method allows Citrix hosts to automatically create client redirected printer
queues based on the peripheral management printers settings of the ThinOS client. The following details are used by the
host print manager to automatically create the printer queues:
○ Name—Printer queue name.
○ Printer ID (Printer Identification)—Printer driver name.
● Citrix Universal Print Driver support—This method allows Citrix hosts to automatically create printer queues based on
the peripheral management printers settings of the ThinOS client. The following details are used by the host print manager
to automatically create the printer queues:
○ Name—Printer queue name.
○ Class—Printer class that is associated by the Citrix host registry to a printer-specific driver name.
NOTE:
ThinOS 8.6 supports the association of PS, PCL5, and PCL4 classes. However, ThinOS 9.0 associations are
limited to the PS class only.
Limitations
● The ThinOS solution to support the client printer redirection functionality is limited to Type 3 printers only. However, the
solution is subject to changes in the future according to the changes made by Citrix.
● After you connect a USB printer to the thin client, the Printer ID information is not automatically displayed in the ThinOS
client Peripheral Management Printer settings menu. This limitation will be resolved in future ThinOS releases.
● ThinOS supports only PS class when using the Citrix Universal Print Driver policy to automatically create ThinOS client
redirected printers. PCL5 and PCL4 classes are not supported. This is a Citrix limitation.
Configuring the thin client local settings
113