Understanding Windows Server Hyper-V Licensing – vembu – Windows Server 2016 Datacenter Edition

Share on facebook
Share on twitter
Share on linkedin

Looking for:

Windows server 2016 cluster standard vs datacenter free –

Click here to Download

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Purchasing 7 Standard edition licenses to run 13 virtual machines on a single host costs the same amount of money as a Datacenter edition license. Note 3: Datacenter edition has features that Standard edition does not, such as Storage Spaces Direct and Storage Replica… among quite a few others. You can lower the number of physical node licensing by preventing VMs from running on specific nodes.

Failover Cluster Manager — Possible Owners setting. If you purchased SA with your server license, you have some additional interesting benefits. Licensing can and does change! This means that in anticipation of a fail-over event, you may run passive fail-over on another qualifying shared server NODE2.

Microsoft Volume Licensing direct. Windows Server Licensing: Windows Server. In my example, I have a server with 4 physical CPUs of 16 cores each for a total of 64 physical cores. Would I need 32 2-core licenses for this server? Yes, you need a 16core datacenter license for each host for unlimited vms. I have two question. So if we have 2 VMs on a 1 proc, 4 core server, 16 core needs to be purchased 3 times.

Is this correct? Secondly, for enterprise, does the above logic holds true? What about if I have 16 VMs on the same configuration? I have to purchase 16 x 16 cores per server. You need to license a minimum of 16 cores per server, period. If the host is doing other stuff as well, like file server, AD, etc.

For every two VMs you have running on Standard edition, you need to license a minimum of 16 cores. After about 13 VMs, Enterprise edition makes sense. What do you think? If all your windows servers are licensed as you say, then you do no need to build a new cluster for SQL, there is no relationship between the licensing.

You need to purchase enough 2-core packs to cover all of your CPU cores, and must license a minimum of 8 cores per CPU. This means that in a server that has two CPUs, you must license a minimum of 16 cores, meaning you need to purchase at least 8 2-core license packs.

This comes out to about the same price as prior Windows Server licensing. Now in your situation, you have more than 16 total cores, but something seems to be off here. Is that 22 cores for each CPU? Was it supposed to be 2x core CPUs for a total of 20 cores? So i have 2 extra core license, now questions are: 1 Should I use my windows standard edition product key to activate 2 windows server VMs same key for both VMS? Linux VMs do not need Microsoft Windows licenses.

Windows VMs and Windows hosts do, however. If your physical servers nodes are running Windows Server, the hardware needs licensed. If your physical servers hosts are running Hyper-V Server not Windows Server , then they do not need licensed. Yes, you can in fact add the Failover Cluster feature to the free Hyper-V Server , and add it to your cluster. Your email address will not be published.

Save my name, email, and site URL in my browser for next time I post a comment. I feel there has been a lot of unnecessary confusion around Windows Server licensing. My goal with this post is to alleviate this confusion by showing you how simple it actually is. Hernan 11 February, at Scott 5 March, at Prasenjeet 18 December, at Hi, I have two question. I have to purchase 16 x 16 cores per server Reply.

Timothy Gruber 19 December, at Dani 13 December, at Hi Timothy, congrats to your blog. It is cheaper to add RAM to a host than to add hosts once licensing costs are taken into account. It seems apparent that he is not talking about real clustering – one host fails, those VMs are offline until he moves the VHDs are moved.

We are just getting what you’re picking up from the conversation – if we take what the OP is saying at face value, it definitely doesn’t seem like he knows what he’s doing. The OP told us earlier in the thread that his tech installed two domain controllers – that’s why I wrote up my list above of hosts as I did. So yes, it appears that the tech installed two Domain Controllers using Windows DataCenter licenses – sigh.

This doesn’t require datacenter licensing. The tech has incorrectly informed the OP that the ‘cluster’ needs to be in it’s own domain, not part of the production Active Directory domain.

This is totally wrong. The OP indicated that his tech made a new dedicated Active Directory domain just for this ‘cluster’. I agree with Kevin, there was, is NO reason to make a new domain for this. Kevin is also correct that RAM and storage added to current hosts are often able to extend current hardware.

As mentioned in several of my other posts already,, there is zero need for a new domain just for this. You’re right, this isn’t a cluster in the form of auto failover or HA. It sounds like there is just shared storage – or at least likely shared storage. Hyper-V never requires licensing – it’s free, completely and utterly. You download the installer from the Microsoft Trial website but it’s not a trial, requires no key and never expires , then install on the hardware. When you purchase Windows Server standard, it includes licensing for 16 cores.

If you have a 16 core or fewer server, that’s all you need. If you have an 18 core or more server, you will need to purchase 2 core add-on packs for every 2 cores over This standard license grants you the rights to have two VMs on a single server.

Windows Server DataCenter license includes licensing for 16 cores on a single server. Like standard, if you have more than 16 cores, you need to purchase 2 core add-on packs. Unlike standard where you are limited to two VMs per license, you get unlimited Windows VMs per license. Now, in your case, it appears that perhaps your vendor instead of selling you 6 Windows Server DataCenter licenses, they sold you only 2 core add-ons.

But it does appear they sold you enough to cover all 6 servers worth of cores, so you are likely covered here. Hyper-V is it’s own system, it’s not part of windows. The fact that you can install it as a role in Windows brings confusion to this point. There is no functionality difference. If Hyper-V is installed directly on Hosts , that is exactly what you want.

Dashrender seems to have the closest understanding to the layout or information I was provided and given host 1 and 2 are domain controllers “DC” a primary and secondary at no point in this chain have I referred to Datacenter as anything other then Datacenter in order to prevent as much confusion as possible.

You are correct he is telling me what he is doing, but though technical terms are being used, they make no since and raise enough flags for me to reach out here. I have never setup a cluster myself just book smarts on how they are supposed to function and configured which is the cause for the flags. So I am looking for validation from other people AKA you among the spiceworld to gain insight as to how this might look if correctly done to determine if it is something I can take on myself.

We have established that when he told me hyper-v core he most likely meant hyper-v server so we can move past that. Additionally he has setup 2 domain controllers that so far Dash has me leaning to being un-needed. Though Tim has provided at least one plausible reason as to why he has setup the domain controllers. So what I am looking for after all the useful information provided so far is, does it at all sound like my tech has a real handle on this project answer so far leans towards no.

That being the case is this something that I can attempt to move forward using documentation and spicehead help to rebuild correctly leaning towards maybe , or most likely do I searching for a consultant.

Under all of that is are the total core licenses we have for server datacenter enough to cover all our physical servers answer seems to be yes. But do you really even need this many hosts? This would not reduce the amount of licenses you need still 12 to 13 total, but could reduce power consumption noticeably, and give you some spare parts. Only testing will tell. OK now that that is out of the way, You could purchase Datacenter licenses for the needed servers.

This gives you the ability to move VMs around at will. But considering your current non HA setup, you can likely skip this. Also from a numbers perspective, DataCenter on it’s own is more expensive than multiple Windows Server Standard licenses if you need less than 13 VMs per server. No my intent was to never give a plausible reason for AD DCs. I was trying to figure out what was going on.

As far as I can tell, they are completely unneeded. I’ve seen no evidence of any clusters cluster meaning HA hyper-v cluster “Microsoft Failover cluster” using at least 2 nodes in the cluster. I still don’t know if that’s what is being done or not. I think I got lost in this mess. Actually we have not established that. We’ve established what he should be using, but we don’t know because we just heard about “Hyper-V Core”. My guess is the Tech claimed MS failover clusters, but then never got it to work.

There is no product called Hyper-V. Most of additional features of Windows Server Datacenter don’t matter to most users, but the difference is not just the virtualization rights. This will put your mind at ease if the all clear comes back and will give you definite questions to ask if not.

You may not be technical nout wrong with that but you need to put your manager hat on at a jaunty angle, but firmly, and get to the bottom of matters. I have never setup a cluster myself and outside of seeing working labs at other locations, vendors, and even professional friends houses so I fully admit this is most likely over my head abit but i can reach up when the need calls for it.

I only have book and web based knowledge about what one is supposed to look like and how it is supposed to function and what he is telling me and setting up is no where close I thank you all for the validation of that provided threw-out this post , but I also will admit that generally the practical design, setup and configuration lets call it standards established by that documentation sometimes deviates. Since I am sure there are multiple ways to skin this cat.

So that is what fueled this post my ignorance in the best practices when it comes to setting up a cluster of servers and that underlying feeling that the information he has been feeding me is BS and not anything near accurate to the original upgrade proposal. Which leaves me trying to determine if this is something within reach of my experience with the assistance of spiceheads and web resources that I can step up and correct, or do I call in big guns and hope I can learn along the way.

This topic has been locked by an administrator and is no longer open for commenting. To continue this discussion, please ask a new question. Your daily dose of tech news, in brief. He conceived the ma I manage several M tenants all with Security Defaults enabled and in one specific tenant, for some reason, no users including Global Admins are able to create a Team directly in the Teams app using the “Join or create a team” option.

This option IS Do you take breaks or do you keep going until you complete the 6 steps of debugging? Today I overcame a, what I thought was a major problem, minor challenge. We just got don Good afternoon and welcome to today’s briefing. Hope you are starting to enjoy the warmer weather up in the north it has been pretty awesome.

That said Security doesn’t sleep and so do we have to keep our systems and our knowledge up to date. We have some Online Events. Log in Join. Windows Server. First question or post to spiceworks ever so please bare with me. Since Datacenter is the version that covers licensing for unlimited vms The task is to setup a cluster of 6 servers with datacenter as the virtual hosts in a cluster so that any future vms wouldn’t require licensing this idea was sold to me at the beginning of the project and we purchased enough core licensing to cover said servers 96 total.

Not sure I am adding this to the right group so may have to repost. Spice 5 Reply Contest Details View all contests. Shaun wrote: So what I am looking for after all the useful information provided so far is, does it at all sound like my tech has a real handle on this project answer so far leans towards no.

A consultant would be another option. Once you know about the storage, let us know. Scott Alan Miller. Shaun wrote: First question or post to spiceworks ever so please bare with me. Spice 1 flag Report. Shaun wrote: I have just checked in with my tech and found that he has setup 2 servers thus far with data center as DC for the cluster I have never setup a cluster so not sure this is needed so that the first question.

Spice 2 flag Report. Verify your account to enable IT peers to see that you are a professional. Shaun wrote: In addition he has setup 4 hyper-v core nodes and migrated our vms over to them. Shaun wrote: he has setup 4 hyper-v core nodes Watch your terminology as it brings confusion – Hyper-V Server is the free hypervisor-only product.

Shaun wrote: The task is to setup a cluster of 6 servers with datacenter as the virtual hosts in a cluster so that any future vms wouldn’t require licensing this idea was sold to me at the beginning of the project and we purchased enough core licensing to cover said servers 96 total. License wise, again, assuming you only have 16 core machines, you look covered.

Just curious, you’re talking about a cluster – in what way is this a cluster? Do you have shared storage? OP Shaun The original plan was to get licensing for are physical servers so we wouldn’t have to mess with licensing ever again for are VM’s addition I have never setup a cluster and my experience with hyper-v has always been within server OS, there is iscsi storage that the VM’s share, though I have been here a year and have no solid answer as to how much is available.

Hyper-V is free. It is a hypervisor. It doesn’t have versions. Shaun wrote: Sorry for the confusion the original idea pitched to me was to have a bed of physical servers clustered together using server datacenter licenses, that would host unlimited VM’s on top of them license free. The original plan was to get licensing for are physical servers so we wouldn’t have to mess with licensing ever again for are VM’s huh – he installed to Domain Controllers on bare metal?

I’d say bring in a consultant. Shaun wrote: Sorry for the confusion the original idea pitched to me was to have a bed of physical servers clustered together using server datacenter licenses , that would host unlimited VM’s on top of them license free. The original plan was to get licensing for are physical servers so we wouldn’t have to mess with licensing ever again for are VM’s Lots here to cover : First, datacenter licensing isn’t related to clustering.

We should step back, why do you have so many hosts? Six is enormous. The third method, which may be the most optimal, is to setup AD activation. It appears that you have: host 1 – domain controller – needs 1 Windows standard license host 2 – domain controller – needs 1 Windows standard license host 3 – Hyper-V server – needs DataCenter license for the number of cores in host host 4 – Hyper-V server – needs DataCenter license for the number of cores in host host 5 – Hyper-V server – needs DataCenter license for the number of cores in host host 6 – Hyper-V server – needs DataCenter license for the number of cores in host Again that is only for what you have listed.

Obsolesce This person is a verified professional. How many virtual machines do you have, and what are the resource requirements of the top 5? Are you SURE you need 6??? One host equals huge single point of failure. That single host is much more likely to stay running than 2 or more servers. Also, there are other things in place such as backups, replication, etc. Please compare the risk factor of the alternative for us. Dashrender wrote: I know Scott said this already, but clustering is not a license function of Windows Server DataCenter edition.

Shaun wrote: Dashrender wrote: I know Scott said this already, but clustering is not a license function of Windows Server DataCenter edition. So it makes it really hard for us to know what’s going on. It’s hard to know by how you are describing things. There is definitely a lack of understanding on both sides, as well as lack of communication. We definitely need a ton of clarification. Wow – that seems insane.. Shaun wrote: This is a correct layout of what we currently have, host 1 and 2 he has setup as DC for the cluster because he states they need to be in there own domain.

What is holding the storage used by this ‘cluster’? Shaun wrote: We are a small agency and im pretty sure the over all server footprint we have is extremely bloated compared to what we actually need so I am hesitant to let him proceed now setting up a modern version of the older configuration.

You’re considering upgrading these systems? Shaun wrote: To clerify terminology “hyper-v core” was what I was told, when I hear core I think of the server core vs GUI install option. Things to remember Hyper-V is always free. It just is.

 
 

Windows server 2016 cluster standard vs datacenter free.Server 2016 Standard vs Datacenter

 
May 05,  · Windows Server will come up in two releases. Standard and Datacenter. The standard edition will however not contain some features that the Datacenter will provide. This wasn’t the case of the current Windows Server R2 where Standard and Datacenter editions provided the same features, but the only difference was in the possibilities to virtualize two . Aug 26,  · Windows Server Standard and Datacenter, Compared. As the name suggests, Datacenter Edition is suitable for large-scale virtualization and is used by enterprises with high workloads and high IT requirements. Datacenter Edition lacks all the limitations of the Standard Edition and also supports all the features available in Standard Edition.5/5(2). After installation, install the latest servicing package. Go to: Microsoft update catalog and search for “Windows Server ”. Evaluation versions of Windows Server must activate over the internet in the first 10 days to avoid automatic shutdown. The Nano Server deployment option in the Windows Server eval ISO is supported for host and.

 

[SOLVED] Datacenter setup and licensing – Windows Server – Locks and Limits

 
So the Standard Edition no longer has all the features of the Data Center Edition. The difference is mainly in the high-availability options. Windows Server Standard and Datacenter are both licensed by physical core. These licenses are sold in 2-packs and packs. Microsoft has. Windows Server Standard vs Datacenter. As the name implies, the Datacenter Edition suits companies with heavy workloads, large virtual.

 
 

Windows server 2016 cluster standard vs datacenter free

 
 
I know Scott said this already, but clustering is not a license function of Windows Server DataCenter edition. The technology relies on industry-standard servers with local-attached drives, and includes features such as caching, storage tiers, and erasure coding.

Vamtam
Vamtam

Lorem ipsum dolor sit amet consectetur adipiscing elit dolor