CAL = Client Access License, i.e. Client Access License (Client License)

Often Microsoft software is licensed under the Server+CAL model (Server License + Client Access License). In this case:

• A server license is required for each running instance of the product, and
• A Client Access License (CAL) is required for each user or device that has access to the Server or uses any functions/services/services of the Server

CALs for the same product do not need to be duplicated. Those. no matter how many, for example, Windows Server is installed and running in an organization, you only need one Windows Server CAL per user or device.

CALs must be purchased for all products used. That is, for example, if an organization uses Windows Server and Exchange Server, then client licenses must be purchased for both Windows Server and Exchange Server. The quantity may vary.

Each User CAL or Device CAL must be permanently assigned to a user or device, respectively. CALs can only be reassigned if the user is not present or the device is not working.

"Per User" or "Per Device"

Device Client Access License (Device CAL). If the organization has fewer devices than users (for example, several people work in shifts on one computer) or devices are easier to account for, then it is better to purchase Device CAL.

User Client License (User CAL). If the organization has fewer users than devices (for example, many users have both a desktop computer and a laptop) or users are easier to account for, then it is better to purchase a User CAL.

Previously, the price for User CAL and Device CAL was the same. But the world is changing, devices are getting cheaper, labor is getting more expensive. The practice of using a large number of different devices by one user is already widespread. Apparently, in this regard, since December 2012, Microsoft has raised prices for User CAL.

The choice of User CAL or Device CAL must be approached carefully, because you can change one license to another only when you upgrade your SA subscription. Which licenses to buy - User CAL or Device CAL - each organization decides for itself.

Core CAL Suite and Enterprise CAL Suite

CALs must be purchased for each product you use. If an organization uses a small number of Microsoft products (for example, only Windows Server), then it is more profitable to buy only Windows Server CALs. If your organization uses a large number of Microsoft products, then it may be more profitable to buy them all together in one Core CAL Suite or Enterprise CAL Suite.

Core CAL Suite includes client licenses:

• Microsoft Windows Server CAL
• Microsoft SharePoint Server Standard CAL
• Microsoft Exchange Server Standard CAL
• Microsoft System Center Configuration Manager Client Management License
• Microsoft System Center Endpoint Protection (antivirus client and subscription service)
• Microsoft Lync Server Standard CAL

Enterprise CAL Suite includes client licenses:

• All licenses included in the Core CAL Suite
• Microsoft Exchange Server Enterprise CAL
• Microsoft SharePoint Server Enterprise CAL
• Microsoft Lync Server Enterprise CAL
• Microsoft Windows Server Active Directory Rights Management Services CAL

Remote Desktop Services CAL

Remote Desktop Services CAL (licenses for accessing the desktop on the server - formerly "terminal" licenses)
Needed for those users or devices that connect to the desktop on the server via RDP (terminal connection).

Product description

Software Microsoft Windows Server CAL is a legal document (not software) that authorizes a user to access a Windows server on a network. A client license is needed: to access the server from a device on the network, or remotely, regardless of the OS used; to use the underlying server services. Under this licensing scheme, the total number of client licenses must be equal to the total number of client PCs or users on the network.

A Microsoft Windows Server CAL is required for Microsoft Windows Server Standard and Datacenter editions. In addition, incremental CALs are purchased in addition to the Microsoft Windows Server CAL for access to Remote Desktop Services (RDS CAL) and Active Directory Rights Management Services (AD RMS CAL).

Microsoft Windows Server CALs can be per device and per user. Device license allows any number of users to access the server software from a single device. This type of CAL is useful for organizations where multiple users work on the same device.

User License allows a single user to access the server software from any number of devices. This type of CAL is useful for organizations with many mobile workers who need to access the corporate network from arbitrary devices, or employees who use multiple devices to access the network.

New in Windows Server 2016

Windows Containers: Support for containers in Windows Server 2016 brings performance improvements, simplified network management, and the use of Windows Containers in Windows 10.

Nano Server

The module for creating Nano Server images has been updated in Nano Server. This update includes additional feature separation between the physical host and guest virtual machine, as well as support for different editions of Windows Server. In addition, the Recovery Agent has been improved to distinguish between firewall rules for inbound and outbound traffic, and the ability to restore WinRM service settings has been added.

Remote Desktop Services

Deploying a highly available Remote Desktop Services environment allows you to use Azure SQL Database for RD Connection Brokers in high availability mode.

Identity and access

The new identity components increase the level of security for organizations' Active Directory environments, as well as help move towards cloud-only deployments and hybrid deployments where some applications and services are hosted in the cloud and others are hosted on-premises.

Active Directory Certificate Services

What's new in Active Directory Certificate Services. For Active Directory Certificate Services (AD CS), Windows Server 2016 has increased support for TPM key attestation. You can now use KSP smart cards for key attestation. For non-domain-joined devices, you can now use NDES enrollment to obtain a certificate that can be attested for keys in the TPM.

Active Directory Domain Services

AD DS includes enhancements to help organizations secure Active Directory environments and improve the efficiency of identity management tasks for corporate and personal devices.

Active Directory Federation Services (AD FS)

Active Directory Federation Services (AD FS) in Windows Server 2016 includes new features that allow you to configure AD FS to authenticate users stored in LDAP directories.

Web Application Proxy

The latest version of Web Application Proxy provides new features for publishing and pre-authenticating additional applications, as well as a better user experience.

Control and automation

Windows PowerShell 5.0 includes important new features, including support for class-driven development and new security features that enhance usability, improve usability, and make it easier to manage Windows environments comprehensively.

Software Defined Networking

Mirroring and traffic routing for new or existing virtual appliances is now available. Together with the distribution of the firewall and network security groups, the user gets the ability to dynamically segment and protect workloads in the same way as in Azure. In addition, you can deploy and manage an entire stack of software-defined networking (SDN) using System Center Virtual Machine Manager.

Improved TCP performance

The default initial congestion period (ICW) has been increased from 4 to 10, and the TCP Fast Open (TFO) feature has also been implemented. TFO reduces the time it takes to establish a TCP connection, and a longer ICW period allows larger objects to be transferred as part of the initial send. This combination can significantly reduce the time it takes to transfer an Internet object between a client and the cloud.

Just Enough Administration

Just Enough Administration in Windows Server 2016 is a security technology that allows you to delegate administration of all components that can be managed through Windows PowerShell. Features include support for executing with a network identity, connecting via PowerShell Direct, securely copying files to and from JEA endpoints, and configuring the PowerShell console to run in the default JEA context.

Credential Guard

To protect secrets, Credential Guard uses virtualization-based security to ensure that only privileged system software can access these data.

Remote Credential Guard

Credential Guard supports RDP sessions so that user credentials remain on the client side and are not exposed on the server side. It also provides single sign-on for remote desktop.

Device Guard (code integrity)

Device Guard enforces Kernel Mode Code Integrity (KMCI) and User Mode Code Integrity (UMCI) by creating policies that specify what code can run on the server.

Shielded VMs

Windows Server 2016 provides new Hyper-V-based shielded VMs to protect any Generation 2 VM from a compromised fabric.

Windows Defender

Windows Server Antimalware will update antimalware definitions and protect a computer without a user interface.

Control flow protection

Control Flow Guard (CFG) is a platform security component designed to address memory corruption vulnerabilities.

Direct Mount Storage Spaces

Storage Spaces Direct allows you to create highly available, scalable storage using local storage servers. They simplify the deployment and administration of software-defined storage systems and open up the possibility of using new classes of disk devices, such as SATA SSD and NVMe.

As part of

All Softline customers who have purchased Microsoft licenses will be able to receive standard and extended support free of charge, including on-site support!

Product Licensing

Windows Server 2016 licensing models

Windows Server 2016 has two licensing models: core-based and Client Access Licenses (CALs). For Windows Server Standard, Datacenter, or Multipoint editions, each user and/or device must purchase a Windows Server CAL or a Windows Server and Remote Desktop Services (RDS) CAL. The Windows Server CAL entitles a user or device to access any edition of Windows Server that is the same or earlier. The Window Server CAL provides access to multiple Windows Server licenses.

Windows Server 2016 licenses for Standard and Datacenter editions are based on cores, not processors. This model is better suited for multi-cloud environments, simplifies the migration of Windows Server workloads with the Azure Hybrid Benefit, and reduces discrepancies between different licensing methods.

To use Remote Desktop Services, Active Directory Rights Management Services, and other additional and enhanced features, you must purchase special CALs.

Windows Server 2016 Standard and Datacenter Editions: Licensing by Core

• All physical server cores are subject to licensing. The cost of a license for each physical server is determined based on the number of processor cores installed in it.
• Each server must be licensed for at least 16 cores.
• Each physical processor must be licensed for a minimum of 8 cores.
• Licenses will be sold in sets of two cores.
• You must purchase at least eight sets of two-core licenses for each physical server. The cost of a license for two cores is one eighth of the cost of a license for two processors of the corresponding edition of Windows Server 2012 R2.
• The Standard Edition entitles you to two OSEs or two Hyper-V containers if all of the server's physical cores are licensed. For every two additional virtual machines, relicensing of all server cores is required.
• The 16-core license for Windows Server 2016 Datacenter and Standard editions is the same as the two processor licenses for the corresponding editions of Windows Server 2012 R2.

Up to 8 cores per processor and 16 cores per server: Customers will be licensed for a minimum of 8 cores per processor or 16 cores per server.

More than 8 cores per processor and 16 cores per server: Customers will receive licenses for servers with more than 8 cores per processor or 16 cores per server.

License to connect a user or computer to any number of Windows Server 2012 servers

What is Windows Server CAL

Per licensing policy, Windows Server Standard 2012 requires Windows Server CALs for every user or device accessing the server.

Situations where CALs are not required:

for access to the server from another licensed server, as well as for access for the purpose of administration from a maximum of 2 users or devices;

if the server is running a web workload or an HPC workload.

to access the physical environment that is used solely for the purpose of hosting and managing virtual environments;

if it is a peripheral device (such as a printer) that does not access the server.

Some additional or advanced features also require the purchase of an additional CAL, such as the Remote Desktop Services (RDS) CAL.

Access to a server running Windows Server 2012 R2 requires only a Windows Server 2012 CAL. Previous versions of CAL cannot be used.

Types of Windows Server CALs

Windows Server CAL licensed per device or user.

Windows Server CAL Device CAL

A Windows Server 2016 Device Client Access License (Device CAL) is a Device Client Access License that grants the right to connect to any number of servers from a single device. Device, or a device with this license, can be used by any of the users and connect to servers, including previous versions. To calculate the required number of such licenses, simply count the number of devices that will be used to connect to servers in the future.

Remote Desktop Services CAL

Windows Server 2016 client access license through Remote Desktop Service. Licensed by device or user. To access via Remote Desktop (Windows Remode Desktop Service) you need to have 2 licenses: Client Access License + Remote Desktop Services CAL.

Windows Server CAL Licensing Considerations

The Microsoft Open License Program (OLP) is a volume licensing program that allows you to purchase software licenses at a lower price than boxed retail prices.

Windows Server CALs purchased through the OLP program are perpetual and allow connection to current and previous versions of Windows Server. The OLP license is not bound to the hardware, it is tied to the organization for which the Windows Server CAL will be issued.

After purchasing a Windows Server CAL OLP license on the Microsoft VLSC website, the buyer will be given access to a personal account in which information about the number of purchased licenses will be available. Client Access licenses do not have activation keys (access opens in approximately 1-2 business days).

Initial order for Windows Server CAL under the OLP program - 5 licenses. All the following orders can be for any number of licenses starting from 1 pc.

After that, a license agreement and closing documents will be sent to your address by Russian post. (Invoice, Act on the transfer of rights, notification of the simplified tax system)

On this page you will find examples of typical and simple scenarios for using Microsoft servers. For more complex cases, use combinations of these simple examples.

Briefly about the main:

Examples:

Three people using three devices use one instance of Windows Server on one server. At the same time or in turn - it does not matter.

Need for licenses:

1. Three Windows Server CALs for three devices that people use the server with.

Three people using five devices use one instance of Windows Server on one server. At the same time or in turn - it does not matter.

Need for licenses:

1. Licenses for all physical cores in the server. But at least 16 licenses per server.
2. Three Windows Server CALs for three people using the server.

Three people using five devices are using two instances of Windows Server on two different servers. At the same time or in turn - it does not matter.

Need for licenses:

Three people using three devices are running two instances of Windows Server on two different servers. In this case, two people using two devices use the graphical interface of one of the servers. At the same time or in turn - it does not matter.

Need for licenses:

1. Licenses for all physical cores in two servers. But at least 16 licenses per server.
2. Three Windows Server CALs for three devices people use the servers with.
3. Two Windows Server CALs for two devices that people use to use the server GUI.

Three people using five devices are using two instances of Windows Server on two different servers. At the same time, two people using three devices use the graphical interface of one of the servers. At the same time or in turn - it does not matter.

Need for licenses:

1. Licenses for all physical cores in two servers. But at least 16 licenses per server.
2. Three Windows Server CALs for three people using the servers.
3. Two Windows Server CALs for two people using the server GUI.

Three people using three devices use an instance of Windows Server and an instance of SQL Server. At the same time or in turn - it does not matter. The number of connections to SQL Server is not important.

Need for licenses:

1. Licenses for all physical cores in the server. But at least 16 licenses per server.
2. Three Windows Server CALs for three devices that people use Windows Server with.
3. Server license.
4. Three SQL Server CALs for three devices people use the server with.

Three people using three devices use the GUI of a Windows Server instance to run a business application (for example, 1C) that uses an instance of SQL Server on another server. At the same time or in turn - it does not matter. The number of connections to SQL Server is not important.

So how are server products licensed? The topic is very complex, so we will try to explain it with a specific example.

Let's say that there is a company with a small PC fleet of about 5 workstations that have licensed Windows Vista installed (you must take into account the fact that the license for the operating system does not give any rights to connect to the server). The company needed to purchase a server, they decided to install Windows Server Standard 2008 on this server, so the company will need to purchase a license for Windows Server Standard itself, and in order to access this server, client access licenses (CAL - Client Access License) are needed. Since the company has 5 PCs, 5 client licenses will be required.

Suppose that after some time the company needs to install another server, let's say Windows Server Enterprise 2008. In this case, the company will need to purchase a license only for Windows Server Enterprise 2008 itself, in this case it is not necessary to purchase additional client licenses, since all 5 workstations already have Windows Server CALs. Client licenses for Windows Server give the right to connect to any of the editions of both Standard and Enterprise, but one more important fact must be taken into account that the CAL version must be at least the version of the server to which you are connecting. Example: under client licenses for Windows Server CAL 2008, you can connect to Windows Server 2003, but not vice versa, an exception - using Windows Server CAL 2003, you can connect to Windows Server 2003 R2. Now suppose that Exchange Server 2007 is installed on one of the servers, respectively, you will have to purchase a license for the Exchange Server itself and the Exchange Server CAL for five PCs.

One more point: in the delivery of OEM and boxed versions, client licenses are included in the delivery set of 5 pieces for corporate licenses, OLPs are purchased separately.

There is another version of licenses - Terminal CAL - licenses are intended for terminal access. Let's try to figure it out with an example: let's say a company decided to expand its PC fleet and buy 5 more thin clients (terminals) to save money and space (more information about thin clients can be found on the Internet). In this case, the company will have to purchase 5 more Windows Server CALs and 5 Terminal CALs. the latter, give the right only to connect terminals.

There are two types of client licenses: "per user" (user CAL) and "per device" (device CAL). The most common CAL is "per device", meaning the device itself is licensed to connect to the server, and multiple employees can connect from that device to the server. The second option, a “per user” license, is beneficial in cases where the number of employees who need access to the server is limited to, say, 20 PCs and only two employees need access. In this case, it will be more profitable to purchase 2 client licenses, and these two employees will be able to connect to the server from any PC, but only these two employees who are assigned a user license. It is fixed by an order for the enterprise, otherwise, when checking, you will not prove in any way that only two employees connect to the server.

Multiplexing.

The concept of multiplexing is extremely difficult to explain to a non-technical person, but we will try to explain it with a specific example. Imagine two servers connected to each other, let's call them C1 and C2. The company needs to install SQL Server and ensure the work of 10 employees with the database and, accordingly, the company wants to save on the purchase of client licenses. What they do: they install SQL Server on C2, and on C1 some free database that does not require any client licenses. As a result, it turns out that the main database lies on SQL Server, which is installed on C2, and employees actually access C1, which in turn receives a request, takes data from C2 and sends it to the client, i.e. works as an intermediary and thus 10 employees connect to SQL Server for free.

This C1, the intermediary switch, is the multiplexer, and this scheme is prohibited and, if verified, will entail criminal liability under Article 146 of the Criminal Code of the Russian Federation. The rules clearly state that multiplexing and intermediate equipment does not affect either the licensing rules or the number of licenses.

To summarize: to provide 10 employees with work with SQL Server, you need 10 SQL Server CALs.

external connector.

Let's try to analyze what the External Connector is with a specific example.

In this case, the best example is the need to create an online store. Imagine that a certain company decided to open an online store or some information portal to provide goods or services to its company. In this case, you will have to provide external users with access to your resources, and this requires all appropriate client licenses for each connection. It is basically impossible to calculate exactly how many client licenses will be needed in a given period of time, since we don’t know how many clients will simultaneously contact the online store, and purchasing many client licenses at once to guarantee enough is simply not profitable. This is where the External Connector is needed - this is a license for unlimited connection to the server, that is, instead of a huge number of client licenses, you can purchase one External Connector.

But there is one caveat: only external users who are not employees of the company can connect via the External Connector, in any form. Those. in our case, only customers of the online store can connect.

Processor Licensing.

Now let's deal with licensing per processor and consider the example of the most common server product that is licensed per processor - SQL Server.

What is the best way to license SQL Server? The standard option applies here: you can license the server itself and purchase the required number of client licenses for it, but you can also buy a license for the processor.

Again, imagine a physical server on which we are going to install SQL Server and connect five users to it, which we will need for this, in addition to a license for Windows Server and CALs for it. Since it is on Windows Server that we will install SQL, we will consider the option of licensing SQL Server itself. So, in a situation where we need to connect five users, we purchase a license for SQL Server itself and, accordingly, five SQL Server CALs for it. This scheme is beneficial when you need to connect a small number of users. Now suppose that we need to connect 100 users to SQL Server, in this case it is not economically viable to buy a license for the server itself and for 100 client connections, in this case it will be profitable to buy a license for the processor and then we will not need a license for SQL Server itself and no client licenses are required because the processor license includes a license for the server itself and for an unlimited number of client connections, both internal and external.

That is, the physical processor itself, the piece of hardware itself, is licensed, regardless of the number of processor cores. The following server products are licensed under this scheme:

Microsoft BizTalk Server 2006

Microsoft Commerce Server 2007