ThinOS 8.6 to 9.0 upgrade

The Merlin image is not used to provide the firmware update.  

The following video will help, https://youtu.be/PXvZN9aWLEI

As will the documentation https://topics-cdn.dell.com/pdf/thinos9_mg_en-us.pdf

Keep in mind that 9.0 is only available for Non-PCOIP devices in this initial release, and only for supported platforms.

I had problems with this also.

You need to upload the Base Image file in the Webinterface under ThinOS, not under the new ThinOS 9 section.
It seems the upload firmware button in the ThinOS9 section only allows pkg files.

The update could then be installed with the WYSE Management Suite, but the client lost all of his settings and also the server connection. As we are using the free Version it wont auto register and you need to go to the client and register it again.

So a mass rollout is not possible for us. Maybe someone has a solution for that?

regards

With ThinOS9 devices will look to a different policy in WMS.   They look for a ThiNOS9 policy so you will need to create new policies to support your upgraded devices.

https://topics-cdn.dell.com/pdf/thinos9_mg_en-us.pdf

You Absolutely can provision devices programmatically to WMS with ThinOS9 and the free edition.  If you are using DHCP Option tags to instruct your thinOS devices to report to WMS, a bug has been identified where ThiNOS9 looks for the WMS Server tag to be defined as https://servername, instead of what ThinOS8 looked for servername:443

You will want to open a support case on this if you are experiencing this, but you may be able to adjust your DHCP option tag for server name to be https://fqdn, or change to DNS_SRV records. 

Hi,

thanks four your answer. It seems it should work but it doesnt. We are using DNS_SRV records which are working with THINOS 8.6, but after the client updated to ThinOS9 it wont register with the server. Using a modified DHCP entry like you suggested sounds like the old 8.6 client would get left behind.

The client is still listed in the Managment Suite with 8.6 and status "offline"

If we enter the WMS path manually it works and the ThinOS 9 policy gets applied. Sound like a DNS Issue but we didn't change any setting and with ThinOS 8.6 this is working.

Two other things we discovered so far:
-Uploaded certificates (from Apps and Data) can not be added in the ThinOS 9 group settings.This still works with the normal ThinOS policy. You need to upload it again while inside the group settings of a ThinOS 9 policy to get it as dropdown.

-Microsoft Teams is still not listed as "Optimized for Citrix" even after the 1912 Citrix Workspace package is installed (I´m not sure if it should, but we thought it would be as 1912 is required for this feature and with a Windows Workspace Client v1912 this works in the same environment)

regards

I would encourgae you to open a support ticket on the DNS_SRV records not being read properly.   My belief is that it is an identified bug, but they would need to confirm that for you.   It makes sense that it still shows in WMS, but offline .

Teams optimization from Citrix just hit "Experimental" for Audio only in CWA 2004.  I can not confirm when that will be added to ThinOS 9. https://docs.citrix.com/en-us/citrix-workspace-app-for-linux/citrix-workspace-app-for-linux.pdf

Yes Certs need to be uploaded separately from ThinOS8 in the ThinOS9 policy.

I am actually experiencing almost the same issue.

We use DHCP options to automatically register devices with WMS.
It works perfectly fine on ThinOS 8.4, ThinOS 8.5_024 and ThinOS 9.0.1136, but not on ThinOS 8.6_206.

The error I get is "WMS agent failed to get server info. (Invalid Group Registration Key)".
I know the group token is correct, as it works with 8.4, 8.5 and 9.0 as I mentioned above.
This only happens when I use 8.6.

I have also tried using DNS_SRV records, but it results in the same problem.

As @mumac mentioned, I can also join WMS by entering all the details manually on 8.6, which works fine, but it needs to be automatic like the other versions.

I actually opened a case with Dell Wyse support, but got nothing so far.

Hopefully someone can figure out this issue.

Update:

Out of nowhere, version 8.6 started working.
It can finally find the WMS server and register automatically via DHCP and retrieve policies.

I’ve spent the some hours on trying to figure out why it’s working now but I have no idea.

I have tried all these things which all worked:

• Device: Wyse 5070
  • Downgrade from 8.6 to 8.5
  • Upgrade from 8.5 to 8.6
  • Upgrade from 8.6 to 9.0
• Device: Wyse 3010
  • Downgrade from 8.6 to 8.5
  • Upgrade from 8.5 to 8.6

I tried all those things multiple times.
I reset the clients multiple times as well to make sure they didn’t save any settings, and it just works.

I haven’t changed anything in DNS or DHCP.
I haven’t changed anything in WMS either.
I asked my network colleague if he had changed anything, and he said he didn’t.

So yeah, I don’t know why it works, but it has been working for 2 days now constantly.

Hi,

same issue here: Citrix Virtual Apps and Desktops 7 1912 LTSR CU1, Wyse 3040 with ThinOS 9.0.1136 and Citirx_1912_1109.pkg installed -> no HDX Optimization in Microsoft Teams.

Did you found a solution for this?

best regards,

Citrix added "Experimental" support for Teams Audio optimization in CWA 2004 for Linux.  Audio and Video optimization will be forthcoming (allegedly) in CWA 2006 for Linux. Once that is released and can be integrated into ThinOS 9 it will be released by Dell.

Teams and Citrix will ONLY present audio and video under their optimization engine, not through HDX redirection at this time. 

Hi everybody,

after 2004 has been release we tested this again and found the issue with the DNS entry:

So in the past the _WMS_MGMT entry was just the FQDN and Port 443.
With ThinOS 9 we had to change the entry to https://FQDN and Port 443.
After this it is working.

regards

Bastian