Licensing Windows 10 with Virtualization Technologies
-
Thanks to @chris at Microsoft for this handy guide:
-
Yes thank you @Chris for the clarification as well.
-
I want this example answered as I see it being much more relevant to SMB than VDI.
Example: I need to install Windows 10 as a VM on my Type-1 Hypervisor because I want to run some Windows based management software like Veeam, Spiceworks, or >Insert Windows program here<. The desktop will only be accessed via ScreenConnect , TeamViewer, or similar for administration purposes.
What do I have to buy?
-
I'll ping @chris for an official answer. But that looks like exactly VDI to me, not "traditional" VDI, but still remote connection to a desktop OS VM.
-
@scottalanmiller said:
I'll ping @chris for an official answer. But that looks like exactly VDI to me, not "traditional" VDI, but still remote connection to a desktop OS VM.
I used bad verbiage. Yes, it is certainly VDI. The question remains that the given examples on that how two are not clear on which license would be required for this.
-
@JaredBusch said:
I want this example answered as I see it being much more relevant to SMB than VDI.
Example: I need to install Windows 10 as a VM on my Type-1 Hypervisor because I want to run some Windows based management software like Veeam, Spiceworks, or >Insert Windows program here<. The desktop will only be accessed via ScreenConnect , TeamViewer, or similar for administration purposes.
What do I have to buy?
I really didn't want to get specific with 3rd party apps or vendors in my documentation I posted within Spiceworks. I didn't want it to seem like I was playing favorites or it was sponsored by that vendor.
To answer your question, Type-1 hypervisors are server based and any server based Windows desktop OS VM requires either a Windows VDA or Windows SA license. Which one you choose (Windows SA or VDA) depends the device and the OS installed. You now have the option in some of the VL agreements to license per User, versus per Device as it is for many SMB customers.
-
@Chris said:
I really didn't want to get specific with 3rd party apps or vendors in my documentation I posted within Spiceworks. I didn't want it to seem like I was playing favorites or it was sponsored by that vendor.
I understand that. but sticking with simply type-1 HV as the "server what else matters? Are you implying that a MS based type-1 would have a different requirement?
To answer your question, Type-1 hypervisors are server based and any server based Windows desktop OS VM requires either a Windows VDA or Windows SA license.
This is the straight part and was my current understanding of how it has always been really.
Which one you choose (Windows SA or VDA) *** depends the device and the OS installed***.
See that is the fuzzy yucky part.. How is the device (to me this means physicla hardware) even a point? It is running in a type-1 hypervisor. And the stated example is it is runnign Windows 10. Or again, were you inferring the HyperVisor when you state OS.
You now have the option in some of the VL agreements to license per User, versus per Device as it is for many SMB customers.
I would never see anything in this example ever being per user, but I guess it is a nice option?
-
Wait... if Type 1 HyperVisors are "always server based" that causes an issue with HyperV on Windows desktops, right? Since Windows 8, HyperV has been included as a feature on the desktop (at least on some editions.) I think that something is incorrect in using Type 1 as the guideline for server as MS' own desktop virtualization tool is Type 1.
-
I think that I have it figured out that the HyperV "physical" VM with console redirect to the screen for, say, Windows 10 does not count as a VM and in cases where you get the "extra" desktop VMs you also have SA licensing so that you are covered for virtualizing them. It's slightly complicated just because "in cases where you'd have access to X, Y would already be there."
-
@JaredBusch said:
@Chris said:
I really didn't want to get specific with 3rd party apps or vendors in my documentation I posted within Spiceworks. I didn't want it to seem like I was playing favorites or it was sponsored by that vendor.
I understand that. but sticking with simply type-1 HV as the "server what else matters? Are you implying that a MS based type-1 would have a different requirement?
To answer your question, Type-1 hypervisors are server based and any server based Windows desktop OS VM requires either a Windows VDA or Windows SA license.
This is the straight part and was my current understanding of how it has always been really.
Which one you choose (Windows SA or VDA) *** depends the device and the OS installed***.
See that is the fuzzy yucky part.. How is the device (to me this means physicla hardware) even a point? It is running in a type-1 hypervisor. And the stated example is it is runnign Windows 10. Or again, were you inferring the HyperVisor when you state OS.
You now have the option in some of the VL agreements to license per User, versus per Device as it is for many SMB customers.
I would never see anything in this example ever being per user, but I guess it is a nice option?
I think the think you're missing is that when you're licensing a Windows 10 server based VM, you don't license the server or the #of VMs running on the server - you license the accessing devices (or now users if you have this license option).
The licensing of Windows VDA or Windows SA remains true regardless of virtualization vendor used.
The only option outside of Windows VDA/SA is for local virtualization (type 2) where you run the VM locally on your device. An example of this would be with Mac and Boot camp or Windows Client Hyper-V. In this scenario you have the option of purchasing a full retail license of Windows to run in the VM. However, SA would still be a more flexible licensing option here as it provides the media and rights to previous versions, ability to access 4 VMs locally or remotely...
-
@Chris said:
The only option outside of Windows VDA/SA is for local virtualization (type 2) where you run the VM locally on your device. An example of this would be with Mac and Boot camp or Windows Client Hyper-V. In this scenario you have the option of purchasing a full retail license of Windows to run in the VM.
Actually that's a problem with the description.... HyperV is always Type 1 no matter where it is used. It doesn't turn into a Type 2 when used on a workstation. VirtualBox, BootCamp and VMware Workstation are all Type 2 whether on a server or a desktop (VBox used to be specifically marketed for VDI deployments, for example.) HyperV remains Type 1 whether it uses a local console redirect or not.
I think the definition needs to be moved to "server vs desktop" or "remote vs local console" because type 1 and type 2 are not correct here.
-
So to simplify the answer Chris.
Type 1 Hypervisors are fine to build a Windows 10 VM on, so long as you have SA or VDA licensing.
Correct?
-
@DustinB3403 said:
So to simplify the answer Chris.
Type 1 Hypervisors are fine to build a Windows 10 VM on, so long as you have SA or VDA licensing.
Correct?
Yes, we've always known that you can do enterprise VDI. That's the one part that was never in question
-
OK Chris Up Vote this if it's right.
If the user of the Windows VM is at the hardware device that is running the VM. Generally a type 2 hypervisor, such as VirtualBox, a retail key is acceptable. but so is SA and VDA.
If the users are remotely accessing the VM, then SA or VDA are required. (one or the other)
-
@DustinB3403 said:
OK Chris Up Vote this if it's right.
If the user of the Windows VM is at the hardware device that is running the VM. Generally a type 2 hypervisor, such as VirtualBox, a retail key is acceptable. but so is SA and VDA.
If the users are remotely accessing the VM, then SA or VDA are required. (one or the other)
There are *caveats to this statement. But generally correct.
*You can license Windows VDA for a device to run the VM locally, but only if that device has a Windows 7 Pro version or better. Otherwise, yes you can use a full retail license of Windows to run locally on the device OR Windows SA.
