ThinOS 10 2602 Released

Question

· Dell ThinOS Migration Guide - This guide provides instructions to migrate from ThinOS 9 (2408 or later version) and Dell Hybrid Client to ThinOS 10 using Wyse Management Suite 5.0 or later.

Highlights

Expanded Repurposing and Conversions
Expanded Hardware Compatibility List (HCL) including Dell Pro Max Micro (Workstation class device supporting 4+ monitors) and Tangent medical devices for healthcare
Windows IoT to ThinOS 10 automated conversions
Qualifying new Dell Ultrasharp 52 Thunderbolt hub monitor and new Dell Pro SD/WD 25 docks
Improved legacy repurposing for non-Dell devices via software TPM

Please refer to the ThinOS 10 Hardware Compatibility List (HCL) for the ThinOS10 supported platform list.

Manageability and Security Enhancements

· Dramatically improved peer-to-peer (P2P) performance – faster and better error handling

· Remote Screen captures

· Input validation to ensure username fields are not vulnerable, making devices more secure

· Dynamic host file updates (Add/Update/Delete)

· FIDO2 NFC w/Yubikey

New Features, Improvements and Additions

· Now supporting WWAN connections (only on devices with Qualcomm modems and physical SIM cards)

· Improvements to App Builder – including Auto Launch (prior to broker sign in), better logging/debugging and support for environment variables from WMS

· NVIDIA GPU Support for 4x4K monitors on applicable HW (limited to older Precision workstation models)

· Continued focus on customer feature requests and bug fix activity

DP2811 · Answer

Anyone else seeing a generic system event like:" Generic Audit event received from WTmacaddress - Vulnerable characters were identified in the received WMS payload."

Generally after a restart we are see this event on all our terminals updated to 2602.

DELL-Scott H · Answer

https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=7jp0t&oscode=thn10&productcode=wyse-thinos-maintenance This build, 2602.10.0573, 2602    released on 3-9 resolved this.

Franz1 · Answer

Dear Community,Unfortunately, we are unable to successfully upgrade from ThinOS 2511 version 10.0380 to ThinOS 2602 version 0555 or 0573 on Dell OptiPlex 3000 thin clients.In both cases, there is no communication with the Wyse Management Suite after the upgrade.Could you please let us know the cause? The URL https://www.dell.com/support/kbdoc/de-de/000444141/dell-thinos-10-ist-nach-dem-upgrade-auf-firmware-2602-nicht-funktionsf%C3%A4hig did not resolve the issue.Thank you very much and best regards

DELL-Scott H · Answer

@Franz1​  Best to open a support case for formal diagnostics and debugging.  1) What do you see in the event logs? 2) Try doing a 'Soft reset' on the device prior to sending the upgrade package down.

Franz1 · Answer

@DELL-Scott H​  1) The event logs confirm that the firmware has been installed and show no errors. 2) The reset was successful. Can the issue be resolved in a newer version?

DELL-Scott H · Answer

@Franz1​ So, A soft reset allowed the device to communicate with WMS and work?  I have seen this in a few cases which is why i recommended it.  If you are able to reproduce it (it has been tough to narrow down) i suggest opening a case to document it for engineering.

jcloredo · Answer

I'm having a similar experience. I'm on an optiplex 3000 that meets all the requirements.

We upgraded from 2511.10.0329 to 2602.10.0573.
Even though I can see if from WMS cloud portal, I can't perform a soft or full reset. When I try to Check-in to "Validate key" from the central configuration it says "checked in to WMS server" but in the logs it says it's trying but never really checks in.
The admin policy tool from the device itself just loads a blank page. When I try to perform a simple restart, the device just shows a loading window and never reboots. Not sure what to do next. Any insights?

DELL-Scott H · Answer

@jcloredo Can you check that the time and date is correct?  We have observed a few cases where this occurs they are off.

jcloredo · Answer

I performed a reset by hitting the G key at startup and that got it back to the default Device Policy.  Once it was there it shows the right Firmware and everything else is checking in.  As soon as I move it to the ThinOS 10 Group Policy I created, the device goes into this state and cannot do anything. The date and time look good, but the device is pretty much useless. We did upgrade other devices, and all are in the same state.

DELL-Scott H · Answer

@jcloredo So it only fails after moving to your policy group?

Review your Bluetooth settings against this known issue
1. https://www.dell.com/support/kbdoc/en-so/000444141/dell-thinos-10-is-inoperable-after-firmware-2602-upgrade?msockid=17afd603392c69380461c3cb38b868c1
Create a policy in a group with just a few settings, does it happen in that group?

Wyse ThinOS

ThinOS 10 2602 Released

Was this post helpful?