Has Windows 10 VDI Licensing changed yet?
-
@stacksofplates said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@stacksofplates said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
Using Windows 10 locally on a machine where it is locally installed is normally VDI free. So like if you one 100 copies of FPP Windows 10 and install them all to VMs (type 1, type 2, that never matters) on your desktop and access them locally, you never run into VDI licensing needs even though they are virtual. It's because Microsoft doesn't use actual VDI as a requirement for VDI licensing. Their licensing is totally disconnected from the term.
Ya I just want to make sure if I do put a Windows VM on my laptop I don't break any licensing rules.
Depends on how you acquire it and how you access it. It's not as simple as "put it on my laptop."
What's the best way? I'm guessing I can't just use an OEM license from an existing machine.
Just console through Virtual-Manager or virt-viewer.
You can... if the existing machine is the same one you are virtualizing on
Like, if you have a laptop with Windows 10 OEM. And you want to install Korora on the base, add KVM, and run Windows 10 on top of it and access it from the local console or via RDP as the only user, you are fine. That's VDI in the real world, but it is not VDI by Microsoft's licensing definition.
-
If you want Windows 10 that is not OEM from the same machine, you'll need a Full Retail Box / FPP copy to install there.
-
@scottalanmiller yes, vitual pc 2007 was long ago. But what do you consider Windows 7 with virtual pc and Windows 8 & 10 with Hyperv as type 1?
-
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@stacksofplates said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@stacksofplates said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
Using Windows 10 locally on a machine where it is locally installed is normally VDI free. So like if you one 100 copies of FPP Windows 10 and install them all to VMs (type 1, type 2, that never matters) on your desktop and access them locally, you never run into VDI licensing needs even though they are virtual. It's because Microsoft doesn't use actual VDI as a requirement for VDI licensing. Their licensing is totally disconnected from the term.
Ya I just want to make sure if I do put a Windows VM on my laptop I don't break any licensing rules.
Depends on how you acquire it and how you access it. It's not as simple as "put it on my laptop."
What's the best way? I'm guessing I can't just use an OEM license from an existing machine.
Just console through Virtual-Manager or virt-viewer.
You can... if the existing machine is the same one you are virtualizing on
Like, if you have a laptop with Windows 10 OEM. And you want to install Korora on the base, add KVM, and run Windows 10 on top of it and access it from the local console or via RDP as the only user, you are fine. That's VDI in the real world, but it is not VDI by Microsoft's licensing definition.
Ya that's what I was thinking. Ok I'll be alright then. Thanks.
-
@dbeato said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller yes, vitual pc 2007 was long ago. But what do you consider Windows 7 with virtual pc
Virtual PC was their non-server Type 2. It lingered longer than 2005 (but not a lot longer) when their server Type 2 died off (Virtual Server 2005.)
-
@dbeato said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller But what do you consider ..... Windows 8 & 10 with Hyperv as type 1?
Yes, Hyper-V is a type 1. No convertible Type 1 / Type 2 has ever been made (and we don't expect one.) The technology makes no sense to merge together. I've got a pending video to make about that, I talked through it with people just the other day.
But Hyper-V is always a T1, no exceptions.
-
But Type 1 vs. Type 2 is all technology, it never matters for licensing. So it doesn't affect anything big.
-
@scottalanmiller found this ancient post but relevant
https://blogs.technet.microsoft.com/chenley/2011/02/09/hypervisors/ -
@dbeato said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller found this ancient post but relevant
https://blogs.technet.microsoft.com/chenley/2011/02/09/hypervisors/
-
@scottalanmiller it tAkes a couple of refreshes
-
I've used RemoteApp successfully. It works well. Have you considered that?
Or are we way past the OP?
-
@dbeato said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller it tAkes a couple of refreshes
Well written. I like that it covers history back to the IBM 1960s era, and clarifies what T1 and T2 are, and makes it perfectly clear that Hyper-V is T1 by both direct statement and description.
-
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@dbeato said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller it tAkes a couple of refreshes
Well written. I like that it covers history back to the IBM 1960s era, and clarifies what T1 and T2 are, and makes it perfectly clear that Hyper-V is T1 by both direct statement and description.
Under type 2 examples, KVM is listed has a type 2.
-
@black3dynamite said in Has Windows 10 VDI Licensing changed yet?:
Under type 2 examples, KVM is listed has a type 2.
It's actually what is now known as a Type 0, which is really a subset of Type 1. It's anything but a Type 2, as it is not on top of an OS.
Type 0 is a bad term, but ESXi and KVM are called that as they don't only not run on top of an OS, but they don't need a "Dom0" OS either. But Xen and Hyper-V still need that Dom0.
-
@black3dynamite said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@dbeato said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller it tAkes a couple of refreshes
Well written. I like that it covers history back to the IBM 1960s era, and clarifies what T1 and T2 are, and makes it perfectly clear that Hyper-V is T1 by both direct statement and description.
Under type 2 examples, KVM is listed has a type 2.
This is an old dispute. KVM is of course type 1, not by the classical definition but in the way it performs, expose the virtual hardware etc. It plays in the same league of Xen, HyperV and ESXi, no need to use other terms. The inner design of the solution is completely transparent to the user.
-
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@black3dynamite said in Has Windows 10 VDI Licensing changed yet?:
Under type 2 examples, KVM is listed has a type 2.
It's actually what is now known as a Type 0, which is really a subset of Type 1. It's anything but a Type 2, as it is not on top of an OS.
Type 0 is a bad term, but ESXi and KVM are called that as they don't only not run on top of an OS, but they don't need a "Dom0" OS either. But Xen and Hyper-V still need that Dom0.
I don't agree with the use of "type 0" in this way, because I've seen it related to hardware virtualization like LPAR, that of course is a completely different thing…
-
@Francesco-Provino said in Has Windows 10 VDI Licensing changed yet?:
@black3dynamite said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@dbeato said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller it tAkes a couple of refreshes
Well written. I like that it covers history back to the IBM 1960s era, and clarifies what T1 and T2 are, and makes it perfectly clear that Hyper-V is T1 by both direct statement and description.
Under type 2 examples, KVM is listed has a type 2.
This is an old dispute. KVM is of course type 1, not by the classical definition but in the way it performs, expose the virtual hardware etc. It plays in the same league of Xen, HyperV and ESXi, no need to use other terms. The inner design of the solution is completely transparent to the user.
Even by classical definition. The hypervisor kernel sits directly on the hardware.
-
@Francesco-Provino said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@black3dynamite said in Has Windows 10 VDI Licensing changed yet?:
Under type 2 examples, KVM is listed has a type 2.
It's actually what is now known as a Type 0, which is really a subset of Type 1. It's anything but a Type 2, as it is not on top of an OS.
Type 0 is a bad term, but ESXi and KVM are called that as they don't only not run on top of an OS, but they don't need a "Dom0" OS either. But Xen and Hyper-V still need that Dom0.
I don't agree with the use of "type 0" in this way, because I've seen it related to hardware virtualization like LPAR, that of course is a completely different thing…
I agree that that makes more sense.
-
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@stacksofplates said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@stacksofplates said in Has Windows 10 VDI Licensing changed yet?:
So admittedly I didn't read through the whole thread just the first couple pages. I'm pretty sure we use XenDesktop for this. We have some guys who use a laptop and they get a VDI session with a dedicated graphics card. Then they run SolidEdge,SpaceClaim, or ANSYS Workbench to do their work.
You have a bit more scale. His issue is that he has so few users.
I guess you could do the same thing on a smaller scale. Just have dedicated VMs that people RDP into, you might not even need the graphics cards if they are just viewing CAD files.
Seems like RDS would work fine if you don't need GPU.
So actually 2016 Server DOES support GPU access both for session host and vdi.
Not sure why but I wasnt getting alerts on this thread all weekend, probably because I left the browser open at the office.
-
@stacksofplates said in Has Windows 10 VDI Licensing changed yet?:
So admittedly I didn't read through the whole thread just the first couple pages. I'm pretty sure we use XenDesktop for this. We have some guys who use a laptop and they get a VDI session with a dedicated graphics card. Then they run SolidEdge,SpaceClaim, or ANSYS Workbench to do their work.
I know a company that uses XenDesktop for Solid Edge and are really happy with it, despite only being a 20 person company.
It seems 2016 Server has done a lot to catch up with XenDesktop though now that I am playing with it.
While Azure has special VM's built for this I dont think GPU is an option on Vultr though.
