Windows Server 2019 Datacenter Iso File Download
Amabella Tevebaugh
I looked it up on Wikipedia, and Datacenter comes with more features. But does that mean more bloat, and services by default? (I would use the system for desktop use/virtualization/development.)
The Datacenter edition is designed for "large-scale virtualization of workloads that require the highest levels of scalability, reliability, and availability to support large, mission-critical applications." -us/server-cloud/windows-server/2008-r2-datacenter.aspx
Virtualization itself will run just fine on Standard, and based on your description it appears you're running tests and labs and such. I'd stick with Standard unless you have a specific need to learn and understand Datacenter.
I'd imagine, though, that the differencse have to do with how the OS prioritizes different processes and systems. A prioritization structure that is best for file and application servers may not be best for virtualization servers, which may, in turn, not be best for SQL servers.
Considering the Datacenter edition can be configured as a Core install, though, seems to me to indicate it is less about out-of-box resource consumption. Installing the two side-by-side in clean states may not appear to be very different.
Regarding whether or not MS has more services set to start by default in one or the other: I've had a little experience with Standard, and very little unnecessary stuff is installed. It's a pretty light (by MS standards) OS in it's clean state. And a version designed for high-availability, high-load systems would seem to me to put a premium on minimizing the default footprint even more so.
It also appears to be, as in the difference between Enterprise and Standard, to be about licensing. Datacenter version includes "unlimited virtualization rights", which isn't about differences in code so much as differences in licensing.
For example, most of my servers (all virtualized via VMWare running on ESXi hosts) need to handle between 1 and 8 cores, and between 4 and 32GB memory. This puts me well below the base requirements of Datacenter. So for me, the Standard and Enterprise versions are "better". I run a few Enterprise licenses and a few Standard, just because that's how they were purchased in our MS Licensing Agreement.
If you've got a system with loads of CPUs and scads of memory and you need to run huge apps on a very high-availability system or run VMs based on the MS Hypervisor, you may find the Datacenter version is "better" for you.
We have a Vcenter with 5 nodes, they are Single CPU Intel(R) Xeon(R) Gold 6210U CPU @ 2.50GHz, which I believe are 20 cores. I want to redo our three Domain Controllers to start and then move on later to some other servers to upgrade. But currently, we have 2012r2 and 2016 on those so I want to get them updated and raise domain-level functions as well for AD.
To fully license a host with 20 cores, you need to buy one 16 core standard pack and TWO 2 core standard packs to total 20. (I typically counsel folks to NOT buy hardware with more than 16 cores for most smaller environments).
If you want ANY of the 5 physical hosts to be able to operate ALL 10 VMs at any given time, then you need 25 standard licenses for Windows Server and assign 5 per host. That gives you UP TO 10 VMs on each host at any time. (This is NOT what I'd recommend, but it's what you need if you don't want restrictions on what you run and from where).
Just a FYI. Per Microsoft licensing rules, each ESXi host has to have a licensed if you are going to run virtualized Windows Servers on every host (DRS, HA, etc). In addition, standard only allows for 2 VM's per license. Therefore, you really need datacenter edition unless you are going to limit each host to only two Windows VM's. Since we have an ELA and have to "true up" every year, I have to report all of this to keep our licensing in check. We have 50 ESXi host and have a Windows Server Datacenter edition for each host.
We have like 80 VM's in the Vcenter, but there is just a handful running Windows Server, 5 are core Windows servers the rest are just hosting files and applications, etc. Also, I have a bunch running 2019 so not too concerned about moving those to 2022 yet. That count seemed right to me, Also I would have a rule on the Vcenter to not put those all on the same host, as they are 3 domain controllers, they would live on separate hosts, so there shouldn't be more than 2 in theory on each Esxi host, unless there was type of outage/ or failure causing vmotion. I really just want to get these update as they are the last servers to do, being they are one 2012 and its EOL.
Just keep that in mind if you get more than that. I have been through a MS audit and it is very detailed and last for several month. If it happens and you are out of compliance it will be a bill to bring you in line with no discounts. Full market price for each license needed.
@Rodney, If I buy the 6x 16 core + 2x 2core to cover what i want now. If I decided to upgrade more servers, it should just be an addon for the additional VM's correct? If so...then I would by 2 core packs?
I have other servers, but I am only looking at upgrading 3 immediately and possible max 10, other servers don't need to be updated. I have appliances, wireless controllers, virtual phones switches, etc, or just windows 10/11 VM's or Linux.
To be certain, I would double check with your licensing provider to verify. However, it does look like 2022 standard does allow what Microsoft calls "stacking" comes in based on what I found below. We run datacenter so I am more familiar with that licensing than standard.
Reminder - licenses - CALs, Windows Server, etc., if they are transferrable (OEM are not in the US) may only be transferred once every 90 days OR under exceptional circumstances (employee terminated and replaced, hardware fails PERMANENTLY).
Client Access Licenses (CALs) are rights to use the software. There are several different types of CALs for server software and, generally speaking, CALs are ADDITIVE - having a "more expensive" CAL does not include the other related CALs you might need.
All users or devices (or a combination) must have user CALs equivalent to the highest version of Windows server users use. MOST of the time, companies want to license by USER. However, in a school environment, it MIGHT be more appropriate to get some device CALs too. It all depends on remote access. If the students access the network remotely, then USER CALs are almost always the better choice. If there are computers where people would ONLY use them in school and some of those people would NEVER use another computer, then a DEVICE CAL is the better choice.
You have 500 students and 300 computers. 50 computers are used exclusively by staff and that staff will remote into the computers to work (admin work, teachers planning, etc). Then you should PROBABLY get 50 USER CALs for the staff and 250 DEVICE CALs for the student computers that any given student might use at any given time. The teachers can then use any computer (because they are licensed by the human) while the students can access any of the 250 computers setup for students but technically can't touch the staff computers.
If you don't want to license each host for all 10 Windows VMs (I'm assuming the other VMs are Linux VMs), then I would recommend picking two or three hosts and then decide you will NEVER transfer VMs to either of the other hosts and/or recognize if you do, they must live there for 3 months). From what you describe, I would say you don't need to get Datacenter - it would probably be more cost effective to get standard licenses. But if you plan on migrating hosts with the Windows VMs you need to keep in mind the licensing restrictions and follow them when you move the servers around OR buy enough Windows Server licenses so you don't have to worry about it.
The above prices are what I would be selling to an educational institution. If you truly qualify as education by Microsoft's standards (I would think, but I cannot declare that you do), then those are the prices I would expect you would be required to pay.
A print server using Windows Server requires a CAL.. Since there aren't print server cals the server CAL is all you need and it covers ALL Windows Servers (be careful there are Standard CALS and Enterprise CALS) If you have any windows datacenter editions on your network you need Enterprise CALS (user or device)
The RDS User CALs are not assigned directly to AD user accounts. When you use the Per User model, licensing is not enforced and each user is granted a license to connect to an RD Session Host from any number of devices. The license server issues licenses from the available RDS CAL pool or the Over-Used RDS CAL pool.
Lets say you have 10 Server 2012R2 servers if you buy Server 2012 CAL's then if you add a newer computer with Server 2016 you have to repurchase all the CAL's again. So what I would advise is buy the highest server year CAL's.. As of today that is 2022 CAL's which makes you ok if you are audited even if you have mostly Server 2016 Standard Servers and a Server 2016 Standard server and a bunch of Server 2008R2's
My statement regarding CAL requirements was misleading, apologize. I was responding to the idea that a print server did not require CALs. There are certain Microsoft products that do not require CALs, but if you use Windows Server Standard or Windows Server Data Center (as opposed to Windows Server Essentials, or the old Foundation server), you are required to have a CAL for each person or device accessing the server. EVEN in a network with Essentials. In an Essentials network, once you add a Windows Server Standard, you MUST acquire CALs. But that is not what this network is. This is CLEARLY a network with Windows services based on Windows Server editions that require CALs.
We have windows server datacenter 2022 which is overutilized and standard 2022 which is underutilized , since datacenter is overutilized so I need to consume overutilized license to standard 2022 since, we have SA that we can use standard too.
d3342ee215