Administrator Guide

How to set up fingerprint using Wyse Device Manager
To set up your fingerprint using WDM, do the following:
1. Export the WDM server certificate from the WDM server that you want to access.
2. Extract the fingerprint value from the WDM certificate in the required format.
You must use a system with OpenSSL installed. OpenSSL can be used to extract the fingerprint in required format from the
WDM certificate itself.
The fingerprint 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 first command. The
certificate supports SHA256 in base64 encoded format.
3.
Configure either the DHCP option or the DNS TXT record.
● If you want to use the DHCP option, configure the following option tags defined in the DHCP server:
○ Option ID—200
○ Name—WDM_Fingerprint
○ Type—String
● If you want to use the DNS TXT record, enter the name as WDM_Fingerprint, and provide the fingerprint string value.
NOTE:
If the DNS TXT record for fingerprint cannot be retrieved, the device fetches the values from the DHCP scope
option. If the fingerprint certificate is already available, the device checks in to the WDM server. If the connection fails, the
failure logs are registered on the ThinOS client.
Automating updates and settings using central
configuration
ThinOS is centrally managed and configured using INI files to automatically push updates and any desired default configuration
to thin clients in your environment. This section describes how to set up your environment to provide your thin clients running
ThinOS with automatic updates and configurations in three simple steps. If no INI files are detected, you can use local dialog
boxes on each thin client to configure the settings. Many of these locally configured settings such as resolution, mouse, and
keyboard are saved on ThinOS to persist after reboot. However, once INI files are detected, rebooting the client causes ThinOS
to become stateless, and ignores the locally configured settings after a reboot. The settings contained in the INI file are used.
NOTE:
Dell Wyse thin clients do not require device management software. They are configured to obtain their IP address,
as well as the location of firmware and configuration instructions, from a DHCP server. However, you can use Wyse
Device Manager (WDM) or Wyse Management Suite for a more hands-on management of your thin clients. For information
about configuring your thin clients to communicate with a WDM server or Wyse Management Suite, see the related INI
parameters in Dell Wyse ThinOS INI Guide.
How to set up automatic updates and configurations
For a thin client running ThinOS to successfully access INI files and update itself from a server, you must set up the server with
the correct folder structure where the INI files and other update files are located, direct the thin client to the server, and then
reboot or start the thin client
Once DHCP and servers are configured and available, the thin client checks (at each boot up) to see whether or not any
updates are available on a predefined server DHCP Option #161 specifies the server URL, DHCP Option #162 specifies the root
path to the server. If updates are available, the updates are automatically installed.
20
Before working on ThinOS