Today I was asked to upgrade the customers Thin Clients, all Wyse TC’s, to the latest version (version 9.0). They would like to use the latest Citrix Workspace App and the possibility to use the Microsoft Teams optimization for Citrix.

They already tried upgrading from version 8.6 to 9.0 but they ran into issues where the new OS didn’t received the correct configuration after the update. To make sure we don’t have issues with their current WMS suite, we upgraded to WMS 3.0. You can download the new WMS version here. The upgrade path is as easy as Next,Next, Finish, so I don’t describe this here.

After the upgrade of the WMS, I downloaded all the latest firmware and application packages, just to make sure their are no issues with provious versions that’s going to cause issues with the upgrade.

Upgrading the wyse to 9.0

I created a new policy called ThinOS9 and set the ThinOS 8.x policy settings that upgrades the firmware to the latest 9.x firmware. as you can see here:

Firmware upgrade settings policy for 8.6 to 9.0

Next we set installation of the necessary packages, Citrix and BIOS update. Bios update is only possible when you have WMS 3.0. See the screenshot below. Both the Firmware upgrade and the package installation is set in the same policy setting.

Installation ThinOS packages (Citrix and BIOS)

Next we started testing the upgrade, because the client is already in WMS because it’s using 8.6 we could assign it to the new Group (ThinOS9) and the machine started upgrading. We ran into two problems:

WMS: failed to check-in: URI does not contain a protocol

The first upgrade went well, but after the reboot the machine didn’t received the packages. Looking into the logs of the TC, the TC received the following error: WMS: failed to check-in: URI does not contain a protocol

When looking into this issue, it’s looked like the Wyse received the wrong settings for connecting to the WMS. Looking into the administrator guide we need to set the DHCP option 165 to FQDN:443. Because we where already using WMS we did set it, but it looks like that’s not correct and changing just the name from FQDN:443 to https://FQDN:443 solved the issue and now after the reboot the machine connected to the WMS server.

Default Group

The next thing we noticed is that the Wyse TC moved back to the old production Group, after looking into the DHCP options again we did set DHCP option 199, their we set it to the default group which is based on 8.x.

After removing this option and verifying that production machines after a reboot keep connected to the correct group, we removed this option from the scope.

You can look here for all the DHCP settings for WMS.

Now we could reboot our Wyse 3040 with ThinOS 9 and it finally received all the packages we configured. Now we could start testing with our Citrix environment look into all the new options.