Has Windows 10 VDI Licensing changed yet?
-
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@stacksofplates yeah, he's a licensing guy, but not a technical one. Which causes problems at times. Because licensing without tech is gibberish. Shows how much of a problem it is with MS licensing that even their own people don't even know what products MS offers. He really should know that Hyper-V is a type 1 hypervisor and that MS discontinued their Type 2 in 2005.
Ya I didn't read that far into it. Just saw type 2.
-
@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.
-
@stacksofplates said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@stacksofplates yeah, he's a licensing guy, but not a technical one. Which causes problems at times. Because licensing without tech is gibberish. Shows how much of a problem it is with MS licensing that even their own people don't even know what products MS offers. He really should know that Hyper-V is a type 1 hypervisor and that MS discontinued their Type 2 in 2005.
Ya I didn't read that far into it. Just saw type 2.
Client Hyper-V is a real term, but it just means Hyper-V installed via windows 8.
https://technet.microsoft.com/en-us/library/hh857623(v=ws.11).aspx
It's tuned differently, but it is still Hyper-V.
-
@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."
-
@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.
-
@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.
