Where to buy Windows Server client licenses (Server CALs). Microsoft Server Licensing Examples Active Directory Certificate Services
The issue of proper licensing of Microsoft server products is one of the most pressing for system administrators. It is necessary to correctly determine the type and number of licenses required, which is not so easy to do. The licensing scheme is quite complex and confusing, and numerous tips, guides and reminders on websites and forums often add even more confusion.
Licensing Basics
Among the variety of the Windows Server 2008 family, two editions are of greatest interest to small and medium-sized businesses: Standard And Enterprise, so we will consider the licensing scheme in relation to these versions. Taking information only from the official Microsoft website as a basis, we will try to make a brief summary that will allow you to quickly determine the required licensing scheme and the number of licenses.
The main licensing scheme for these editions is Server + Client Access License (CAL). This means that for each server in the organization, a server OS license + the required number of client access licenses must be purchased. A server license can be assigned to another server no earlier than 90 days after the last assignment, or sooner if the original server permanently fails.
A Windows Server 2008 license gives you the right to use a 32-bit or 64-bit version of the software, but you should remember that some tools (for example, Hyper-V virtualization technology) can only be run on a 64-bit version of Windows Server.
License types and licensing models
There are two types of client license (CAL):
- per Device- allows anyone number of users to access the server with one devices. This type of license is convenient to use when the number of users on the network is greater than the number of devices. For example, when six users work in shifts from three PCs.
- per user (per Users)- allows alone user to access the server from unlimited number of devices. This type of license is convenient for organizations that have many mobile users or users who need to access the server from several network devices.
User and device licenses have the same cost and their selection should be based on the actual infrastructure of the enterprise. It is acceptable to use both types of licenses simultaneously.
There are two licensing models for Windows Server:
- per user or device, this model provides for a CAL license for each user or device on the network, regardless of the number of servers, and makes it possible to connect to any of them. This model is usually used in a network with multiple servers and is used for any Microsoft server products(for example SQL Server). The total number of licenses under this licensing scheme must be equal to the total number of PCs or users on the network.
- to the server, this model implies limiting the number of connections to the server by the number of purchased licenses. Licenses are purchased for a specific server and their number must correspond to the maximum number of connections to the server at any given time. Once the maximum number of connections to the server is reached, other devices and network users trying to access the server will not be able to do so. This model is usually used in a network with a single server or with infrequent use of basic server functions, as well as for remote access servers. This licensing scheme applies Windows Server only.
Terminal Server Licensing
Windows Server 2008 Terminal Services requires separate licensing. To use Terminal Services (TS) features, you must have a Terminal Services Client License (TS CAL) in addition to the Client Access License (CAL).
TS CAL, like CAL, provides for two types of licenses: per device and per user, which provide for similar rules of use. There is only one licensing model: per user or per device.
Hyper-V
Hyper-V virtualization is one of the key features of the base Windows Server 2008 OS, but not all users need virtualization, so there are versions of Windows Server 2008 without Hyper-X, which is clearly reflected in their name. Although the cost of these versions is slightly lower, they have the same licensing conditions as the basic ones, incl. and on the use of virtualization. In this case, you will need to separately purchase a license for a virtualization tool, be it Hyper-V, Microsoft Virtual Server R2, or technology from another manufacturer (for example, VMware).
The following scheme is provided for licensing virtual machines: 1+1 for Standard and 1+4 for Enterprise. The numbers indicate the number of virtual OS instances that can be launched on one physical instance. The total number of OS instances available to clients at any given time should not exceed 1 for Standard and 4 for Enterprise, i.e. when the virtual system is running, a physical instance of the OS Windows Server 2008 Standard can be used only to maintain the virtual system. Windows Server 2008 Enterprise allows you to use a physical system together with three virtual ones. When running the fourth virtual system, the physical OS can also be used only for servicing virtual machines.
These rules apply not only to Hyper-V, but also to any other virtualization technology (MS Virtual Server, VMware, etc.)
How many licenses are needed?
Now, having familiarized yourself with the basics of licensing, you can try to correctly answer this question. Please note that the CAL not required in the following cases:
- The server is accessed only via the Internet, and no authentication or other identification procedure is performed, either through server software or otherwise. Example: Accessing an IIS based web server.
- For each server license, up to two devices or users may have access solely for the purpose of administering that server.
Client CALs required also for users or devices with indirect access to server functions, for example using a DHCP server.
Let's look at a few examples.
Example 1.
The simplest and most common case. The server is used as a file server and a router to organize public access to the Internet, and a DHCP server is also used to configure the internal network. Guest access is used on the server; user identification is not performed. Many people mistakenly believe that in this case one server license is enough, and client access licenses are not required (especially when the server is used only as a router and DHCP). However, this is not true; you must have CAL licenses with a total number equal to the number of devices or users on the network (in our case, 5).
Example 2.
The organization has a network of 9 PCs, of which five machines must have access to the file server for 1C Enterprise. In this case, you can apply the “per server” licensing scheme and purchase 5 CAL licenses.
Example 3.
The organization has a file server and a terminal server, has a fleet of 9 PCs, 4 of which must have access to the file server, and on 5 PCs 10 users work in terminal mode in shifts, there are also two mobile users who must have access via VPN to the server terminals. There is also an administrator's workstation. In this case, the most optimal scheme will be the following: for all stationary PCs, 9 CAL licenses per device are purchased, for 5 PCs using terminal services, 5 TS CALs per device are additionally purchased. For mobile users, it would be more appropriate to use CALs + TS CALs per user. The administrator does not need a client license, as he gains access to the servers solely for the purpose of administration.
Additional licensing information for Windows Server 2008 can be found at
Microsoft offers its corporate clients a convenient option for managing client access licenses for basic server products that make up the enterprise infrastructure - Core CAL Suite (Client Access License). Microsoft Core CAL is a set of CAL licenses for products such as:
- Microsoft Exchange Server CAL.
- Microsoft SharePoint Server.
- Microsoft System Center Configuration Manager.
- Microsoft Lync Server.
- Microsoft Windows Server 2008 R2.
- Microsoft Forefront Endpoint Protection.
Number of purchased sets Microsoft Core CAL should be equal to the number of PCs on which it is planned to use the software from this list. There is no similar set of server licenses. Core CAL Suite is available through Volume Licensing programs only as items that include Software Assurance. The cost of Core CAL Suite is 15% less than the sum of the costs of its components, and with standardization, savings can be up to 35%.
Delivery options
Boxed version- delivery in the form of a box includes a software distribution kit on a DVD in English or Russian, a certificate of authenticity and a license agreement. Purchasing Microsoft software in a boxed version is an easy way to purchase the product for private customers and small organizations (up to 5 users).
Microsoft Open License Program (OLP)- OLP volume licensing program provides perpetual rights to use current and previous versions of products. Along with the licenses, you can purchase a subscription to the Microsoft Software Assurance (SA) support program, which provides the right to update the software to new versions and some additional benefits (packages of free services and tools) for a period of 24 months.
At the end of 24 months, individual SA renewal licenses can be purchased. The product use rights granted by OLP licenses are set forth in the official Microsoft Product Use Rights (PUR). The minimum initial order is 5 OLP licenses for any products. Subsequent orders within two years can be for any number of licenses.
After purchasing an OLP license for Microsoft Office Word on the Microsoft VLSC website, the buyer is given access to the keys and installation file for current and previous versions of the product (access is available in approximately 2 business days).
Comparison table of OLP licenses and boxed versions
| User rights | Volume Licensing Programs | Box (FPP) |
| Right to use previous version (downgrade) | + | |
| Ability to install and use multiple copies of software on one PC | Any number of copies | One copy |
| Ability to install an additional copy of the software on a portable device for use by the single primary user of the licensed device | + | + |
| Ability to install an additional copy of the software on a network device | + | |
| Transfer to another PC |
Allowed no more than once every 90 days |
|
| Transfer to a third party | Permitted according to the terms of the agreement | One-time transfer is permitted provided the software is removed and all components are transferred |
Microsoft Windows Server Client Licenses (Server CAL)
| Name | Price, RUB per piece |
Comments |
| Windows Server CAL 2019 Device License | 1762 | OLP (corporate registered delivery). Only for organizations and individual entrepreneurs. Delivery time: electronic access to licenses is provided within 2 days. Within another 2 days, shipment according to accounting documents takes place along with the provision of a license on paper and license stickers. NDS is not appearing. |
| Windows Server CAL 2019 User License | 2236 |
See also: Windows Server 2019 and terminal licenses for Windows Server 2019
Windows Server 2019 Client Access License (Server CAL) grants the user or device the right to access the server software.
A Windows Server 2019 CAL is required if the user or device accesses or uses Windows Server server software. However, if access is over the Internet and is anonymous (for example, when browsing a public Web site), this license is not required. Additionally, an organization can purchase External Connector licenses to license access for external users. Additionally, Windows Server CALs are not required when Windows Server 2019 is used solely as a virtualization host, except for configurations that use Windows Server virtual machines, which require Windows Server CALs. For example, if virtual machines running Windows Server 2003 are deployed on a server running Windows Server 2008, users of the virtual machines do not need Windows Server 2008 CALs. However, they do require CALs for the editions of Windows Server deployed on the virtual machines (in this case, Windows Server 2003).
Is a Server CAL necessary if the user only occasionally uses certain server software protocols or services (for example, Network Access Protection or DHCP)?
Yes. A Windows CAL is required to access and use server software, regardless of frequency.
What is the difference between Windows Server CALs and Terminal Services CALs (terminal licenses)?
If a user or device directly or indirectly accesses Windows Server, they need a Windows Server CAL. Additionally, if a user or device accesses or uses Windows Server Terminal Services, you must purchase a Terminal Services CAL in addition to the CAL. In this case, up to two users or devices can access the server software solely for administrative purposes, without using Terminal Services CALs or Windows Server CALs.
CAL = Client Access License, i.e. Client Access License (Client License)
Microsoft software is often 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 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. Regardless of how many Windows Servers are installed and running in an organization, only one Windows Server CAL is needed per user or device.
Client licenses 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 absent or the device is inoperable.
"Per User" or "Per Device"
Device client license (Device CAL). If there are fewer devices in an organization than users (for example, several people work in shifts at one computer) or the 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 it is easier to account for users, 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 becoming cheaper, labor is becoming more expensive. The practice of one user using a large number of different devices is already widespread. Apparently, in connection with this, 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 exchange one license for another only when updating your SA subscription. Which licenses to buy - User CAL or Device CAL - each organization decides for itself.
Core CAL Suite and Enterprise CAL Suite
Client licenses must be purchased for each product used. If an organization uses a small number of Microsoft products (for example, only Windows Server), then it is more profitable to purchase only CALs for Windows Server. 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 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 will connect to the desktop on the server via RDP (terminal connection).