Hey all! I wanted to let you know Dell has just released several new Dell thin client and Wyse Management Suite training offerings!
Here is a list of the offerings:
You can check out the various options here!
Enjoy!
Connect to the Dell Community here!
@chris_messier ~~> Subscribe to blog to get latest updates <~~
Deploying Azure Virtual Desktop (AVD) in a Kiosk configuration is a common question we get asked when using Dell Windows 10 IoT thin clients.
The idea is when the device boots, it will present only with an AVD login with no other options present on the desktop, start menu, etc… thus creating a locked down kiosk solution.
By default, this is the behavior with ThinOS & AVD since the device is natively locked down. An example of this is outlined in a previous post here.
We can also do the same thing with Dell Windows 10 IoT by using a great Dell utility included in IoT called EasySetup. You can configure this tool in the Wyse Management Suite console and just specify an AVD connections and remove any other options, icons, configuration, etc.. from the desktop of the thin client. These same steps can be used to configure any other VDI connections, i.e. Citrix, VMware, browser icons, etc..
You can configure by following the steps below;
Configure your Wyse Management Suite (WMS) group configuration to launch the AVD client as shown below.
2. In the WES WMS configuration group, go to ‘Wyse EasySetup‘ and enable ‘Kiosk Mode‘. Under ‘Applications‘, section give the connection icon a name, i.e. AVD Desktop and under ‘Application Location‘, enter the path to the AVD client, i.e. C:\Program Files\Remote Desktop\msrdcw.exe
Configure any of the optional settings as desired.
3. Once complete with the settings, click ‘Save & Publish‘ at the top of the page to save settings.
4. Once the device boots up and downloads your updated WMS configuration, it will enable the Wyse EasySetup shell and the end result should be the following below.
Note: The File Base Write filter needs to be enabled in order for the Wyse EasySetup shell to be enabled and applied. If not, you will boot to the normal Windows desktop and not see the single icon as shown below.
5. By default, the ‘Wyse Easy Setup’ policy removes many configurations from the start menu so the user can’t access any settings. If you want to enable some specific Start Menu options, Control Panel settings, task bar settings, etc.. you can toggle many of these features on in the ‘Wyse Easy Setup’ policy.
For example, some of the settings you can enable are shown below. These settings are located the same ‘Kiosk Mode’ section shown above. To see more details of the available Wyse EasySetup configuration options search for the latest the WMS administration guide here.
I hope this helps provide some additional information about using the Wyse EasySetup utility to setup an Azure Virtual Desktop connection in Kiosk mode on Windows 10 IoT thin client.
Hope you found this helpful!
Additional Resources:
@chris_messier ~~> Subscribe to blog to get latest updates <~~
A new Dell Wyse ThinOS enhancement to be aware of is the introduction of a ThinOS Activation License that was introduced as part of ThinOS version 2205 (version 9.3.1129) & Wyse Management Suite 3.7.
This new license is required in certain scenarios as outlined here.
In some cases, you may encounter the following message below:
“Login is denied (ThinOS activation license is not available)”
You will get this for a few reasons as outlined in the release notes here and outlined below.
This license takes effect starting with ThinOS 2205/9.3.1129 & Wyse Management Suite 3.7 as noted in the release notes here.
If you are running into this issue after upgrading to ThinOS 2205, you may need to reach out to your Dell account team to likely purchase the appropriate ThinOS Activation License if you fall into one of the categories.
Alternatively, you can roll back to prior versions of ThinOS until you identify the reason you are getting this license message & purchase the proper ThinOS activation license(s).
The new ThinOS Activation License is discussed in greater detail here, Dell ThinOS – Installation & Activation License User Guide. This document also covers installing ThinOS on newer hardware manually such as the Wyse 3420 thin client laptop IF it is not pre-loaded at the factory.
If you use WMS on prem you will need to export your ThinOS Activation License from WMS Cloud to WMS on prem server as noted here.
Hope you found this helpful!
Additional Resources:
@chris_messier ~~> Subscribe to blog to get latest updates <~~
The latest release of Wyse Management Suite, 3.6, is out! I put together a brief summary of the installation process if installing locally on a Windows 2019/2016/2012 server. Alternatively, WMS can also be run as a hybrid cloud solution as noted here. Enjoy!
You can download Wyse Management Suite v3.6 from here along with documentation and release notes here.
2. Accept EULA and click ‘Next’
3. Choose Typical or Custom and be sure to check off ‘Turn off IE Enhanced Security Configuration’ then click ‘Next’. I selected Typical for this standard install.
4. Provide credentials for both database access and administrator credentials. Note: The administrator credentials will be the login credentials you’ll use to log into the WMS console.
5. I clicked ‘Next’ past this section as it’s specific to using Teradici zero clients which I’m not using. If you are, see more info at page 15 here
6. Select an option to create the WMS service account from the below options.
7. Provide credentials for the Software Vault as noted below.
8. Click ‘Next’ to accept the default security configuration
9. Select the installation and repository location as noted below
10. Once you click ‘Next’, the installation will start!!
11. Once install finishes, click ‘Launch’ at the end and a wizard will finalize the install. You can see more of these final steps here starting at Step 14.
Additional Resources:
@chris_messier ~~> Subscribe to blog to get latest updates <~~
I recently came across an issue that took some time trying to resolve regarding 802.1x configuration on ThinOS 9.1 that I wanted to share.
Ultimately, the issue came down to the SSL certificate name not matching the certificate name entered into the Wyse Management Suite (WMS) configuration.
When the device was trying to authenticate, it was using a certificate name that didn’t match what was in the WMS configuration and failed to authenticate because of this.
Some errors we received in the event log but weren’t very descriptive although it appeared to be a certificate authentication issue based on ‘private key passphrase needed for SSID’ error message.
Example log:
We then looked at the WMS 802.1x configuration and verified the certificate name, in this case, ‘wyse.pfx’ – note the lowercase ‘w‘. We uploaded again to WMS and verified we got prompted for password so that looked correct.
We then looked at actual certificate we uploaded, ‘Wyse.pfx’, and made note of the case – capital ‘W‘ vs the lowercase ‘w‘ that was entered in WMS console so we changed WMS to match certificate name. We changed it from ‘wyse.pfx’ to ‘Wyse.pfx’. Once we did this and rebooted device, it connected to the network successfully!
Lesson learned, it’s never a bad idea to verify case sensitivity and try to make sure they match to avoid this potential pitfall!
Hope you found this helpful!
Additional Resources:
@chris_messier ~~> Subscribe to blog to get latest updates <~~
The Dell Wyse team has recently launched support for Windows Virtual Desktop(WVD) on Dell Wyse ThinOS 9.1. This is big news as it allows us to use a non-Windows thin client endpoint to connect to your WVD environment! Microsoft posted a quick announcement about this as well here.
I’ve covered some details about the configuration below and you can access the official documentation here;
The configuration for ThinOS & WVD is pretty straightforward with the only configuration needed is a Wyse Management Suite (WMS) policy to specify Windows Virtual Desktop under the broker setting which is shown below.
Note – by default, the WVD client package is pre-installed on 9.1 but incase it’s not or you’re looking for latest you can get from support.dell.com under drivers for your model, for example 5070, search for ‘wvd’.
2. Under the following section you just need to choose the appropriate WVD deployment model you are using. You will chose either the latest WVD ARM (Azure Resource Manager) based deployment model or the ‘classic’ WVD non ARM based deployment. In my testing, I am using the Azure portal ARM based deployment so I selected the (ARMv2) option. When you are done, click ‘Save & Publish’.
3. Also under, Broker Settings\Global Broker Settings set to – “Windows Virtual Desktop” on your policy as shown below:
4. Once the updated WMS policy is received by your device, you should see your new WVD setting reflected on your device as shown below 
4. Once the devices reboots, you should be prompted with the Microsoft Azure AD login screen as shown below 
5. At this point you are ready to login into WVD and access your VMs! 
6. In this case I have access to a Windows 10 VM! 
Hope you found this helpful!
Additional Resources:
@chris_messier ~~> Subscribe to blog to get latest updates <~~
“Client configuration were obtained using an unsecure connection. Please consider the potential security risk before proceeding.”
To resolve this, you will want to enter the following value on the Advanced section in WMS:
signon=yes enablemessage=no
This Advanced section is located under your group profile located in Advanced Device Configuration\Advanced as shown below.
You will then enter, signon=yes enablemessage=no, on an available line as shown in the example below:
Additional details:
Release notes here.
HTH!
@chris_messier ~~> Subscribe to blog to get latest updates <~~
Microsoft Teams Optimization is now available for Dell Wyse ThinOS 9 with the launch of the latest Citrix WorkSpace app 2006 for Linux. Users of ThinOS 9 can now download this latest Citrix WorkSpace app and get the benefits of Microsoft Teams Optimizations in a Citrix environment.
Unified Communications have always been a challenge in virtual desktop environments and the continued innovations in this area are much needed.
Citrix does a nice job of outlining the details of how the optimization works along with a quick video in this blog post.
Here are some additional details:
Supported Platforms and Management Software:
Citrix resources for Microsoft Teams Optimization
ThinOS 9 Resources
Enjoy!
@chris_messier ~~> Subscribe to blog to get latest updates <~~
In a previous post, here, I covered how to resolve the SSL error message, “SSL Certificate Authority is Unknown” when using ThinOS.
In this post I will cover how to upload SSL certificates into Wyse Management Suite (WMS) and how to assign them to a specific group configuration/profile for ThinOS 8.x and 9.x.
The process is slightly different for ThinOS 8.x & ThinOS 9.x but I will cover both below.
How to upload SSL certificates for use by ThinOS 8.x:
1. In WMS, browse to “Apps & Data”:
2. Scroll down to “File Repository”:
3. Click “Add File” to upload Certificate:
4. Browse out to the Certificates you exported. You will need to do for each Certificate you exported.
5. Once you click upload it should show up under the ‘Apps & Data – Inventory File Repository”:
How to upload SSL certificates for use by ThinOS 9.x:
How to assign SSL Certificates to WMS configuration group/policy:
Once your certificates are imported into WMS, you then need to assign them to your ThinOS profile you are using under, “Groups & Configs” select the group you want to edit following steps below;
This completes the process of uploading your SSL certificates to WMS and assigning them to a ThinOS policy.
For more assistance, check out Dell Community Forums (formally Dell TechCenter):
@chris_messier ~~> Subscribe to blog to get latest updates <~~
“SSL Certificate Authority is Unknown”
A common issue connecting to a VDI connection broker, i.e Citrix, VMware, etc.., from Dell Wyse ThinOS or any thin client, is an SSL certificate error. There are generally 2 reasons why.
Error: SSL Certificate Authority is Unknown
This is easily fixed by installing both the missing Root and likely the Intermediate certificate.
To do this, you can simply export from a browser, and then import on the device, generally through Wyse Management Suite (WMS) or even a USB key if you had to.
I will cover the 3 step process to fix this.
Steps to export certificate from browser:
3. This will bring up the certificate information:
4. Click on “Certification Path” tab bring up the following:
5. Select the top level certificate, in this case, “Sectigo (formally Comodo CA)”
6. This will bring up the Root certificate as shown below, “Comodo RSA Certification Authority”. This is the first certificate we want to export.
7. Click on the “Details” tab and select, “Copy to File”:
8. Take defaults and follow the wizard to export the certificate:
9. Once you export the top level Root Certificate, follow the same steps to export the Intermediate certificate. This Intermediate is chained, or trusted, by this top level Root Certificate so we need both certificates in this chain.
10. In the browser, select the Intermediate Certificate, “COMODO RSA Domain Validation Secure Server CA” and select “View Certificate”:
11. Select “Details” and “Copy to File” to export the certificate:
12. Follow wizard again to export the Intermediate Certificate:
13. You now have successfully exported both the top level Root Certificate, “Comodo RSA Certification Authority”, and the Intermediate Certificate, “COMODO RSA Domain Validation Secure Server CA”.
Once exported you need to upload them into your WMS server. It’s a simple process and the steps to upload the certifications are outlined here. Once complete, resume to step 15 below to assign the certificate(s) to your group configuration/profile.
15. Once certificates are imported into WMS, you then need to assign them to your ThinOS profile you are using under, “Groups & Configs” select the group you want to edit following steps below;
This completes the process of exporting the SSL certs, uploading to WMS, and assigning them to your profile. This should resolve the issue of “SSL Certificate Authority is Unknown”.
For more assistance, check out Dell Community Forums (formally Dell TechCenter):
@chris_messier ~~> Subscribe to blog to get latest updates <~~
VDI Toolbox 