From a Windows admin since 1993: No wonder companies / people, at least in the country where I live, are leaving the Microsoft model. Licenses are so complicated it takes the fun and eagerness out of trying to get it right. And I mean that sincere. Tech admins as well as legal department do not want things overly complicated or they start looking at alternatives, even though they might be more expensive = paying to get it more simple in life.
@@joejoe2452 Our local Windows servers are slowly replaced with the same applications but running on NASes, BSD machines, Enterprise Linuxes as well as remotely hosted services. The company I work for right now: We're surprised that Microsoft slowly ruins their platform. A platform we've been on since the '90s. Too weird licensing is only ONE of the problems. And the sad thing for Microsoft is that we're not moving to Microsoft Azure. That TOO is too complicated. As developers of our own software we need the freedom to use the software and hardware we purchase as we please. We can't stand it when we're limited by silly outlined licenses. Nvidia is also out of the question.
It is not only the licencing model. The legal terms are impossible to understand since the terms are peppered with Microsoft terminology and product names (that change hourly). All product name are in camel case and each one requires you to understand today's use case for the product, as this impacts on the licencing model. There is a huge market opening up especially in the directory services space. I am sure either China or India will fill the gap. It is not that we can trust the USA anyway, since all information is made available to the intelligence agencies.
Excellent explanation of Microsoft's complicated licensing scheme. Can you clarify the part about not needing user CALs if users are already licensed with Microsoft 365 E5? Does this rule apply to on-prem hardware as well? For example, I have a physical server with Windows 2022 Datacenter acting as a Hyper-V host. All my users are licensed with Microsoft 365 E5 licenses. Do users still need a CAL to access the physical on-prem Hyper-V host?
Hi, thank you for this great video! I'm totally lost :D :D I have 3 servers (in cluster) each server have 2 physical processor with 20 core each (total of 6 processors and 120 cores). I will run on them 15 VMs. The total number of the employees/devices are 250. How should I license them?
The simplest is 120 SINGLE core licenses (60 2-core packs) of Windows Server Datacenter + 250 User CALs. If you plan giving remote access, add 250 RDS User CALs.
@@SAMexpertTV Thanks! What will happen if I only license 16 cores per server (if I license 48 cores instead of 120 for all 3 servers)? I'm I able to use the "non licenses" cores for VMs?
@@sashosimeonov7324 You will be non-compliant. You must license all cores. The alternative is to license each VM but licenses must match the edition of the VM, and you need at least 8 cores per license. And they must be subscription licenses or licenses with SA as well as all the CALs must be subscrtiption/SA. And then you need to pay attention to what OS you use as a hypervisor. One word: COMPLICATED.
I have small company with 30 pc users and still growing. Looking at the hpe proliant dl385 gen 11 for running reckon account hosted. Looking to run VMs on the server for remote access from other branch with 10 pc users. Windows server 2022 standard. What license do I need? Also is virtualisation different license from the windows server 2022 license? Do I buy the windows server 2022 license separate from the user licenses and also separate from the virtual machines license? Or maybe someone can recommend the right solution if I am confused?
Please review in the video the virtualisation section, Windows Server license stacking. There are exact formulas taking into account cores and the number of virtual machines. Also, review where I talk about Client Access Licenses + RDS CALs for remote access to the desktop.
I have all users licensed with Microsoft 365 E5 in a hybrid environment (on-prem & Azure). If I set up an isolated network and deploy clients and a Windows Server Standard 2022 host, are my CAL equivalents from my E5 licenses valid, even though the network has no internet or Azure connectivity nor an association with the corporate network? In short - is the important factor that we are the same organisation rather than some technical factor to benefit from CAL equivalence
@@SAMexpertTV thanks! I have another few of questions: 1) If I have Windows 10 Pro from the OEM of my equipment (purchased shortly before Windows 11 became GA), if I now want to go to Windows 11 Enterprise I believe I can do this by using the appropriate per user or per device licence from our EA. I am paying for the change in edition but don’t have to pay to go 10 to 11? Is this correct? If it is, why do MS appear to sell (per their Windows 11 Product Brief at least) a licence which upgrades Windows 10 to 11? 2) Is there a way to licence Windows 11 Enterprise on a per device basis but with the security features of Windows 11 Enterprise E5. The scenario is a laboratory computer used by multiple E5 licence holders, none of whom are not the primary user of the device by Microsoft’s definition 3) Regarding the entitlement to use virtual machines on Windows 11 Enterprise. I understand I either need per device licensing with SA or per user E3/E5 licensing. Does it matter what virtualisation technology I use (VMWare Workstation Pro in my case)? Provided I am compliant I assume I can achieve technical activation using our MAK for each VM?
Congratulations on the great work. I have a debt using vmware (bare metal) with windows server Standard. I need to license the virtual cores (vcores) or physical (host)?
What are the licensing requirements for disaster recovery? If you have a host with a mirror of your production VMs for example at a remote site that is not being actively used except in a disaster? If I understand it correctly, it doesn't have to be licensed but if you move to it you have to stay there for 90 days OR have software assurance. Any guidelines on that would be appreciated.
DR is a Software Assurance right with an equivalent in CSP. The backup servers MUST be off. The cluster MUST NOT have anything except backup instances.
Yes. Because each virtual thread will be then supported by one physical thread. And that’s what they want you to pay for. But why would you want hyper threading inside a VM? It makes no sense.
@@SAMexpertTV Oh, that's interesting. Can they insist on it because none of their documentation mentioned needing to license the virtual threads? At least the ones that I looked at keep mentioning virtual cores unlike SQL Server where they made a mention of threads. Unless I missed one major documentation that clearly called it out?
Nice videos, quick question if say I had VMware environment. 3 hosts with a small number of VM’s running windows server Can I use the Per VM windows server licensing model to license these VMs running on VMware? And if needed I can actually buy standard buy install data center for extra savings.
@@SAMexpertTV They can move between the hosts for a bit of resilience, which means if licensing by the traditional method, needing to increase license cont to make sure licenses available to cover in the event a VM could move for either maintenance or outage.
Hi Alex, Thank you for the great videos. I have interesting licensing scenario. If we have 3 host Hyper-V cluster with 2 VMs with Windows Server and 65(for example) Linux VMs. What is the license that is needed for the hosts Standard or DC? This is the definition of OSE: Operating System Environment. An “operating system environment” is: i. all or part of a physical or virtual (or otherwise emulated) operating system instance, that enables separate machine identity (primary computer name or similar unique identifier) or separate administrative rights, and instances of applications (if any), configured to run on the operating system instance or parts identified above. It is not stated Windows or Linux or whatever other OS.
muchas gracias por la información! saludos desde Ecuador, soy ingeniero en preventa y realmente la informaci[on que estas explicando me sirve un montón.
Hello, thank you for this great video! One question, if a client has perpetual license through OV and doesn't pay SA, can they add additional VMs (through CSP) on the same host with new licensing model (per VM)? Thank you
If in one cluster we have 23 Vm, where 20 vm is using standard os and 3 Vm using datacenter os. It is still required to license entire infra with datacenter or we can do use both Std. and Dc based licensing sepately in a cluster
Hello, I have purchased 48 Dell servers, each with 2 sockets and 28 cores per socket. They were supplied with OEM Windows Server 2022 Datacenter licenses per server, covering all cores. I am utilizing VMware vSphere for virtualization. How can I license all of my Windows Server 2022 virtual machines? I have been using the OEM keys to license each virtual server, but I have run out of activations and can no longer activate additional servers.
There are at least 2 basic scenarios: Windows Server Datacenter without (or with) SA, and Windows Server Standard 2022 with SA. But that’s just the start.
I have a question: my client wish to upgrade his licensing to windows server 2022 to his actual 16 core physical Server. But my cliente told me that he is going to buy a new physical Server in 3 months and he wishes to transfer (move) the 16 core windows server licenses to this new physical server. ¿Does CSP licensing work in this case? Either perpetual or suscription mode. I'll be really greatfull if you can help with this doubt 🙏🏼
Thank you for the video! Do I need active Software Assurance for my Windows Server and SQL Server 2022 licenses if I want to use colocation hosting (my own HW and SW)?
I have an on-prem server with dual CPUs and 28 cores each. There would only be 2-4 users. Would I then need 56 single core licenses to be fully compliant? Just curious, what happens if, theoretically, I only procured a 16-core license? Would only 16 cores be available to be assigned?
@SAMexpertTV I have 1 CPU Intel i9 14900 with 28 cores. Planning on getting Microsoft Data Center 2022. Would I then need 32 licenses (pack of 2 at 16 each pack per Core/ Cal) and 32 core licenses? Microsoft makes this confusing. This is for personal use at home running 1 or 2 docker container with 1 virtual machine to learn for school stuff as Im learning networking, cloud and security so I want to get a little ahead of the game so when I start working I have more experience with data center, not to mention without breaking my personal pc when learning how to scrip. Also will I be able to run 18 drives total at different drive capacities in a raid format, not sure if you can help me with these questions. Thanks in advance.
From a Windows admin since 1993: No wonder companies / people, at least in the country where I live, are leaving the Microsoft model. Licenses are so complicated it takes the fun and eagerness out of trying to get it right. And I mean that sincere. Tech admins as well as legal department do not want things overly complicated or they start looking at alternatives, even though they might be more expensive = paying to get it more simple in life.
And that's right. I agree with you, it has become too convoluted.
If you make a comment like that you should also recommend a better solution? What can replace windows server os?
@@joejoe2452 Our local Windows servers are slowly replaced with the same applications but running on NASes, BSD machines, Enterprise Linuxes as well as remotely hosted services. The company I work for right now: We're surprised that Microsoft slowly ruins their platform. A platform we've been on since the '90s. Too weird licensing is only ONE of the problems. And the sad thing for Microsoft is that we're not moving to Microsoft Azure. That TOO is too complicated.
As developers of our own software we need the freedom to use the software and hardware we purchase as we please. We can't stand it when we're limited by silly outlined licenses. Nvidia is also out of the question.
@@joejoe2452 No, he does not have to recommend a better solution. He is free to make his comment.
It is not only the licencing model. The legal terms are impossible to understand since the terms are peppered with Microsoft terminology and product names (that change hourly). All product name are in camel case and each one requires you to understand today's use case for the product, as this impacts on the licencing model. There is a huge market opening up especially in the directory services space. I am sure either China or India will fill the gap. It is not that we can trust the USA anyway, since all information is made available to the intelligence agencies.
Excellent explanation of Microsoft's complicated licensing scheme. Can you clarify the part about not needing user CALs if users are already licensed with Microsoft 365 E5? Does this rule apply to on-prem hardware as well? For example, I have a physical server with Windows 2022 Datacenter acting as a Hyper-V host. All my users are licensed with Microsoft 365 E5 licenses. Do users still need a CAL to access the physical on-prem Hyper-V host?
It's simple. E5 includes Windows Server, Exchange, SharePoint, SfB CALs for on-premises. It doesn't include SQL CAL however.
Hi, thank you for this great video! I'm totally lost :D :D I have 3 servers (in cluster) each server have 2 physical processor with 20 core each (total of 6 processors and 120 cores). I will run on them 15 VMs. The total number of the employees/devices are 250. How should I license them?
The simplest is 120 SINGLE core licenses (60 2-core packs) of Windows Server Datacenter + 250 User CALs. If you plan giving remote access, add 250 RDS User CALs.
@@SAMexpertTV Thanks! What will happen if I only license 16 cores per server (if I license 48 cores instead of 120 for all 3 servers)? I'm I able to use the "non licenses" cores for VMs?
@@sashosimeonov7324 You will be non-compliant. You must license all cores. The alternative is to license each VM but licenses must match the edition of the VM, and you need at least 8 cores per license. And they must be subscription licenses or licenses with SA as well as all the CALs must be subscrtiption/SA. And then you need to pay attention to what OS you use as a hypervisor. One word: COMPLICATED.
I have small company with 30 pc users and still growing. Looking at the hpe proliant dl385 gen 11 for running reckon account hosted. Looking to run VMs on the server for remote access from other branch with 10 pc users. Windows server 2022 standard. What license do I need? Also is virtualisation different license from the windows server 2022 license? Do I buy the windows server 2022 license separate from the user licenses and also separate from the virtual machines license? Or maybe someone can recommend the right solution if I am confused?
Please review in the video the virtualisation section, Windows Server license stacking. There are exact formulas taking into account cores and the number of virtual machines. Also, review where I talk about Client Access Licenses + RDS CALs for remote access to the desktop.
I have all users licensed with Microsoft 365 E5 in a hybrid environment (on-prem & Azure). If I set up an isolated network and deploy clients and a Windows Server Standard 2022 host, are my CAL equivalents from my E5 licenses valid, even though the network has no internet or Azure connectivity nor an association with the corporate network?
In short - is the important factor that we are the same organisation rather than some technical factor to benefit from CAL equivalence
The licenses are valid.
@@SAMexpertTV thanks! I have another few of questions:
1) If I have Windows 10 Pro from the OEM of my equipment (purchased shortly before Windows 11 became GA), if I now want to go to Windows 11 Enterprise I believe I can do this by using the appropriate per user or per device licence from our EA. I am paying for the change in edition but don’t have to pay to go 10 to 11? Is this correct? If it is, why do MS appear to sell (per their Windows 11 Product Brief at least) a licence which upgrades Windows 10 to 11?
2) Is there a way to licence Windows 11 Enterprise on a per device basis but with the security features of Windows 11 Enterprise E5. The scenario is a laboratory computer used by multiple E5 licence holders, none of whom are not the primary user of the device by Microsoft’s definition
3) Regarding the entitlement to use virtual machines on Windows 11 Enterprise. I understand I either need per device licensing with SA or per user E3/E5 licensing. Does it matter what virtualisation technology I use (VMWare Workstation Pro in my case)? Provided I am compliant I assume I can achieve technical activation using our MAK for each VM?
Congratulations on the great work. I have a debt using vmware (bare metal) with windows server Standard. I need to license the virtual cores (vcores) or physical (host)?
Please elaborate on the detailed configuration. Also what licenses do you have?
What are the licensing requirements for disaster recovery? If you have a host with a mirror of your production VMs for example at a remote site that is not being actively used except in a disaster? If I understand it correctly, it doesn't have to be licensed but if you move to it you have to stay there for 90 days OR have software assurance.
Any guidelines on that would be appreciated.
DR is a Software Assurance right with an equivalent in CSP. The backup servers MUST be off. The cluster MUST NOT have anything except backup instances.
If hyper-threading is enabled in the virtual machine, then do I need to consider logical cores for the windows server license calculations?
Yes. Because each virtual thread will be then supported by one physical thread. And that’s what they want you to pay for. But why would you want hyper threading inside a VM? It makes no sense.
@@SAMexpertTV Oh, that's interesting. Can they insist on it because none of their documentation mentioned needing to license the virtual threads? At least the ones that I looked at keep mentioning virtual cores unlike SQL Server where they made a mention of threads. Unless I missed one major documentation that clearly called it out?
Check where they talk about virtual cores supported by more than one hardware thread. It’s enough.
@@SAMexpertTV Gah, you're right. How could I have missed that! Thanks.
Nice videos, quick question if say I had VMware environment. 3 hosts with a small number of VM’s running windows server
Can I use the Per VM windows server licensing model to license these VMs running on VMware? And if needed I can actually buy standard buy install data center for extra savings.
Is licensing Windows Server per VM cheaper?
@@SAMexpertTV They can move between the hosts for a bit of resilience, which means if licensing by the traditional method, needing to increase license cont to make sure licenses available to cover in the event a VM could move for either maintenance or outage.
@@RobertGilliland-bw1vi it’s a video reply :) Please watch it.
Hi Alex,
Thank you for the great videos.
I have interesting licensing scenario. If we have 3 host Hyper-V cluster with 2 VMs with Windows Server and 65(for example) Linux VMs. What is the license that is needed for the hosts Standard or DC?
This is the definition of OSE: Operating System Environment. An “operating system environment” is:
i. all or part of a physical or virtual (or otherwise emulated) operating system instance, that enables separate machine identity (primary computer name or similar unique identifier) or separate administrative rights, and instances of applications (if any), configured to run on the operating system instance or parts identified above.
It is not stated Windows or Linux or whatever other OS.
You’re overthinking it :) Only count Windows Server VMs.
Thanks for the answer @@SAMexpertTV
muchas gracias por la información! saludos desde Ecuador, soy ingeniero en preventa y realmente la informaci[on que estas explicando me sirve un montón.
De nada :)
Hello, thank you for this great video! One question, if a client has perpetual license through OV and doesn't pay SA, can they add additional VMs (through CSP) on the same host with new licensing model (per VM)? Thank you
Yes but they will also need CALs with SA.
@@SAMexpertTV Just for employees that approach to that VMs (CSP), or to all employees?
@@NikolaVuckovic-k2t can you with 100% certainty prove limited access, including indirect?
If in one cluster we have 23 Vm, where 20 vm is using standard os and 3 Vm using datacenter os. It is still required to license entire infra with datacenter or we can do use both Std. and Dc based licensing sepately in a cluster
Since version 2022, it’s no more a simple question. There a per vm option now.
Hello,
I have purchased 48 Dell servers, each with 2 sockets and 28 cores per socket. They were supplied with OEM Windows Server 2022 Datacenter licenses per server, covering all cores. I am utilizing VMware vSphere for virtualization. How can I license all of my Windows Server 2022 virtual machines? I have been using the OEM keys to license each virtual server, but I have run out of activations and can no longer activate additional servers.
Hi. I would ask Dell. They must support OEM licenses.
Awesome video,
Let’s say I have 5 esxi hosts and 250 servers (VMs) how should I go about licensing those VMs. Windows server 2022 standard.
There are at least 2 basic scenarios: Windows Server Datacenter without (or with) SA, and Windows Server Standard 2022 with SA. But that’s just the start.
With this density of VMs you will probably pay less in the first scenario but it depends on the number of cores in the hosts. You need a calculator.
@@SAMexpertTV so you think one datacenter 16 core would suffice?
@@javalex561 have you watched the video? You need to license all cores in the cluster.
I have a question: my client wish to upgrade his licensing to windows server 2022 to his actual 16 core physical Server. But my cliente told me that he is going to buy a new physical Server in 3 months and he wishes to transfer (move) the 16 core windows server licenses to this new physical server.
¿Does CSP licensing work in this case? Either perpetual or suscription mode.
I'll be really greatfull if you can help with this doubt 🙏🏼
They can move the licenses unless the one they have is an ORM license. but do they have enough to cover the new server’s cores?
Thank you for the video! Do I need active Software Assurance for my Windows Server and SQL Server 2022 licenses if I want to use colocation hosting (my own HW and SW)?
Do servers on collocation require software assurance
Thanks for the all the information
its really helpful... where's excel formula
On the slide, isn’t it?
I have an on-prem server with dual CPUs and 28 cores each. There would only be 2-4 users. Would I then need 56 single core licenses to be fully compliant? Just curious, what happens if, theoretically, I only procured a 16-core license? Would only 16 cores be available to be assigned?
It should work, although I haven't tried it. But you will be in legal breach of license compliance.
@SAMexpertTV I have 1 CPU Intel i9 14900 with 28 cores. Planning on getting Microsoft Data Center 2022. Would I then need 32 licenses (pack of 2 at 16 each pack per Core/ Cal) and 32 core licenses? Microsoft makes this confusing. This is for personal use at home running 1 or 2 docker container with 1 virtual machine to learn for school stuff as Im learning networking, cloud and security so I want to get a little ahead of the game so when I start working I have more experience with data center, not to mention without breaking my personal pc when learning how to scrip. Also will I be able to run 18 drives total at different drive capacities in a raid format, not sure if you can help me with these questions. Thanks in advance.
Very very cool video, Iiteraly work with this scenarios every day and this refresh information it's really helpfull!! Regards from México 👍👍👍
Glad it helped :) The recent changes are significant.
Leave it to MSFT to complicate things
They never seize to deliver, do they?
@@SAMexpertTV they should do Ubuntu license 😂