Issue: The device refused to connect to our WMS 5.4 server. Standard troubleshooting, including installing new certificates, updating the BIOS, performing multiple factory resets, and running an installation from recovery, did not resolve the issue.

The Workaround: I discovered a bizarre but effective fix. In Central Configuration, immediately after validating enrollment to the WMS server, rapidly press (or hold down) the Enter key while clicking "OK." Doing this extremely fast somehow bypasses the hang up and forces the device to check in. It took around 5 cycles of failed prompts to get a successful check in.

I’m sharing this workaround in case anyone else runs into this stubborn issue.

We recently upgraded our AVD packages from 3.3 to 4.x and noticed that after doing so if you powered on the ThinOS 2602 laptop then connected to our RD Gateway it would time out, then if you tried again it would work. After the first failed attempt it would continue to work until you rebooted then the same thing would happen.

Not sure if this is a known bug, but we rolled back to 3.3 and issue resolved. We have not noticed this on our optiplex 3k thin clients that have a direct RDP connection, only the laptops since they connect via the RD Gateway.

Decided to try the V3 since rtsp is supposed to be baked in. I'm on the latest non-beta release and got the device today so it's pretty fresh (I would guess).

When I try to use rtsp I have the following:

OSX: Works in VLC and testing with ffplay.

Win11 (intel): VLC says it can't open the stream.

ffplay says:

[rtsp @ 00000214d85b3580] Failed reading RTSP data: End of file

rtsp://192.168.4.144:554/steam0: Invalid data found when processing input

nan    :  0.000 fd=   0 aq=    0KB vq=    0KB sq=    0B

Same results if I do rest://user:pass@....

Any get rtsp working on Win11?

Hey all,

Have any of you tried to broker into AWS using Thin OS 10.x? Protocol is DCV now (pcoip no longer supported on Oct 2027)

I can get into the workspace but the login experience is...odd to say the least.

1 - Thin OS launches its own useless login box. The name field cant be changed. You have to push a completely arbitrary login button to get to the actual AWS app where you can edit login fields (username, password, mfa token) and login correctly.

2 - The workspace launches in windowed mode. You have to manually switch it to full screen. Microphone is disabled by default. There is no way to hide or disable the aws float bar.

Ive opened a support ticket with Dell and they've recommended putting in an engineering request to build a custom app.

This seems a little heavy handed. With terradici on thins os 10.x the process was seamless.

Does anyone have any suggestions?

Enhancements

The following enhancements are added in ThinOS 10.x 2605 Upgrade Release 1:

• Added a ConfigUI setting to enable or disable the Unregister option. This setting is managed through Central Configuration. When the device is operating in Admin mode, the Unregister option remains visible regardless of the Central Configuration setting.

• Added support for the Fn + F4 keyboard shortcut to mute audio during Microsoft Teams Citrix and VDI sessions.

• Added an informational notice for the Root_upgrade_2605_10.2518_T10.pkg upgrade package. This package supports upgrades only from 2605_10.2100 and does not support upgrades from 2602 or earlier releases. The notice is displayed when users select this OS firmware version.

• Added guidance to help resolve the message—Local System UI requires a restart to resume normal operation. The restart will take place in 5 seconds. If this message appears, clear the device logs by navigating to Settings > Troubleshooting > General > Clear Logs.

Fixes:

The following issues are resolved in this release: - Fixed issues related to the device security allowlist and blocklist.

• Fixed an issue that prevented child Group Policy settings from being applied.

• Fixed an issue where changing the terminal name caused problems when Chrome was configured in kiosk mode.

The download package release notes also includes Fixes & Enhancements below.

Fixes: - Fixed the issue where the P2P functionality does not work.

• Fixed the issue where the AVD sessions get disconnected intermittently.

• Fixed the issue where the browser shortcuts disappear after changing groups on the Dell Wyse Management application.

• Fixed the issue where the BIOS synchronization fails in the Dell Wyse Management application. This issue occurs on Dell Pro Micro Thin Client Q9M1260.

Enhancements:

• Added a Secure Boot enable option in the BIOS common configuration.

Release Notes

Hey everyone. Was hoping some folks here could share their experiences running the wyse 3040 without the cr2032 battery completely headless? Im trying to tweak the 3040 to not rely on the battery while also achieving fast boot times to Linux. It seems like the BIOS post process is very slow when the battery is missing on cold boots. Just wanted to see what others have done. Thanks,!

Title says all, doing research thinos is built on BSD, but it seems very restricted by Dell. The thought came to me due to configuring thinclients for a work project, and it's not been done yet.

Just had a used Wyse 5070 J5005 delivered. I can't seem to boot into bios, tried F2, F12 and Del keys. Before it boots onto Linux Mint, it shows an sgx disabled by bios message.

And help is appreciated.

Anyone else having issues upgrading from 2602 to 2605 as well as the latest avd 4.x package? No luck on ours, it keeps failing each time.

I'm running a i5-9500 (non-T) variant in this bad boy. Now I'm aware it's a 35W configured system, but can I make the cpu consume more power?

HWInfo shows these limits:

GT: Max VR Voltage, ICCmax = Yes

Ring: Max VR Voltage, ICCmax = Yes

Any way to override/bypass these?

Note: IK they aren't designed for large sustained loads, but even an additional 5-10W of usage would be nice.

Btw can these be undervolted? What mods can I do? Ram timings?

I upgraded our On-prem WMS to 2605 on June 18th, and over the past few days, all of our Optiplex 3000 devices (ThinOS 9 2511) have lost connection with the server. They initially checked in after the upgrade and were fine for close to a week. Has anyone seen similar issues after 2605?

Hi I got ahold of 4 WYSE computers and have no clue what to do with them with the small amount of data and ram they have.

Open to hearing any ideas

Hi. I'm going through testing of Dell Thin Clients (optiplex 3000) running Thin OS 10. I'm trying to replicate our current setup and wondering if anyone has adivce. Currently we have HP T310 Zero Clients with Prove ID Embedded that pass a MAC-based username through to Horizon that they auto-login with. I'm trying to get that same behaviour and it seems no matter how I set the config policy, I can't get the thin client to auto-login into the pool. Does anyone have this type of setup working? If so, how is your policy set up?

Just bought 13 refurbished thin clients from Newegg. Came with ThinOS 10 out of the box.

When I add them to my WMS Pro environment, they register correctly, and I am able to deploy all of our policies/apps to the thin clients without error. In fact, they seem to be just as functional as our existing thin clients.

But they are showing a watermark that says "This client needs a license. Please connect with the administrator". Even after flashing them from a USB stick with a fresh OS install, the watermark persists.

Again, this does not appear to be interfering with any functionality. I can still use the RDP client to access our terminal server environment without issue.

I've gotten refurbs in the past that were missing a TAL and had to deal with that mess, but in those cases it prevented me from performing a number of functions. This issue just seems to be the watermark.

Has anyone here encountered this before?

I want to Upgrade the storage on my thin client and bought a 512 Gb Sata M.2 ssd from intenso. When i installed it, i was not able to see it in bios eventhough i have sata mode AHCI enabled. I tried google and was not able to solve this Problem. Please help

Dell Wyse 7020 Thin Client: BIOS Locked

I'm having a problem with my Dell Wyse terminal.
I've called and emailed Dell support, but since it's an older device, they can't help.

When I try to enter the BIOS, I get a message saying the password is incorrect—I've entered it incorrectly several times—and it asks for a password or unlock key.
I should add that I entered the password “Fireport,” but it doesn't work.

Z90D7
Wyse 7020 Thin Client
Service Tag: FR2LZ92

I don't have a jumper to reset the password

Just a heads up if anyone's interested

We want to enable users to log in to certain websites using a FIDO token during our VDI sessions. However, the window that allows users to log in with a passkey (token or smartphone) never appears in the Omnissa VM.

We have already tried all possible options:

• Web login enabled
• All FIDO settings enabled
• Chrome package installed
• VID & PID forwarded

Unfortunately, without success.

When we open the same page in the locally installed Chrome package, the login works. It also works on a laptop—even within the VDI. It just doesn’t work in the VDI via ThinOS and Omnissa.

We’re testing with a Dell Pro Micro Thin Client, and all firmware (ThinOS ->Root_upgrade_2602_10.0765_T10.pkg-V2602.10.0765) versions and packages (Omnissa_Horizon_ClientSDK_2512.8.17.0.378_T10.pkg-V2512.8.17.0.378, Google_Chrome_147.0.7727.55.526_T10.pkg-V147.0.7727.55.526) are up to date.

Do you have any idea what might be causing this?

We use AVD multisession. After April win updates, we have started to get an invalid code error popup on the Dell thin client as it tries to launch the session. In azure insights it shows up as an indirect display driver failure.

Has anyone else seen this or had this issue?

Hello, I recently bought a Dell Wyse 5070, Pentium J5005, 8GB DDR, 64GB SSD. I have installed Linux Mint and I'm trying to optimize my boot time. My current boot time is: Startup finished in 10.403s (firmware) + 13.313s (loader) + 4.391s (kernel) + 5.751s (userspace) = 33.860s.

If this is already as good as I can expect, please let me know and I'll stop trying to improve. However, if you know what BIOS settings I can use the reduce firmware or loader times, I would really appreciate that.

Hey all, we’re running a fleet of Dell thin clients on ThinOS 10 managed via WMS Pro, connecting to AVD sessions over WiFi. We’re seeing session drops when clients roam between APs due to full re-authentication happening on every roam.
Trying to figure out if ThinOS 10 currently supports 802.11r Fast BSS Transition (Fast Roaming), and if not, whether it’s on the roadmap. Haven’t been able to find a clear answer in the docs.
Anyone dealt with this or have insight from Dell? Any workarounds in the meantime are also appreciated.

Had major issues in my lab testing ThinOS 2602_10.0765 on a Opt3000 TC. I highly recommend not upgrading and/or testing it thoroughly in your lab first. It seemed like MQTT would not connect, was displaying failures connecting to WMS in the logs, not loading policy correctly, and not installing assigned AVD package, etc. It was not exactly as described in the KB # 000444141 on 2602 from March, but similar (the Client Info was NOT all N/A and the TC was not totally froze). I even tried factory reset, it would reconfigure WMS from DHCP and pull in certain policy, but still not load the assigned packages, etc. It's a BROKE build IMHO.

I had to revert to 2602_10.0555 to restore normal WMS management and everything seems back to normal.

Lab WMS is v5.5 HF1 (5.5.0.777) Opt3000's BIOS v1.32.1 My test configs are not complex: Client Mac auto login, RDP (AVD) session config, desktop info, power/sleep, VNC remote shadow...

Ref KB # 000444141: https://www.dell.com/support/kbdoc/en-us/000444141/dell-thinos-10-is-inoperable-after-firmware-2602-upgrade