Forum Discussion
chas1101
Apr 22, 2019Copper Contributor
WVD Licensing setup
How do I enable licensing for WVD - I get a pop up saying to configure RDS Licensing.
- Jun 20, 2019
It's similar to how on-premises licensing works . If you are using Windows Server RDSH, you need a RDS CAL for every user that connects. If you are using a Windows Client OS, you are covered with your Windows E3 (or better) Per User licensing.
Since, from a licensing perspective, Windows 10 Multi-session is considered a client OS - you don't need an RDS CAL and there is no need to configure a TS licensing host.
An Admin might be getting pop-ups about a grace period, that's something we are fixing.
- For 1903 builds that should go away in a couple of weeks.
- For 1809 builds it will take longer and the best workaround is using the latest image from the gallery which has a grace period of 800 days. We promise to fix this before the 800 days are over.
Thanks, Pieter
Ethan Stern
Apr 22, 2019Iron Contributor
chas1101 awesome, I hope that works for you!
TheDooj
Jun 19, 2019Copper Contributor
Should we even be using RDS cal's for this environment? It was my understanding that the Microsoft E3 license covered that for multi user session.
- PieterWiglevenJun 20, 2019
Microsoft
It's similar to how on-premises licensing works . If you are using Windows Server RDSH, you need a RDS CAL for every user that connects. If you are using a Windows Client OS, you are covered with your Windows E3 (or better) Per User licensing.
Since, from a licensing perspective, Windows 10 Multi-session is considered a client OS - you don't need an RDS CAL and there is no need to configure a TS licensing host.
An Admin might be getting pop-ups about a grace period, that's something we are fixing.
- For 1903 builds that should go away in a couple of weeks.
- For 1809 builds it will take longer and the best workaround is using the latest image from the gallery which has a grace period of 800 days. We promise to fix this before the 800 days are over.
Thanks, Pieter
- jonasnilssonNov 05, 2019Copper ContributorPieter, do you have a fix for the issue when running Windows 10 1903?
- PieterWiglevenNov 05, 2019
Microsoft
jonasnilsson did you follow these instructions: https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-vm-configuration#remote-desktop-licensing-mode-isnt-configured
Please let us know if this helps.
- HandAOct 23, 2019Brass ContributorHi there,
I still get this pop up when using the market place Images of Windows 10 1903. Should this have been fixed by now? I have a M365 E3 license assigned to the admin user I am using
Thanks
Gerry- jonasnilssonNov 05, 2019Copper Contributor
Bump, we have the same issue with one (out of 6) host. It is running Windows 10 1903
- Joachim LøeAug 14, 2019Brass Contributor
Still i get this when using the Remote Desktop Client (WVD).
If no RDS license server is required, then why. This suddenly started.
I have 2 hosts in a pool. Only 1 have this issue./Joachim
- Joachim LøeAug 14, 2019Brass ContributorI ended up redeploying to the 1903 image. Working now.