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;
- ThinOS 9.1 & WVD product summary noted here
- ThinOS 9.1 administrators guide here, release notes here, & 8.6 to 9.1 migration guide here
- Note – If you are still on ThinOS 8.6 you can learn how to upgrade to 9.x 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’.
-
- In WMS, edit your ThinOS 9 policy and browse to ‘Advanced –> Broker Settings –> Windows Virtual Desktop Settings’ as shown below
- 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’.
- Once the updated WMS policy is received by your device, you should see your new WVD setting reflected on your device as shown below
- 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! 
- In WMS, edit your ThinOS 9 policy and browse to ‘Advanced –> Broker Settings –> Windows Virtual Desktop Settings’ as shown below
Hope you found this helpful!
Additional Resources:
- If you are new to ThinOS 9.1, here is a quick video overview of some of it’s features.
- Looking for more details on ThinOS 9.1? Check out the release notes here
- ThinOS 9.1 release notes discussing WVD setup here & 8.6 vs 9.1 feature comparison here
- Excellent Dell Wyse community located here
- Dell Community forums for ThinOS here
@chris_messier ~~> Subscribe to blog to get latest updates <~~
[…] I recently worked with a customer exploring Windows Virtual Desktop (WVD) and they asked about Dell Wyse support. This article talks about our Windows 10 IoT support and we also have released support for Dell Wyse ThinOS 9.1 which you can read more about here. […]
LikeLike
[…] Chris Messier from VDI Toolbox has written a great blog post on how to get up and running with WVD using the latest Dell Wyse ThinOS 9.1. In the post he shows you which configuration settings you need to configure and performs some testing. You can view his post here – Dell Wyse ThinOS 9.1 & Windows Virtual Desktop (WVD) Support | VDI Toolbox […]
LikeLike
Hi Chris, any idea why we need to login again with old SAM? We have no RDP passtrough.
It ends with RDP Login : RDP Session Host login, user: something@domain.x missing credentials.
LikeLike
Hi Rene – are you using Active Directory Domain Services for WVD? I’ve asked a few times around this in the MS community and SSO in this case isn’t currently supported but on the roadmap from what I’ve heard. A bit more info here; https://docs.microsoft.com/en-us/azure/virtual-desktop/authentication#single-sign-on-sso
Another lengthy thread on it here as well: https://techcommunity.microsoft.com/t5/windows-virtual-desktop/wvd-single-sign-on-double-authentication/m-p/1163055
LikeLike
No, we are using regular AD via VPN (to AD). I can use UPN without domain now, but still typing a password 2 times to connect is not really user friendly.
This is the same behaviour as using an BYOD laptop/desktop.
LikeLiked by 1 person
Yes, I know lots of folks are asking for this so hopefully addressed soon as noted above.
LikeLike
Dear Dell
We have more than 100s of Wyse 3040 .
When we try to use in Windows virtual desktop infrastructure , our staff need to input their password twice.
Can your technical expert check this and advise us to resolve or overcome this issue as our staff started to complain as this is frustrating them.
Because
1. They use RDS before and they did not need to input password or user name twice
2. Whenever the screen lock ( we are a medical charity and we must do this for information governance purpose) after particular time interval, they need to do the login process again
I attach screen shots , please see attaches for login process in number order.
Your speedy response will help us to build our staff confidence.
The operating system is Thin OS 9.1.2101
Regards
LikeLike
Hi Chris,
Have a weird one, using 3040 upgraded successfully to 9.1.1131. Did a factory reset to clear all settings. Enabled WVD ARMv2 with direct internet access, no firewall. these are the only settings enabled, everything else is as default on 9.1.1131
Am able to successfully enter corporate credentials and MFA prompted, but no WVD feeds are being pulled through.
Any thoughts, will be appreciated
MTIA
Alex
LikeLike
Few thoughts…
– when you login, do you see the toolbar off the the left but no desktops/apps listed?
– do you get desktops/apps when logging in here? https://rdweb.wvd.microsoft.com/arm/webclient/index.html
– under ‘Packages’ on the device, did you verify WVD package is installed? It likely is if you can authenticate.. https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=pk00h&oscode=thn80&productcode=wyse-3040-thin-client
LikeLike
Hi Chris,
Happy, happy, now I am.
Ensuring that the WVD package is installed makes all the difference – I believe it is a must. As I thought 9.1.1131 already had the WVD pre-installed. Not the case
Thank you very much for the pointers
Many thanks
Alex
LikeLike
Alex – great to hear! Yes, I believe it should be part of image, but will look into. Out of curiosity, did you upgrade from 9.0 –> 9.1 or did you go 8.6 –> 9.1?
LikeLike
Chris,
This particular unit was upgraded from 8.6 to 9.1 – but others had been 8.6>9.0>9.1 but that was due to the VNC issue, and in our case with the WMS hotfix going from 8.6>9.1 still allowed VNC to work.
LikeLike
Alex – ok good to know. Thanks.
LikeLike
Where do you find all these settings in Azure?
What is a “Client ID”?
If the choice is binary between WVD ARM and ‘classic’ why are there 2 separate toggle switches?
LikeLike
The “Client ID” is already pre-populated in the WMS console, they are fixed for the WVD client, you don’t need to enter those.
Those 2 options exist depending on how your have WVD setup so you choose one or the other.
See more on differences here: https://www.christiaanbrinkhoff.com/2020/05/01/windows-virtual-desktop-technical-2020-spring-update-arm-based-model-deployment-walkthrough/#DifferencesbetweenWVDnon-ARMandARM
LikeLike
Thanks for your response. I appreciate you taking the time.
If Client ID fixed for WVD (i.e. it’s set by Microsoft and never going to change) then why have them as configuration to change at all?
I understand that the 2 options exist to service both types of set up but you can’t have both and you need at least 1; so why does the UI allow you to select both or deselect both?
I’m not trying to be obtuse here, I honestly want to understand this so I can address the gaps in my knowledge.
Thanks again for your time.
LikeLike
Those are both very good points and I would agree with you, no particular reason they are set that way to my knowledge. I will bring this up to product team as something to considering changing. Thanks for feedback. -Chris
LikeLike
Great! Thanks very much for the clarification!
LikeLiked by 1 person