My problem is that, I also have read several blogs and articles stating that is required for a VDI deployment when using RD Web to access the Win10 Vms plus the VDA which seems to be an overkill. There's a different type of VDA license to use when the virtual desktop that is being accessed is hosted by an official Microsoft hosting partner. In fact, I have implemented several times RD GW and RD Web to connect to physical/virtual servers that were not RDSH servers and I did not even needed to install the RD Licensing role. VDA through Open Value is used when you are hosting your own Windows VMs on-prem and users are accessing the VM like a desktop (rather than say a SQL server or web server or the like). After two of the seven servers showed up like this, i've stopped upgrading the other VDA's. It separates the personal computing environment from the physical machine and provides a virtualized desktop that is stored and run on a remote central server. VDI offers an alternative desktop delivery model. They upgrade fine, but after a VDA is upgraded this server shows up in Director as failure type 'maximum load' and failure reason 'agent shutdown'. What is VDI Virtual Desktop Infrastructure (VDI) is the ability to host desktops on remote servers (thin client).

Seems that RDS CAL are only required when users connect to a RD Session Host server not when you connect to a VM running in a RD Virtualization Host. Only thing left is to upgrade some VDA's on Published App servers. I have a question about RDS lisensing for a Windows 10 VDI deployment project using Windows Server 2019 Remote Desktop Virtualization Host role.Īs per this documentation: rds-client-access-license

How to upgrade server vdi vda