How to upgrade ThinOS correctly

As I got more and more request on how to upgrade ThinOS device the correct way, I thought it would be a good idea to write a small summary.
I will not explain how to upgrade the clients technically using a fileserver with /wnos folder, etc. This is something I assume you all know.

ThinOS is designed to upgrade or downgrade from any version to any version. However there are a few exceptions:
1) Units with new Dell Mac Address ranges require 8.1_027 or higher code. In newer 8.4_108 code there is actually blocking to prevent downgrades.
2) Due to file system changes it is recommended, you upgrade older units to from 6.x / 7.x to 8.0_512 prior to upgrading to 8.1/8.2/8.3 or 8.4.
3) It is recommended you upgrade directly from 8.0_512 to 8.3 or 8.4. There are some known issues where upgrades to 8.1 or 8.2 will not unpack code correctly and result in errors (example
ICA EXEC errors).
4) When upgrading to 8.3 or higher you are now required to set a global Security Policy (SecurityPolicy=) in the INI file or a security level of Warning will be applied to WDM and File
Server SSL connections.
5) When downgrading from 8.4 you are now required to disable the Digital Signature check (Autoload=value VerifySignature=No). Digital Signatures are a new security feature to protect code
integrity in 8.4 and newer code, that and these are not found in older image files.

Please note this also applies to ThinOS Lite (for Citrix, also known as Xenith) where 1.x Xenith = 7.x ThinOS versions, and 2.x Xenith = 8.x ThinOS versions.

ThinOS 8.4_110 hotfix release available on Dell Digital Locker

On October 24th Dell has released the latest version of ThinOS on Dell Digital Locker. This is a free upgrade for all customers under ThinOS maintenance.
What’s new in version 8.4_110?
As this is mainly a hotfix release there is only one enhancement. This is the updated RTME package, which is now version 2.3.
Be aware:
With RTOP/RTME 2.3 the video resolution performance is downgraded due to Citrix design change of RTOP CPU utilization; please refer to Citrix RTOP documentation or technical support for full details. The RTME 2.3 on ThinOS could result in 30%-60% video resolution downgrade comparing to RTME 2.2 on ThinOS. The last RTME package version 2.2.42091 for ThinOS could still be used on the latest ThinOS image for better video resolution performance, but with known issues from RTOP 2.2 which are fixed in 2.3.

The rest are mainly bugfixes and new INI parameters.

BTW, all new parameters are already included in the latest ConfGen version 8.1.01.

Supported hardware platforms
Platform                                                                                        Image
Wyse 3010 Thin Client with ThinOS (T10)              DOVE_boot
Wyse 3010 Zero Client for Citrix                                 T00_xen.bin
Wyse 3020 Thin Client with ThinOS (T10D)         T10D_wnos
Wyse 3020 Zero Client for Citrix                                 T00D_xen
Wyse 3030 LT Thin Client with ThinOS                   U10_wnos
Wyse 3030 LT Thin Client with PCoIP                      PU10_wnos
Wyse 3040 Thin Client with ThinOS                          A10Q_wnos
Wyse 3040 Thin Client with PCoIP                             A10QP_wnos
Wyse 5010 Thin Client with ThinOS (D10D)         ZD10_wnos
Wyse 5010 Thin Client with PCoIP (D10DP)        PD10_wnos
Wyse 5010 Zero Client for Citrix                                 ZD00_xen
Wyse 5040 AIO Thin Client (5212)                             ZD10_wnos
Wyse 5040 AIO Thin Client with PCoIP (5213)   PD10_wnos
Wyse 5060 Thin Client with ThinOS                           D10Q_wnos
Wyse 5060 Thin Client with PCoIP                             D10QP_wnos
Wyse 7010 Thin Client with ThinOS (Z10D)          ZD10_wnos

Annoyed of the VNC implemetation in WDM WebUI?

Recently our user sono87 has published a great post in the WDM forum.
He was kind of annoyed of the VNC implementation we currently have in the WDM 5.7.2 WebUI.
Those of you using the WebUI may know this dialog when trying to shadow a client.

Followed by

and more steps like downloading the VNC player, executing it and even typing in the IP address of the client you had just selected.
All in all, not a very smart implementation.

So, sono87 sat down and did some smart modifications to make it much more intuitiv.

This is how it looks afterwards:

These are steps to do:
1. Disable Internet Information services on the WDM server.

2. Navigate to inetpub\wwwroot\WebUI\externals\cui\js\ccc-vendor.js and edit the following line 42269.
We are adding vnc to the whitelist so the url’s get recognized. (ccc-vendor.js is loaded by indexf.html) if not done correctly you will get unsafe:vnc://ipaddress urls.

Before

var aHrefSanitizationWhitelist = /^\s*(https?|ftp|mailto|tel|file):/,

After

var aHrefSanitizationWhitelist = /^\s*(https?|ftp|mailto|tel|vnc|file):/,

3. Add VNC  option in the devices tab of WDM
Edit the following file
inetpub\wwwroot\WebUI\app\device\devices.html
Navigate to Line 89 or 90

Before

<span data-ng-if=””key!=’iconStatus’”>{{device[key]}}</span><span data-ng-if=””key==’lastCheckIn’””>{{device[key]|wdmDateFormat}}</span>

After

<span data-ng-if=””key!=’iconStatus’”>{{device[key]}}</span><span data-ng-if=””key==’lastCheckIn’””>{{device[key]|wdmDateFormat}}</span><span data-ng-if=”key==’ip'”><a href=”vnc://{{device[key]}}”><img style=”width: 15px; height: 15px;” src=”../app/device/UI/images/vncicon.png” alt=”vnc” /></a></span>

Pysical path on WDM server for the VNC icon is ”inetpub\wwwroot\WebUI\app\device\UI\images\vncicon.png”
That is the location on the webserver where you need to put a vnc icon.

4. Optionally you can disable the Remote Shadow right click by editing the same devices.html line 98

Before

<li href=”#” id=”remoteShadow_CP” data-ng-click=”handleContextMenuClick(wdmCommands.REMOTESHADOW,$event)” data-ng-hide=”isContextMenuCommandHidden(wdmCommands.REMOTESHADOW)”>{{ “WDM_CMD_REMOTE_SHADOW” | translate }}

After

<!–li href=”#” id=”remoteShadow_CP” data-ng-click=”handleContextMenuClick(wdmCommands.REMOTESHADOW,$event)” data-ng-hide=”isContextMenuCommandHidden(wdmCommands.REMOTESHADOW)”>{{ “WDM_CMD_REMOTE_SHADOW” | translate }}</li–>

5. Now we need to add some files to the Windows OS in order for the browser to recognize the vnc:// extension.
Download the WDM_WebUI_VNC.zip file from the Downloads section and extract it to the root of your C drive.

6. Navigate to C:\Wyse\WDM\vncviewer\ and run regadd.bat as administrator.

The browser this is tested in is Google Chrome and IE 11,  but it should work in any other browser.
Sono87 or I are not in any way responsible if you crash your server.
Do this at your own risk.
As always, make a backup of the files you are altering!

7. Restart the IIS Server again or reboot the server

Big kudos to sono87 for this fantastic WDM mod.
Thanks a lot.

Here is the full thread

Wyse 3040 now with wireless option available

Dell announced yesterday that the Wyse 3040 thin client with wireless option for ThinOS is now available. Both wired and wireless options of Wyse 3040 thin client with ThinOS come with 8GB Flash, 2GB RAM.
The wireless model in contrary to all other thin clients models will come with an integrated antenna.

Announcing availability of USB Imaging tool 2.1.4

Dell has announced a new version of its USB Imaging Tool.
The new version 2.14. has the following new features:

• Support for USB Keys with C-Type port

• New hardware/ OS platforms:
o Wyse 3040 thin client with ThinLinux
o Wyse 5060 thin client with Win10 IoTE
o Latitude 3480 mobile thin client with Win10 IoTE

You can download this version here in the Download section.

First mobile thin client available globally

Last week Dell officially annouced the release of the new Dell Wyse 3480 Latitude based Thin Client.

Equipped with Windows 10 IoT and available in more than 20 countries worldwide, Dell uses the well-known Latitude brand to create a mobile Thin Client.

It is designed for task and knowledge workers and includes broad connectivity options along with the familiar user experience of an enterprise-class laptop.

Here are some technical specs:

Specifications Latitude 3480 mobile thin client
Operating system Windows 10 IoT Enterprise, 64bit
CPU Intel® Celeron 3865U (Dual Core, 1.8GHz, 2MB SmartCache, 15W) (Kaby Lake – 7th Generation Intel®)
Memory 8GB DDR4 RAM 2400 MHz running at 2133 MHz; 2 slots supporting up to 16GB
Hard Drive 128GB or 256GB M.2 280 SSD Class 20
I/O peripheral support 1 x HDMI 1.4

1 x VGA

1 x USB 2.0

2 x USB 3.1 Gen 1 (one with PowerShare)

1 x RJ-45

1 x Multi-media card reader (SD 3.0)

1 x Universal Jack

Display 14.0” (16:9) Anti-Glare, FHD (1920×1080) WLED, 220 nits with Integrated HD webcam, Non-touch
Multimedia Integrated HD video webcam (1.0 megapixel)

Integrated High Quality Speakers

Universal Headphone Jack

Integrated digital single array microphone

Graphics Intel® Integrated HD Graphics
Input Single Pointing Keyboard, w/Precision compliant Clickpad

Touchpad (no buttons)

Networking 10/100/1000Mbps Ethernet via RJ45

WiFi 802.11 a/b/g/n/ac dual band. Qualcomm QCA61x4A 802.11ac Dual Band (2×2) Wireless Adapter+ Bluetooth 4.1

An optional USB 3.1 dock is also available.

The wait is over – ThinOS 8.4 is finally available

As many of you have already asked for several times in the forum has happened yesterday.
Dell has released the latest and greatest version of its ThinOS operating system.
This release is packed full of new and cool features.
Here is a comprehensive list of all new additions.

– VMware Blast protocol is included
– Citrix HDX Real Time Optimization Pack was updated to version 2.2.100. You have now support for RTME 1.8 and 2.2 in just one package
– Citrix ICA Self-Service Password Reset (SSPR) added
– QUMU multi-casting
– HTML5 Video Redirection
– Bluetooth 4.0
– Simple Certificate Enrollment Protocol (SCEP)
– Changing display resolutions works now without rebooting
– Security enhancements: Firmware signature. After upgrading to 8.4, you have a signature check included. Therefore, you cannot downgrade anymore unless you use Autoload=1 VerifiySignature=no

If you are under ThinOS maintenance you can now download the new firmware directly from Dell Digital Locker. Simply log in, select “Wyse ThinOS Maintenance” under Products and then “Available Downloads”. All the new different versions are listed there. The naming is not always intuitive, but I am sure you guys will figure it out.

ThinOS 8.4 is available for the following plattforms:

Platform                                                                                          Image name
Wyse 3010 thin client with ThinOS (T10)                  DOVE_boot
Wyse 3020 thin client with ThinOS (T10D)              T10D_wnos
Wyse 3030 LT thin client with ThinOS                         U10_wnos
Wyse 3030 LT thin client with PCoIP                           PU10_wnos
Wyse 5010 thin client with ThinOS (D10D)             ZD10_wnos
Wyse 5010 thin client with PCoIP (D10DP)             PD10_wnos
Wyse 5040 AIO thin client with ThinOS (5212)     ZD10_wnos
Wyse 5040 AIO thin client with PCoIP (5213)       PD10_wnos
Wyse 5060 thin client with ThinOS                               D10Q_wnos
Wyse 5060 thin client with PCoIP                                  PD10Q_wnos
Wyse 7010 thin client with ThinOS (Z10D)              ZD10_wnos

As there was an issue with analog audio recording on the 3040, the release of 8.4_009 for Wyse 3040 was postponed.

Wyse Management Suite announced at Citrix Synergy

Earlier this week during the Citrix Synergy Dell announced the availabilty of the new management suite for Dell Wyse Thin Clients, called Wyse Management Suite 1.0.

WMS is technically very similar to the Cloud Client Manager. Therefore CCM will now be renamed to WMS. However, WMS will be available in three versions.
The Standard version will be on-premise solution, it is free of charge and can be installed in the local datacenter.
The Pro version will be available as on-premise and public cloud offering. This version is subscription based that includes per seat cost, maintenance and ProSupport.

CCM customer do not have to do anything. They are automatically migrated to the new WMS.
If you are using WDM, you should stay with it for now. Later Dell will release a migration path at no cost, if you want to go from WDM to WMS.

 

Feature set matrix:

Features Wyse Management Suite Standard Wyse Management Suite Pro
Private Cloud Public Cloud
Highly scalable solution Up to 10,000 endpoints +50K endpoints +1M endpoints
Cost Free Per seat subscription Per seat subscription
Architecture On-premise On-premise Cloud-based
Manage devices behind firewalls Limited Limited Yes
Asset visibility
Automatic Device discovery X X X
Asset, Inventory & Systems management X X X
View effective configuration at device level after inheritance X X X
Reporting & Monitoring
Alerts, Events and Audit logs X X X
Enterprise Grade Reporting X X
Alerts via email and Mobile app X X
Security
Secure communication (HTTPS) X X X
Two-factor authentication X X
Active directory authentication for role based administration. X X
Comprehensive management
OS Patch and Image management X X X
Smart Scheduling X X X
Bundle Applications to simplify deployment and minimize reboots X X
Dynamic group creation and assignment based on device attributes X X

 

 

Hardware support

The following thin clients can be managed by Wyse Management Suite:

  • Wyse 3010 thin client with ThinOS
  • Wyse 3010 zero client for Citrix (ThinOS Lite)
  • Wyse 3020 thin client with ThinOS
  • Wyse 3020 zero client for Citrix (ThinOS Lite)
  • Wyse 3030 thin client with WES7
  • Wyse 3030 LT thin client with ThinOS, ThinOS w/PCoIP and ThinLinux
  • Wyse 3040 thin client with ThinOS and ThinOS w/PCoIP
  • Wyse 5010 thin client with ThinOS, ThinOS w/PCoIP, Linux, WES7, WE8S
  • Wyse 5020 thin client with Linux, ThinLinux, WES7, WES7P, Windows 10 IoT Enterprise
  • Wyse 5040 AIO thin client with ThinOS and ThinOS w/PCoIP
  • Wyse 5060 thin client with ThinOS, ThinOS w/PCoIP, WES7P, ThinLinux and Windows 10IoT
  • Wyse 7010 thin client with ThinOS, Linux, WES7, WE8S
  • Wyse 7010 extended thin client with WES7
  • Wyse 7020 thin client with Linux, ThinLinux, WES7, WES7P, WE8S, Windows 10 IoT Enterprise
  • Wyse 7040 thin client with WES7P and Windows 10IoT
  • Latitude 3460 mobile thin client with WES7P
  • Latitude E7270 mobile thin client with WES7P
  1. Refer to Wyse Management Suite documentation for the current list of supported Wyse thin clients and recommended firmware builds.
  2. Note: Wyse Management Suite does not support PCoIP zero clients.

Best ConfGen Version ever released

Normally I am not patting myself on my back. However, the new version of ConfGen has cost me a lot of work and I really hope you will like it as much as I do.
The new version 8.0.0.1 has a brand new section for Dell Wyse Thin Linux.

All parameters up to version 1.0.3 are included now.
As this is the first implementation, I do hope that I haven’t made to many mistakes here. Be nice to me please 🙂

Second new part is ThinOS.
Of course, ThinOS is not new to ConfGen. However, I have included all new parameters for the upcoming 8.4_009 release planned for end of June.
Besides of all the new parameters, I have done some design changes.
There is a new dropdown field available, which is capable of selecting more than one value.

As you can see below, the field it auto-expanding in the moment you move your mouse pointer on it, showing all values with small checkboxes in front and as soon as you leave the box with your mouse pointer, it is shrinking automatically again showing a small green tick in front of the box to make clear, you have selected something.

The other change is the red alert sign in front of all fields that allow encryption. As you know, I am no longer allowed to encrypt any strings in ConfGen, as you all should use AES encryption instead. To make it clearer, I have added the red alert sign showing up as soon as you enter anything in such a field. You can hover over that sign to get a warning or click on it to get help on creating AES encrypted passwords.

Last but not least, I have modified all Comboboxes and Numeric fields to be read only to prevent entering wrong values. Also ConfGen is now saving the path of the last opened file for later use.

Let me know what you think about all these changes.