Administrator Guide

5 Click Add Firmware File.
The Add File dialog box is displayed.
6 Browse and select the downloaded rmware le. Enter an appropriate description.
7 Click Upload.
The ThinOS Lite rmware le is uploaded, and the rmware le is listed on the Apps & Data - ThinOS Lite OS Image Repository
page.
8 Select the check box that corresponds to your ThinOS Lite rmware le.
9 On the Groups & Congs page, select a custom group, and click Edit Policies > ThinOS.
The Select ThinOS Lite Conguration Mode screen is displayed.
10 Click Advanced Conguration.
11 In the Device Conguration pane, click Firmware Upgrade, and then click Congure this item.
12 From the Platform type drop-down list, select your thin client model.
13 From the Firmware to auto deploy drop-down list, select the rmware le that corresponds to your thin client model.
14 Click Save & Publish.
The thin client restarts, and the rmware version is upgraded.
System conguration and deployment
• ThinOS BIOS policy can be congured using Wyse Management Suite Console, Wyse Management Suite group INI, Wyse Management
Suite advanced settings and FTP INI. Dell recommends that you use any one of the methods to congure the BIOS policy. Setting the
BIOS policy simultaneously using dierent methods may cause a policy mismatch, and the device reboots repeatedly. This reboot loop
issue is observed when you select the reboot immediately option in the BIOS policy settings section on the Wyse Management Suite
console.
• All the installed packages are deleted when you update the ThinOS Lite version between major releases—2.5 to 2.6—using FTP, WDM,
or Wyse Management Suite.
Solution for updating rmware using FTP and WDM—Ensure that you have set the PKG install parameters in the WNOS.ini, and the
pkg les are uploaded in the directory. After the device reboot, the packages are re-installed automatically.
Solution for updating rmware using Wyse Management Suite—Wyse Management Suite App policy works only once after the policy is
created. The deleted package cannot be reinstalled using the same policy. Dell recommends that you create a new App policy to install
the package after the rmware update is complete.
• WDM vulnerability is xed in this release. You must congure either the DHCP or the DNS option/record of the WDM server ngerprint
to automatically fetch and validate the ngerprint before checking in to the WDM server. However, there is no impact to the ThinOS
Lite device functionality if you do not to congure the ngerprint validation environment. For more information about how to set up
ngerprint using WDM, see the Dell Wyse ThinOS Lite Version 2.6 Administrator's Guide at www.dell.com/support.
How to set up ngerprint using Wyse Device Manager
To set up your ngerprint using WDM, do the following:
1 Export the WDM server certicate from the WDM server that you want to access.
2 Extract the ngerprint value from the WDM certicate in the required format.
You must use a system with OpenSSL installed. OpenSSL can be used to extract the ngerprint in required format from the WDM
certicate itself.
The ngerprint is generated from the following command:
openssl x509 -in <your certificate name>.crt -pubkey -noout | openssl pkey -pubin -outform
der | openssl dgst -sha256 -binary | openssl enc -base64
NOTE
: If cert.crt is in DER format instead of the PEM format, you must add -inform to the rst command. The
certicate supports SHA256 in base64 encoded format.
3 Congure either the DHCP option or the DNS TXT record.
• If you want to use the DHCP option, congure the following option tags dened in the DHCP server:
Before working on ThinOS Lite
11