FAQ: Microsoft Windows Server 2016 RDS 10 User CAL

What is Microsoft Windows Server 2016 RDS 10 User CAL?

Microsoft Windows Server 2016 RDS 10 User CAL is a package of 10 User CAL access licenses for Remote Desktop Services in a Windows Server 2016 environment. It is not a program or installer, but a license entitlement, which is a document confirming the right of users to access remote desktop services. Such a license is required when employees or collaborators log in remotely to the server and use applications or a full desktop provided by RDS.

Is RDS CAL the same as a Windows Server license?

No. These are two different elements. A Windows Server license itself entitles you to use the server system, while RDS CAL is an additional access license required for the legal use of remote desktop services. In practice, this means that a company may have a properly licensed server, but if users connect through Remote Desktop Services, the corresponding RDS CALs are still required. It is also worth remembering that RDS CAL is a license document, not separate software to download.

What does the User CAL version mean?

User CAL is assigned to a specific user, not to one computer. This means that one person can access from multiple devices, such as an office computer, home laptop, and tablet, as long as it is still the same user. This solution is particularly convenient for companies where employees work hybridly, mobilely, or use more than one workstation. In this licensing model, people are licensed, not equipment.

How does User CAL differ from Device CAL?

The difference lies in the way the license is assigned. User CAL is assigned to a person, while Device CAL is assigned to a device. If several employees take turns using one terminal, the Device CAL option may be more cost-effective. However, if one employee logs in from multiple locations and devices, User CAL is usually the better choice. In the case of the Microsoft Windows Server 2016 RDS 10 User CAL product, you purchase access for 10 named users, regardless of the number of their devices.

How many RDS CAL licenses do I need?

You need to count the number of people who will actually use the remote desktop services. If 10 different users will connect to the RDS server, a package covering at least 10 User CALs is required. If there are more users, additional licenses should be purchased to match the actual usage. The number of simultaneous connections is not relevant, but rather the number of users entitled to access. From a licensing compliance perspective, it's best to adopt the principle that every person with login capability should be covered by an appropriate license.

Does one User CAL license allow multiple people to use one account?

This should not be done. A User CAL license is intended for a specific user and should not be treated as a shared entitlement for multiple people. Sharing one account among several employees can lead to licensing rule violations and problems during audits. For compliance, it's best to assign access individually and maintain a transparent record of who uses the license. This is especially important for companies that want to demonstrate the full legality of their software and access entitlements.

Are these licenses required even if the server is already running?

Yes. The obligation to have the correct RDS CALs stems from Microsoft's licensing model, not from the technical fact of launching the service. The server may be running, but this does not automatically mean that user access is properly licensed. In the event of an audit, what matters is whether the company has the appropriate number of valid access licenses and documents confirming their origin. Therefore, purchasing legitimate RDS CALs is a matter of compliance, business security, and limiting legal risk.

Can an RDS CAL license be transferred to another user or to another company?

In principle, licenses should be treated in accordance with the manufacturer's terms and sales documentation. In practice, assignment within an organization should be stable and justified, and any changes must comply with Microsoft's licensing rules. Particular caution should be exercised when attempting to transfer licenses between separate business entities. If doubts arise regarding the transfer, it is best to rely on licensing documents and proof of purchase. Since RDS CAL is a legal entitlement, not a physical medium, proper documentation is crucial.

How do you know that the key and license are legal?

Legality is primarily confirmed by the reliable origin of the license, complete sales documents, and product compliance with the offer. The customer should receive clear information that they are purchasing a CAL/RDS license, i.e., a document authorizing access, not new software. The seller's data, the possibility of obtaining a VAT invoice, and clear delivery terms are also important. When making a purchase, it is worth paying attention to whether the offer does not mislead as to the nature of the product. A legal key should be provided with commercial documentation allowing the right to use the license to be demonstrated.

What does the delivery, VAT invoice, and post-purchase support look like?

In the case of this type of product, licensing data and documents confirming the purchase are delivered, as we are dealing with an access license, not a boxed program. The customer receives a legal key, and the sale is documented through a VAT invoice, which is important for both accounting and evidentiary purposes in the event of an audit. For many companies, this is an essential element of purchasing policy and compliance. If you need to clarify the difference between User CAL and Device CAL before making a purchase, confirm the number of licenses needed, or discuss compliance rules, you can use the telephone contact at 00 800 121 1654.

Is Microsoft Windows Server 2016 RDS 10 User CAL a good choice for a small and medium-sized business?

Yes, if specific employees use the remote desktop on multiple devices within the company. The 10 User CAL package works well where you need to organize access for a team, maintain licensing compliance, and have transparent documentary bases. This is a solution for organizations that need legitimate access rights to the RDS environment in Windows Server 2016, not another application to install. The most important thing is to correctly match the number of licenses to the number of users and maintain full purchase documentation. You can also contact [email protected] for more information or assistance.