Windows server 2016 standard vs datacenter breakeven free.Windows Server 2016: Standard vs Datacenter
Windows Server is a server operating system created by Microsoft. Currently available in eight versions, Windows Server OS consists of approximately Our article is focused on Windows Server , the second most recent release which has been generally available since October 12, The operating system comes in two editions, Standard and Datacenter. The purpose of our article is to reveal the differences and similarities between the two Windows Server versions.
The key difference is in the type of workloads they can handle. Specifically, the Standard Edition does not provide some of the features available in Datacenter Edition.
The functionality of our product allows you to seamlessly back up your data while simultaneously ensuring the consistency of databases and applications. With a whole set of our features, you can ensure utmost data protection, improve backup performance, offload your network, and minimize expenses. Before proceeding to the comparison of Windows Server versions, let’s take a quick glance over the basic features the two editions share.
Of course, the entire list is not limited to the features outlined below, though the following definitely deserve special attention. New in , this is a server operating system with remote administration, designed for private clouds and datacenters. It is compact consumes little more than MB of disk space and approximately MB of memory , fast to set up, and largely undemanding when it comes to updates and system restarts.
This solution provides a way to create a highly scalable software-defined storage unit with basic features of a traditional SAN or NAS, all while still staying within your budget.
The technology relies on industry-standard servers with local-attached drives, and includes features such as caching, storage tiers, and erasure coding. There are two deployment options available: hyper-converged and converged, which greatly simplifies the deployment process. This technology enables you to upgrade the operating system of cluster nodes without needing to stop the Hyper-V or Scale-Out File Server workloads that are running on the nodes.
Put differently, this is a way to help minimize if not fully avoid downtimes. This functionality requires neither any additional hardware to use, nor the presence of a new cluster, and the upgrade process can be reversed unless you choose the “point-of-no-return”. This edition is a good choice for companies with small-to-medium IT infrastructure that are seeking a robust and efficient system.
Get the Free Trial now! As the name implies, the Datacenter Edition suits companies with heavy workloads, large virtual infrastructures, and high IT requirements. To further maximize efficiency, set up a schedule of your backup jobs to ensure that you avoid overlaps and reduce the risks from manual handling. At the time of release, Windows Server provided the market with quite a wide range of new features.
These include new functionality to enhance virtualization, administration, networking, security, storage efficiency, and so on. The release became a full-fledged solution which offered a smooth, hassle-free experience to its users. The difference between Windows Server Standard and Datacenter editions becomes particularly evident when it comes to virtualization, storage replication, containers a lightweight alternative to VMs , and inherited activation functionality. The Standard Edition is an optimal choice for infrastructures with comparatively low IT requirements.
In turn, the Datacenter Edition is in place to satisfy expectations at the enterprise level. Subscribe today to our monthly newsletter so you never miss out on our offers, news and discounts. Minimum order size for Basic is 1 socket, maximum – 4 sockets.
Virtual Appliance — Simplicity, Efficiency, and Scalability.
Windows server 2016 standard vs datacenter breakeven free
If the server fails, it stays down until the part is replaced. If it will take too long, you spin up the replica if it’s worth the potential 30 seconds – 15 minutes data loss. 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.
Note this is not the domain our agency actually uses is more of a workgroup for the hosts and iscsi. They are physical boxes so they both are using 16 core licenses each as that is the min for a server. The word cluster is miss leading to me because although he says it is a cluster if we lose 1 of the host nodes we lose the vms that are hosted on them until we can attach the vhd and bring them online on one of the other hosts.
If the foundation is ok to be hyper-v server then it brings licensing to question for me. I may be reading it wrong but the jist seams to be that we dont license the hyper-v foundation, but we do insure that we have enough core licenses to cover those machines if audited. 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.
We are working with r servers with 16 cores and 48 gigs of memory so nothing really good enough to handle more then 7 VMs max I would think. 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.
So those 4 hosts are hyper-v server, where as my thinking is we would need to be using server datacenter core instead, I understand it has a bigger footprint, but that is what my reading has pointed me to so far, which is what raised the questions about what he is actually doing and if it is being done correctly.
I think tommorow I will ask for some clerification since after re-reading this I am not certain he knew what he was talking about when providing the update today so I cannot say for certain that he installed server DC core or just the hyper-v server, on the 4 host nodes as he called them. This is getting confusing. So you aren’t talking about “clustering” in the traditional sense – shared storage and all that?
It seems like he is telling you what he’s doing, and you have absolutely no idea what’s going on. Then coming here and throwing around some of the terms you picked up from him talking about it, without understanding any of it. What it’s starting to sound like, is he has a 2-node cluster consisting of Host1 and Host2. I don’t know what you mean as DC There’s no way he has a Domain Controller to run two nodes in a server cluster, that just doesn’t make any sense.
What he presumably means, is that he has host1 and host2 in a 2-node cluster that share storage by some means assuming iSCSI because you mentioned that. Where is the shared storage located? Is it on a SAN? It could also mean he has host1 and host2 set up to BE the shared storage That said, they should be in the main domain.
If you don’t have one, why not? The domain controllers can be VMs on the hosts in the cluster. 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. Hi All, i’m hoping someone can help me out – i’m stumped.
In 25 years of windows, i’ve never seen this before. I found one reference in this thread:https Dilbert by Scott Adams Over the years, we’ve seen many conversations in our Community where IT professionals have discussed the use of buzzwords, from “cloud” to “Internet of Things” to “Future Proof.
Hi all,I have a user whose mailbox is used for sending customer invoices, so their sent items folder fills up every few months because of attached PDF’s. I can’t seem to find any way to create the rule where this user is the sender and the rule is to kick It’s the idea of planned obsolescence. I will be honest, I have considered the idea of company making faulty gea Your daily dose of tech news, in brief.
Is it already Monday? The weekend felt like it went by faster than usual. Speaking of time going by quickly, back on August 8, , when Netscape Communications went public, and turning an unprofitable inter Online Events. Login 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 Windows not using available RAM – Revisit Server Losing ability to connect to gateway Event id 41 on windows virtualized infrastructure. View all topics. 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. Restoring from VM backup it worth the few percent performance lost over bare metal. While you can configure the number of cores that SQL Server uses, that has nothing to do with licensing. Again, you can license Individual VM rather than the whole physical box. The minimum buy is 16 cores for a physical server — got it. Do I have to buy an additional 16 cores, or can I squeeze through with another 8 cores of licensing?
From the guide: Standard Edition provides rights for up to two OSEs or Hyper-V containers when all physical cores in the server are licensed. Not sure on the affect of having 2 NUMA nodes instead o 1. Pete, thank you! Hi all… trying to understand something. There have been references to the windows licensing PDF but i can see nothing in there to indicate you can do this.
Any thoughts? Your email address will not be published. Post Comment. I love teaching, travel, cars, and laughing. Want to advertise here and reach my savvy readers?
Licensing , SQL Server. Leave new Gianluca Sartori. Lorenzo J Huffman. Brent Ozar. Lorenzo is correct, you can license per VM rather than the whole physical box. Martin Guth. Phil Curtis. Jason A.
If you only need 4 cores, build a machine with only 4 cores. What kind of detail are you looking for?
Windows server 2016 standard vs datacenter breakeven free
While you can configure the number of cores that SQL Server uses, that has nothing to do with licensing. Again, you can license Individual VM rather than the whole physical box.
The minimum buy is 16 cores for a physical server — got it. Do I have to buy an additional 16 cores, or can I squeeze through with another 8 cores of licensing? From the guide: Standard Edition provides rights for up to two OSEs or Hyper-V containers when all physical cores in the server are licensed. Not sure on the affect of having 2 NUMA nodes instead o 1. Pete, thank you! Hi all… trying to understand something. There have been references to the windows licensing PDF but i can see nothing in there to indicate you can do this.
Any thoughts? Your email address will not be published. Post Comment. I love teaching, travel, cars, and laughing. Want to advertise here and reach my savvy readers? Licensing , SQL Server. Leave new Gianluca Sartori. Lorenzo J Huffman. Brent Ozar. Lorenzo is correct, you can license per VM rather than the whole physical box.
Martin Guth. Phil Curtis. Jason A. If you only need 4 cores, build a machine with only 4 cores. What kind of detail are you looking for? Pete Cousins. Let’s start with small and medium sized businesses SMBs. For SMBs with growing IT needs who require advanced features, support for remote offices, and a flexible way to virtualize their environment, Windows Server Standard may be an ideal fit.
Windows Server Standard provides rights for up to two Virtual Machines VMs or two Hyper-V containers, and the use of unlimited Windows Server containers when all server cores are licensed. Note: For every 2 additional VMs required, all cores in the server must be licensed again.
So if your customers have a single volume of data to be replicated, Windows Server Standard is a good option.
However, if your customer has more than just a single volume of data to be replicated, Windows Server Datacenter may be a better fit. Windows Server Datacenter is a good option for customers that have more demanding IT workloads, require advanced storage, virtualization, and application deployment. So customers with high virtualization needs can greatly benefit from Windows Server Datacenter.
Don’t forget, Microsoft has announced Windows Server End of Support EoS will be January 14, , and many of your customers will need to migrate to a new operating system before the EoS date! This is a great reason to reach out to customers, inquire about their current server infrastructure and their migration plans, and explain how pairing Windows Server OEM licensing from HPE with HPE ProLiant Gen10 Servers can provide them with a winning combination to help them transform their IT and keep up with modern demands.
Visit hpe. We encourage you to share your comments on this post. Comments are moderated and will be reviewed and posted as promptly as possible during regular business hours To ensure your comment is published, be sure to follow the Community Guidelines. Click here to learn more. Windows Server Resources Announcements Email us Feedback.
Log In. New Article. Windows Server Standard vs.