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

9 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

Post a comment: