Buying RDS CALs for Windows Server 2012 R2: A Comprehensive Guide

Remote Desktop Services (RDS) is a vital component of any Windows-based infrastructure, allowing users to access remote desktop sessions and work efficiently from anywhere. However, to ensure that your RDS deployment is compliant with Microsoft's licensing policies, you need to purchase and implement the correct RDS Client Access Licenses (CALs). In this article, we will discuss the two methods available for implementing RDS CALs, as well as the steps involved in installing and configuring a Remote Desktop License Server on Windows Server 2012 R2.

Method 1: Assigning RDS CALs Per User

One method of implementing RDS CALs is to assign them per user. This means that each user who accesses the remote desktop session needs their own CAL. You can do this without Active Directory, making it a viable option for organizations with limited directory infrastructure. To assign an RDS CAL per user, you need to purchase the relevant license from Microsoft or a licensed vendor.

Method 2: Assigning RDS CALs Per Device

The other method of implementing RDS CALs is to assign them per device. In this scenario, each device that accesses the remote desktop session needs its own CAL. This approach can be useful for organizations with a large number of devices, but it may not be as flexible as assigning CALs per user.

Choosing the Right Licensing Model

When purchasing RDS CALs, you need to choose between two licensing models: Per User or Per Device. The Per User model is ideal for organizations with a large number of users who access remote desktop sessions simultaneously. On the other hand, the Per Device model is better suited for organizations with a large number of devices that require access to remote desktop sessions.

Default Licensing and Activation

When you install and activate RDS CALs on your Windows Server 2012 R2 deployment, there is a default licensing period applied. During this period, which lasts for 180 days, no purchased RDS CAL license is required. However, after the grace period expires, you will need to purchase and implement the correct RDS CALs to ensure compliance with Microsoft's licensing policies.

Installing and Configuring the Remote Desktop License Server

To install and configure the Remote Desktop License Server on your Windows Server 2012 R2 deployment, follow these steps:

1. Open the Server Manager console and click on the 'Add Roles and Features' option.

2. In the Add Roles and Features Wizard, select the 'Remote Desktop Services' role and proceed with the installation.

3. Once the installation is complete, open the Remote Desktop License Server console and configure it according to your organization's needs.

In conclusion, purchasing and implementing RDS CALs for Windows Server 2012 R2 is a crucial step in ensuring compliance with Microsoft's licensing policies. By understanding the two methods available for implementing RDS CALs – per user or per device – you can choose the right approach for your organization. Additionally, by following the steps outlined in this article to install and configure the Remote Desktop License Server, you can ensure that your remote desktop deployment is secure and compliant with Microsoft's licensing policies.

Remember that there are no noticeable changes in the steps involved in implementing RDS CALs across different Windows Server editions, including 2012, 2016, or 2019. The same steps apply to all these editions, making it easy to implement RDS CALs on any of these platforms.

Buy windows server 2012 r2 rds cals