How to set up license - Windows Server 2016 - RDS Client Access License (CAL)

Brass Contributor

Hi,

 

On https://docs.microsoft.com/en-us/azure/virtual-desktop/overview#requirements it states the following:

 

First, make sure you have the appropriate licenses for your users based on the desktop and apps you plan to deploy:

Windows Server 2012 R2, 2016, 2019RDS Client Access License (CAL) with Software Assurance

 

Is there any information as to how a setup for licensing WVD with a Win Serv 2016 with traditional RDS Client Access Licenses? Do we need a standard RDS Licensing server, and if so, how do we set up licensing to the RDSH server using WVD?

4 Replies

@andersidahl I think all this really means is owning the CAL licenses.  If you have 30 RDS users, you should budget for 30 RDS CALs.  That is merely a guess though.

@andersidahl : We have initial/general documentation for setting up a license server with CALs: https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-client-access-lic... .

 

It looks like we're missing a step on how to set up licensing specifically for Windows Virtual Desktop, so thank you for the feedback!

Would just like to confirm the below is correct, please:

If I wanted to run Windows Server as the OS for an AVD Session Host, then the license that is required is just an RDS CAL (Remote Desktop Services (RDS) Client Access License (CAL) with active Software Assurance (SA)) correct? I don't need the actual OS license? Same as it is for Windows 10 Multi-session, where I am entitled to use the OS at no additional cost if I were to use one of the supported licenses, e.g. Business Premium?