windows server 2012 remote desktop licence

How are you delivering the desktops VMs from the server to the clients? If you are using Remote Desktop Services Opens a new windowto deliver the OS to the client - yes you need a RDS CAL on top of the Windows VDA license. Windows VDA is not a 'repetitive cost' - as the OEM license does not allow for flexibility that is most often overlooked when virtualization solutions being discussed.Ĭhris, Let's assume I only want to deploy Windows 7/8 desktops from Hyper-V, do I need RDS licenses as well as VDA (or SA) licensing? But if you have an OEM Windows Pro license you can add SA and not purchase Windows VDA. So, technically if you had a linux device or device without a Windows OS, then technically your're not purchasing the license twice. Windows VDA is included with WIndows Client SA.

Windows VDA – provides rights to access a VM of Windows desktop OS on a server.

VL is upgrade licenses only - Only a single user of the licensed device can RDP into that device.

FPP/OEM license allows for local install only - Only a single user of the licensed device can RDP into that device.

There are basics to the Windows OS licensing that might help with this common misconception:

So in essence to use a virtual desktop in this situation, this one person needs 4 licenses bought for them?

So say someone is using a windows 7 desktop without SA (so weve already purchased that client license) to access a dedicated windows 7 VM (have to purchase another license for that) which means theyd need a VDA license, which is not only one shot but a yearly repetitive cost, in addition to the per client license of the way its being access (RDP, VMWARE, CITRIX) is this correct?

Windows server 2012 remote desktop licence