Forum Discussion
WVD Licensing setup
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
Thank you for the fast response.
I guess I was looking to see how do you manage licenses in WVD since Microsoft manages the front end servers for RDS. Looking through the documents it states to have SA on your Microsoft licenses.
I am going to give your suggestion a try on the WVD server, point it to my current RDS license server.
Thanks!
chas1101 awesome, I hope that works for you!
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.
- PieterWigleven
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
Cool, thanks for the info. Ive found this forum more helpful than any other Windows forum, keep up the good work!
