04-22-2019 10:01 AM
@chas1101 Hi Chas, have you tired:
04-22-2019 10:29 AM
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.
06-20-2019 10:30 AMSolution
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.
08-13-2019 11:50 PM - edited 08-13-2019 11:51 PM
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.
10-23-2019 07:11 AM
11-05-2019 07:00 AM - edited 11-05-2019 07:00 AM
We're also seeing this and are somewhat worried, since our counter is approaching 30 days (screenshot from a few days ago):
11-05-2019 07:41 AM
@jonasnilsson did you follow these instructions: https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-vm-configuration#remote-desktop-...
Please let us know if this helps.
11-05-2019 07:48 AM
11-05-2019 10:32 AM
@jonasnilsson Can you configure it to "disabled"? It should switch to an AAD mode which, regardless on how you configured AAD, will always succeed and remove the grace period. If the counter hits 0, you will only be able to login with with an admin (using mstsc.exe /admin).