Windows Server 2016 Pricing
-
@scottalanmiller said in Windows Server 2016 Pricing:
Imagine what it was like on HP Superdomes with IA64 architecture. You could have one Windows instance on over 128 CPUs!!
Did MS have special licensing agreements with HP for those?
-
@scottalanmiller OK for the sake of my own sanity-
In my environment, I have 3 hosts, each with 2 CPUs. All are running ESXi. If I have eight Windows Server 2012 R2 licenses, how many VMs can I run with Server 2012 R2?
-
@wrx7m said in Windows Server 2016 Pricing:
@scottalanmiller OK for the sake of my own sanity-
In my environment, I have 3 hosts, each with 2 CPUs. All are running ESXi. If I have eight Windows Server 2012 R2 licenses, how many VMs can I run with Server 2012 R2?
This totally depends on how you split the licenses over the hosts. You can't move licenses between hosts more than once every 90 days.
-
Let's assume the most evenly split load
VM host 1 : 3 licenses = six VMs
VM host 2 : 3 licenses = six VMs
VM host 3 : 2 licenses = four VMs -
@Dashrender OK - Good. That is what I thought. That is how it is setup currently.
I guess, once you get beyond 2 CPU, is when you need extra licenses to cover the additional CPUs?
-
@Dashrender said in Windows Server 2016 Pricing:
@scottalanmiller said in Windows Server 2016 Pricing:
Imagine what it was like on HP Superdomes with IA64 architecture. You could have one Windows instance on over 128 CPUs!!
Did MS have special licensing agreements with HP for those?
No
-
@wrx7m said in Windows Server 2016 Pricing:
@Dashrender OK - Good. That is what I thought. That is how it is setup currently.
I guess, once you get beyond 2 CPU, is when you need extra licenses to cover the additional CPUs?
Correct, each Standard License covers up to TWO VMs, on TWO CPUs.
-
OK. I was getting worried because that was my understanding and I am almost done filling out the MS audit spreadsheet. I haven't had more than 2 CPUs on any host, so that part hasn't applied to me. That is interesting (and annoyingly convoluted), though.
-
@scottalanmiller said in Windows Server 2016 Pricing:
@Dashrender said in Windows Server 2016 Pricing:
It really bends you mind when you think of an 8 processor chassis.
In this case you would need 4 licenses to just be allowed to run two VMs, you would need 8 licenses to run four VMs, etc.Like an HPE Integrity.
Cloud@Cost was running 8 CPU servers with VMware and windows I believe. All legally licensed I'm sure.
-
@Jason said in Windows Server 2016 Pricing:
@scottalanmiller said in Windows Server 2016 Pricing:
@Dashrender said in Windows Server 2016 Pricing:
It really bends you mind when you think of an 8 processor chassis.
In this case you would need 4 licenses to just be allowed to run two VMs, you would need 8 licenses to run four VMs, etc.Like an HPE Integrity.
Cloud@Cost was running 8 CPU servers with VMware and windows I believe. All legally licensed I'm sure.
They had no Windows. You couldn't even get Windows from them. You had to supply your own and had to license the entire cloud for a single VM that you might want to run.
-
@Jason said in Windows Server 2016 Pricing:
@scottalanmiller said in Windows Server 2016 Pricing:
@Dashrender said in Windows Server 2016 Pricing:
It really bends you mind when you think of an 8 processor chassis.
In this case you would need 4 licenses to just be allowed to run two VMs, you would need 8 licenses to run four VMs, etc.Like an HPE Integrity.
Cloud@Cost was running 8 CPU servers with VMware and windows I believe. All legally licensed I'm sure.
https://mangolassi.it/topic/4842/why-you-cannot-effectively-run-windows-on-cloudatcost
-
@scottalanmiller said in Windows Server 2016 Pricing:
@Jason said in Windows Server 2016 Pricing:
@scottalanmiller said in Windows Server 2016 Pricing:
@Dashrender said in Windows Server 2016 Pricing:
It really bends you mind when you think of an 8 processor chassis.
In this case you would need 4 licenses to just be allowed to run two VMs, you would need 8 licenses to run four VMs, etc.Like an HPE Integrity.
Cloud@Cost was running 8 CPU servers with VMware and windows I believe. All legally licensed I'm sure.
They had no Windows. You couldn't even get Windows from them. You had to supply your own and had to license the entire cloud for a single VM that you might want to run.
They had it.. just not licensed haha.
-
@JaredBusch said in Windows Server 2016 Pricing:
@zuphzuph said in Windows Server 2016 Pricing:
Does anyone have a stupid simple breakdown of pricing? I'm still confuzzled on how this per core stuff works... Currently I work for an MS partner so this isn't something I've had to worry about for quite some time...
For Server 2016 Standard:
$882 for the minimum 16 cores means that the per core price is $55.13.
You are required to buy in 2-core packs. Each 2-core pack then should cost $110.26.
If you have a 2 proc x 10 core server, for 20 total cores, then you will buy 10 2-core packs for $110.26 * 10 = $1102.60.
It won't be easy to stay within basic Standard fee for pretty much ANY server in ±12 months from now. Reason: TOO MANY CORES!
-
I knew this was coming when I ordered my last servers, I didnt need alot of processing power, so I ordered a 1 socket 10core cpu. I believe it can be done with the base pricing.
-
They will be adding licences per NIC's next lol.....Don't agree with this per core licencing model, shitty move by Microsoft I think....
-
@brianlittlejohn said in Windows Server 2016 Pricing:
I knew this was coming when I ordered my last servers, I didnt need alot of processing power, so I ordered a 1 socket 10core cpu. I believe it can be done with the base pricing.
Yes, because minimum is
8 cores per proc
16 cores per serverYou will be licensed for 6 more cores than you have.
-
@KOOLER said in Windows Server 2016 Pricing:
@JaredBusch said in Windows Server 2016 Pricing:
@zuphzuph said in Windows Server 2016 Pricing:
Does anyone have a stupid simple breakdown of pricing? I'm still confuzzled on how this per core stuff works... Currently I work for an MS partner so this isn't something I've had to worry about for quite some time...
For Server 2016 Standard:
$882 for the minimum 16 cores means that the per core price is $55.13.
You are required to buy in 2-core packs. Each 2-core pack then should cost $110.26.
If you have a 2 proc x 10 core server, for 20 total cores, then you will buy 10 2-core packs for $110.26 * 10 = $1102.60.
It won't be easy to stay within basic Standard fee for pretty much ANY server in ±12 months from now. Reason: TOO MANY CORES!
I'm pretty sure that all the server makers will make servers specifically to meet this need.... providing other features but limiting the cores to match the licensing limits.
-
@StuartJordan said in Windows Server 2016 Pricing:
They will be adding licences per NIC's next lol.....Don't agree with this per core licencing model, shitty move by Microsoft I think....
It's really not as bad as it seams. They are pretty much just recognizing that sockets don't reflect what the original pricing model was based on.
-
@scottalanmiller I can understand the pricing may be a little dated, they should of just increased the cost per socket a little more rather then implementing core based licencing. Oh well I wont rant too much about it, after all its the weekend
-
The new licensing looks like a nod from Microsoft towards Intel. This really makes the whole hyperthreading vs more cores concept tip the scales towards Intel.