Microsoft Licensing Requirements for Desktop Virtualization (VDI)

I’ve been trying to get the License SKUs required for different VDI Deployment Scenarios. Today I worked with a Microsoft Licensing Specialist from CDW and this is what I learned.

If a customer has a PC with an OEM Version of Windows Vista Business, the requirements are:

  • Microsoft SKU “66J-01128″ - Microsoft Windows Vista Business - W/ Microsoft Windows Vista Enterprise - software assurance - 1 PC - Open Business - English (License Only)
  • Microsoft SKU “DSA-00050″ - Vista Enterprise Centralized Desktop for SA (Subscription)


If a customer has a PC with a downlevel version of Windows, i.e. XP Pro or 2000 Pro, the requirements are:

  • Microsoft SKU “66J-01215″ - Microsoft Windows Vista Business - W/ Microsoft Windows Vista Enterprise - upgrade & software assurance - 1 PC - Open Business - Single Language (License Only)
  • Microsoft SKU “DSA-00050″ - Vista Enterprise Centralized Desktop for SA (Subscription)


If a customer has a thin client device, regardless of OS the requirements are:

  • Microsoft SKU “DSA-00056″ - Vista Enterprise Centralized Desktop for Devices (Subscription)


Optional components:

  • Microsoft SKU “WSB-00090″ - Microsoft Desktop Optimization Pack (MDOP) - Includes Microsoft Application Virtualization (Softgrid)


Notes:
VECD entitles a single client device to access up to four (4) Virtual Desktops, whether they are running locally in VMware Workstation or Virtual PC, or hosted on a Hypervisor like Microsoft Hyper-V, VMware ESX or VI3, Virtual Iron or Citrix XenServer.

For customers doing VDI on Parallels Virtuozzo Containers, the requirements are the same as for Terminal Services, i.e. Windows Terminal Server CAL & Windows Server CAL, but they don’t have to deal with VECD. Instead Virtuozzo users can purchase Windows Server 2003 Datacenter Edition to run unlimited number of containers on a single host.

If a customer has a Select or Enterprise Agreement, they should contact ther Value Added Reseller (VAR) for those SKUs.

For more information:

Quest Software accepts no responsibility for the validity of this information. When in doubt, contact your VAR’s licensing specialist or your Microsoft Licensing Representative.

Tags: ,
Posted in: licensing

You can leave a response, or trackback from your own site.

Bookmark and Share

19 Responses to “Microsoft Licensing Requirements for Desktop Virtualization (VDI)”

  1. Jim Kenzig

    Patrick Here is the Link for VECD License info from Microsoft. The bottom line is if you want to do VDI you need VECD whether you are running XP or Vista
    Licensing Vista with VM

    Jim Kenzig
    http://www.techblink.com
    twitter.com/kenzig

  2. Patrick Rouse

    Jim, you are absolutely correct, and thanks for clarifying this, as I didn’t explain that piece. My biggest challenge was finding someone who could provide me with actual Microsoft SKUs as to what needed to be purchased. Luckily today one of my contacts at CDW hooked me up with one of their Microsoft Licensing Specialists who provided the information I posted. The information was spread through an email thread, but what is posted is just a summarized, organized verision.

    Thanks again Jim. :)

  3. Alec Istomin

    Patrick, thanks for binging this up, very useful!
    I was wondering if you know how to separate and distinguish the server and client side licensing for VDI, especially in case of vmware and virtuozzo. Since I might be running XP/VIsta on my laptop and also have optional access to Virtual Desktop running XP, Vista or maybe w2k3 server…

  4. Iwan Rahabok

    Thanks Patrick for taking time to publish this. It’s hard to believe a simple thing like this can be so complicated. No wonder Business thinks IT can improve a lot :-)

    Just 1 little suggestion: if this post is still up to date (which I think it is), it would be good to add a note like “up to date as at Feb 09″. It just that extra piece of mind, since we are talking $$ here.

    Cheers from Singapore
    e1

  5. Patrick Rouse

    You’re welcome, and nothing has changed (that I know of). One interesting note is that one can virtualize Server 2003 or Server 2008 desktops w/o VECD. You simply license 2003/2008 Datacenter Edition and purchase TSCALs for each user or device that will be accessing the desktops. This bypasses the subscription model of SA & VECD. So long as you can run your apps on 2003 or 2008, this should work fine. This is what Parallels Virtuozzo customers do for VDI.

  6. Josh

    Patrick,

    Thanks for all the good data!

    One question for you. I have heard and read about getting around VECD by using Virtuozzo and a Datacenter copy of 03/08.

    Obviously I am not the first person to think of this, but why could you not use the same idea for VMware view? Meaning, instead of dishing out VDI sessions with XP/Vista, have it push out 03/08 Datacenter edition.

    So, I know I can’t (its too obvious), but do you know why you couldn’t?

    Thanks!

    Josh

  7. Patrick Rouse

    Josh, VECD is not used for Virtuozzo VDI because they deliver server OS desktops, and VECD only pertains to client OS, i.e. XP, Vista…

    There’s no technical reason why one can’t deliver server OS with other products, but I think the EULA for View and XenDesktop require one to use desktop OS, which ties you to VECD. Check with VMware about delivering 2003/2008 desktops via View.

    Virtuozzo has the advantages of 2-3X scalability (on the same server hardware), no SAN storage or VECD requirements.

  8. Josh

    Patrick,

    Thanks for the answer. I am going to talk to my VMware guy on Monday about this.

    With the Vista License + SA + VECD, plus the VMware View license on top of all that, VDI is out of the question for us (gotta hate the MS licensing scheme right now…).

    But, if we could get away with getting a few Datacenter editions of 03 + View, that might change things.

    I will let you know what I find out. Thanks for the input!

    Josh

  9. Patrick

    Hi Patrick,

    thanks for the answers right now. I got it with VECD and the Vista-License. But how does Microsoft license Office on a VM? Do I only need a licensed copy of office in the end or another VECD-License for each Client?

    Patrick

  10. server hosting

    server hosting…

    Before virtualization technology on the Intel platform, (It has been around for YEARS in the IBM mainframe/ midrange world!) the prospect of setting up your own server cluster just to“ mess around” with things was an expensive endeavor. This is pretty …

  11. Andy Thomas

    Has anyone actually purchased the VECD license “Microsoft SKU “DSA-00056″ - Vista Enterprise Centralized Desktop for Devices (Subscription)”? I would like to get a contact to purchase the correct licenses. A search on cdw.com or cdwg.com turns up no hits for the search term “dsa-00056″. A general search on Google shows a few links that list it as a MONTHLY subscription (like on Provantage.com) for a lot more than $110 per year.

  12. Patrick Rouse

    Andy, you can contact any VAR for this, but the list pricing is as follows:

    VECD for SA - $23 per year, per device
    VECD for Devices (computers not covered by SA, i.e. thin clients) - $110 per year, per device

    I don’t know if these SKUs are valid anymore.

  13. Mike

    I’m in the planning phase of a VMware View implementation.

    For this scenario, can you tell me if my assumptions around the VECD and MS licenses are correct. (for simplicity, i will keep it limited to just 1 user)

    I have one user, will purchase a laptop for this user with Vista. This user will also use this laptop to access a virtual machine with a Vista OS on it.

    So from a MS licensing standpoint I need:
    A Vista license for the laptop
    A SA subscription for the above Vista license
    A VECD subscription which gives the laptop the right to access the VM
    Also an additional Vista license that will be used on the VM

    So do I really need two Vista licenses for just one user, (one lic for the laptop, and one for the VM)

    What about MS Office, if I want to install and use Office on the laptop and also install and use Office on the VM, are 2 licenses required, even if it is only for one person?

    It seems I need to double up on MS Window licenses for each user, one license for the physical device, and one for the virtual device.

    Does is still hold true if the physical devices ran XP, but they accessed Vista VM’s? Would I need to have an XP license for the physical devices(laptops) and a Vista license for each user.

    This is all very confusing, any advice you can offer would be great.

    Thanks,

  14. Patrick Rouse

    The basics are as follows:

    To connect to any hosted virtual desktop, regardless of hypervisor, VECD is required. VECD can be obtained in one of two ways.

    1. Obtain Subscription Advantage for the Windows Client OS -> Enroll in VECD for SA

    2. Enroll in VECD for Devices (typically for any device that is not covered by SA, i.e. non-Windows devices, thin clients)

    In scenario 1, a customer must own a Windows Client OS License, enroll it in SA and VECD. In scenario 2, the customer only enrolls in VECD, as no pre-requisite client OS is required.

    Check with Microsoft on Office licensing.

  15. Mike

    Patrick, thanks for the quick response. I will call MS about the licenses. I think each user will need two Client OS licenses. I don’t want to get into a situation where you go to activate a windows machine and it says that the license has already been used and activated before because it was initially activated when the laptop was first set up, then when a user tries to activate that license again on the virtual OS it would be used again.

  16. Patrick Rouse

    That definitely is NOT required. At most you’d need an OS license + SA + VECD, but not two OS licenses.

  17. Mike

    Patrick thanks again for the info, I am also waiting to hear back from MS on my licensing questions.

    I hope two license are not required. But still it is two different OS’s in use (one on the laptop, and one on the VM), so wouldn’t two licenses be required? For example what if the user were to use their laptop for a number crunching program, but use their VM for MS Office type work. In this example it would be possible for a user to kick off a process that takes a while to complete, and while it is working away on the that, they could then bring up an RDP session to their VM and work on an Excel document. Now there are two OS’s doing totally different things, but using the same license at the same time. Wouldn’t this be why two Client OS license are required?

    Does my question make sense? It seems you would need a license for the OS on the laptop. And then a different license for the VM you log in to.

  18. Patrick Rouse

    This is exactly what VECD entitles you to do, run up to 4 VMs of anything from XP Pro to Win7 from a machine that is enrolled in VECD. The VMs can be hosted on any hypervisor, remote server… If using VECD for SA, you purchase a Win7 License, enroll in SA+VECD and you’re covered for the local OS plus your 4 VMs. If using VECD for Devices, you don’t buy any Client OS and just enroll in VECD for Devices.

    Make more sense now? Let me know if still unclear.

  19. Mike

    It does make sense now. Thank You! When you said “you’re covered for the local OS plus your 4 VMs” is what made it all click. That is what I couldn’t seem to figure out from reading all the documentation out there.

Post a comment: