jason scotly
asked on
Windows Server 2016 licencing confusion?
Greetings,
I have one question regarding Windows Server licencing and I do not understand that part.
I am using Windows Server 2016.
I have a licence where said Windows Server 2016 / 10 cores per server. What does that mean in practical explanation?
Next, I have CAL fpr win2016 serv = 25 CALs - that means I can add 25 machines/ users to Active Directory and they can access server, or I can use the same licence key for 25 devices, including client and server machines?
Thank you
I have one question regarding Windows Server licencing and I do not understand that part.
I am using Windows Server 2016.
I have a licence where said Windows Server 2016 / 10 cores per server. What does that mean in practical explanation?
Next, I have CAL fpr win2016 serv = 25 CALs - that means I can add 25 machines/ users to Active Directory and they can access server, or I can use the same licence key for 25 devices, including client and server machines?
Thank you
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Regarding the CPU/Core licenses, you will have to look up the exact specfication for the license, because there are allowed copies to run VMs involved. IIRC the 10 cores can be used up for more than one server if in the same infrastructure (the same physical host).
Your user CALs are bound to named users - but you can reuse licenses for deactivated users. You just cannot share licenses, e.g. between shifts.
The number of users in AD does not need to correspond to number of CALs. You might have accounts only used on the server itself, for example, and you do not need to disable/remove inactive accounts. But doing the latter makes it much easier in case of a license audit.
Your user CALs are bound to named users - but you can reuse licenses for deactivated users. You just cannot share licenses, e.g. between shifts.
The number of users in AD does not need to correspond to number of CALs. You might have accounts only used on the server itself, for example, and you do not need to disable/remove inactive accounts. But doing the latter makes it much easier in case of a license audit.
ASKER
Thank you for help. Where can I find information about exact specification of licence, I have only information Windows Server 2016 / 10 cores per processor.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you. If am using VMware ESX host and I have license which I mentioned in post, will I be able to install two VMs (WS 2016) and use the same license for them, or that is only valid if I am using host with Windows Server 2016 which handle Hyper V, wherw I can install two VMs.
thank yoh cery much
thank yoh cery much
Every Windows Server 2016 license requires the purchase of eight 2-Core packs to be a valid license. HOWEVER, if your server has more than 16 TOTAL physical cores (as opposed to assigned VM CPUs/Cores), then you need to purchase additional 2 core packs until the total number of licensed cores is covered.
Every Windows Server 2016 Standard "full" license (8+ cores) allows you to run 2 VMs on the same physical hardware you assign the license to.
If you want more than 2 Windows VMs, you buy another 8+ cores (again, depending on physical cores in the hardware) and you get another license.
If you purchase a Data Center License of Windows Server (sold by the core as well), then you can run unlimited (by licensing) Windows VMs on the physical server the 2016 Data Center license is assigned to.
Licenses are (assuming NOT OEM) transferrable once every 90 days.
With regards to CALs, Microsoft does not license by the account or by the concurrent user. Every human being (NOT user account and NOT concurrent connection) who is going to use ANY resource provided by Windows (including, for example, File Shares, DNS, DHCP, etc) REQUIRES a User CAL (if you chose to license by user as makes the most sense in most environments). Microsoft also licenses by Device as an option but in MOST environments, this would be more costly (again, every device must then be licensed and if you have employees with network printers, cell phones, tablets, laptops, remote access, desktops, etc all for ONE person it makes far more sense to license that person than EACH of that person's devices.
Lastly, you should keep this in mind:
Licensing Disclaimer
License information provided here is "best efforts". The comments of the respondents are based on interpretation of the license agreements and their knowledge of the particular laws and regulations in their geographic location. Laws in your location may invalidate certain aspects of the license and/or licenses can change. "They told me on Experts-Exchange" will not be a valid excuse in an audit. You need to contact the license granting authority to confirm any advice offered here.
Every Windows Server 2016 Standard "full" license (8+ cores) allows you to run 2 VMs on the same physical hardware you assign the license to.
If you want more than 2 Windows VMs, you buy another 8+ cores (again, depending on physical cores in the hardware) and you get another license.
If you purchase a Data Center License of Windows Server (sold by the core as well), then you can run unlimited (by licensing) Windows VMs on the physical server the 2016 Data Center license is assigned to.
Licenses are (assuming NOT OEM) transferrable once every 90 days.
With regards to CALs, Microsoft does not license by the account or by the concurrent user. Every human being (NOT user account and NOT concurrent connection) who is going to use ANY resource provided by Windows (including, for example, File Shares, DNS, DHCP, etc) REQUIRES a User CAL (if you chose to license by user as makes the most sense in most environments). Microsoft also licenses by Device as an option but in MOST environments, this would be more costly (again, every device must then be licensed and if you have employees with network printers, cell phones, tablets, laptops, remote access, desktops, etc all for ONE person it makes far more sense to license that person than EACH of that person's devices.
Lastly, you should keep this in mind:
Licensing Disclaimer
License information provided here is "best efforts". The comments of the respondents are based on interpretation of the license agreements and their knowledge of the particular laws and regulations in their geographic location. Laws in your location may invalidate certain aspects of the license and/or licenses can change. "They told me on Experts-Exchange" will not be a valid excuse in an audit. You need to contact the license granting authority to confirm any advice offered here.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Likewise to Server Licenses, CALs are transferrable once every 90 days UNLESS an employee leaves the company/device fails completely. Then the transfer may take place sooner. This 90 day limit is why concurrency doesn't work. Again License Disclaimer applies.
ASKER
Thank you for help. I understand everything.
ASKER
I installed Windows Server 2016 as a virtual machine on VMware ESXi server and it is time for licensing.
Licence - Windows Server 2016 / 10 cores - can be installed only on one server with 10 cores? Can I use that license and install more Windows Servers?
If I have only 25 CALs, and I'm using all of them, will I be able to add more users to AD DS or not, will I get some warning?
Also, If I want to add additional 10 users, I need to buy 10 CALs?
If two users left the company, I can delete them, and add another two users with that 2 CALs?
Thank you