
Dell Wyse ThinOS 9.1.3129, 9.1.3112, 9.1.2101, and 9.1.1131 Administrator’s Guide
Configure the EPOS headset settings
ThinOS enables you to configure and manage EPOS headsets that are connected to the thin client. Use Wyse Management Suite or Admin Policy Tool on ThinOS to configure the headset settings.
Steps
-
Create a text file with the EPOS Connect configuration details.
NOTE:Ensure that you specify a valid tenant ID and a tenant URL. Log file configuration is optional.For example:
log_filepath = /tmp/epos-connect/Logs/ tenant_filepath = <filepath> log_output = CONSOLE log_level = TRACE proxy_setting = <proxyserver> tenant_id = <id> tenant_url = <url>
Table 1. EPOS Connect configuration detailsEPOS Connect configuration details Command Description log_filepath Specifies the log file path. tenant_filepath Specifies the tenant configuration and device settings file path. log_output Specifies where the log entries are to be saved. Default is set to CONSOLE. Change the value to FILE if you want to write log entires to a log file. log_level Specifies the log level. Default is set to OFF. Change the value to one of the following options as per your preference: - TRACE
- DEBUG
- INFO
- ERROR
- WARN
- EXCEPTION
- OFF
proxy_setting Specifies the proxy server. tenant_id Specify the tenant ID. tenant_url Specify the tenant URL. - Open the Admin Policy Tool on ThinOS or go to the ThinOS 9.x policy settings on Wyse Management Suite.
- In the Advanced tab, expand Peripheral Management, and click Device Headset Settings.
- Click the Enable EPOS Connect toggle switch to enable the option.
- Browse and upload the configuration file.
- From the drop-down list, select the uploaded configuration file.
- Click Save & Publish.
- Restart the thin client for changes to take effect.
Next steps
- Start the ThinOS client.
- Connect the EPOS headset to your thin client.
NOTE:It is recommended that you use the silent deploy type during the firmware upgrade process.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\