Has Windows 10 VDI Licensing changed yet?
-
@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.
-
Also it does seem if you want to use Azure you can eliminate SQL and 2 domain contrllers leveraging Azure SQL and Azure AAD.
I am going to try running Vultr servers for the Gateways and internal servers, linking them to AAD today. I feel like this will end up being a premise based deployment though for us.
Its nice that you can replicated everything to the cloud for DR, but man Azure's new GUI sure is a headache compared to the one I was using a couple years back.
-
@bigbear said in Has Windows 10 VDI Licensing changed yet?:
Also it does seem if you want to use Azure you can eliminate SQL and 2 domain contrllers leveraging Azure SQL and Azure AAD.
Yes, AWS offers their own database options too. As does Rackspace.
-
@bigbear said in Has Windows 10 VDI Licensing changed yet?:
Its nice that you can replicated everything to the cloud for DR, but man Azure's new GUI sure is a headache compared to the one I was using a couple years back.
Hard to believe that it could get worse
The terrible interfaces and unintuitive system are some of the reasons that I like to avoid it. It is a huge pain to do anything on it compared to the alternatives.But things like capacity based MS SQL Server are big bonuses of it.
-
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@bigbear said in Has Windows 10 VDI Licensing changed yet?:
Also it does seem if you want to use Azure you can eliminate SQL and 2 domain contrllers leveraging Azure SQL and Azure AAD.
Yes, AWS offers their own database options too. As does Rackspace.
Yeah but no 2016 Server yet? I will say that I have seen video games streamed on 2012 on AWS videos a while back so I am excited to see what 2016 can do with a dedicated GPU.
But am I alone that I would still rather have this on-prem?
-
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@bigbear said in Has Windows 10 VDI Licensing changed yet?:
Its nice that you can replicated everything to the cloud for DR, but man Azure's new GUI sure is a headache compared to the one I was using a couple years back.
Hard to believe that it could get worse
The terrible interfaces and unintuitive system are some of the reasons that I like to avoid it. It is a huge pain to do anything on it compared to the alternatives.But things like capacity based MS SQL Server are big bonuses of it.
And yeah it is amazingly worst. And I still hate that the RDS Gateways are a requirement. It complicated an otherwise simple installation for a small setup like ours. If we are lucky we MAY have 20 people by end of year and I doubt we add a person or two per year at peak growth.
-
@bigbear said in Has Windows 10 VDI Licensing changed yet?:
But am I alone that I would still rather have this on-prem?
I never "want" on prem anything. I hate on prem. Sometimes for latency it's the way to go, but I'm never happy about it.
-
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@bigbear said in Has Windows 10 VDI Licensing changed yet?:
But am I alone that I would still rather have this on-prem?
I never "want" on prem anything. I hate on prem. Sometimes for latency it's the way to go, but I'm never happy about it.
Just because we have no servers at the moment I am going to give it a go with Vultr. I am even running a couple broadsoft switches there now. Whenever there has been latency it seems to be in Chicago's DC and usually late at nights or weekends.
-
@bigbear said in Has Windows 10 VDI Licensing changed yet?:
@scottalanmiller said in Has Windows 10 VDI Licensing changed yet?:
@bigbear said in Has Windows 10 VDI Licensing changed yet?:
Its nice that you can replicated everything to the cloud for DR, but man Azure's new GUI sure is a headache compared to the one I was using a couple years back.
Hard to believe that it could get worse
The terrible interfaces and unintuitive system are some of the reasons that I like to avoid it. It is a huge pain to do anything on it compared to the alternatives.But things like capacity based MS SQL Server are big bonuses of it.
And yeah it is amazingly worst. And I still hate that the RDS Gateways are a requirement. It complicated an otherwise simple installation for a small setup like ours. If we are lucky we MAY have 20 people by end of year and I doubt we add a person or two per year at peak growth.
What makes you require an RDS gateway?
Perhaps instead of on Prem, you should go for Colo. You're own hardware with your own firewalls.
