Has Windows 10 VDI Licensing changed yet?

scottalanmiller

That quote can't be legit since Hyper-V has no Type 2 option or mode. WTF is "Client Hyper-V"? Whoever wrote that didn't know what Type 2 was, so the only thing we know for sure is that it is not a reliable source. Not knowing the basics of what is stated as a requirement means we really don't learn anything from it.

scottalanmiller

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.

stacksofplates

@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:

That quote can't be legit since Hyper-V has no Type 2 option or mode. WTF is "Client Hyper-V"? Whoever wrote that didn't know what Type 2 was, so the only thing we know for sure is that it is not a reliable source. Not knowing the basics of what is stated as a requirement means we really don't learn anything from it.

Chris wrote that.

scottalanmiller

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

stacksofplates

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

stacksofplates

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

scottalanmiller

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

scottalanmiller

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

stacksofplates

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

scottalanmiller

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

scottalanmiller

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.

dbeato

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

stacksofplates

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

scottalanmiller

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

scottalanmiller

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