@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...
