Would you like to see the site in a different language?
RDS TOOLS BLOG
Windows Server CALs, User CALs, Device CALs, RDS CALs? Our what, why, how to and when of CALs.
)
In the realm of IT infrastructure, ensuring proper licensing is crucial. Indeed, more than ever, businesses need to maintain compliance and avoid legal issues. Client Access Licenses (CALs) are an integral part of Microsoft's licensing framework. For organisations using Remote Desktop Services (RDS), understanding RDS CALs has become essential.
This article aims to shed light on RDS CALs, explaining what they are, why they are needed, the differences between User and Device CALs, and their role in conjunction with Server CALs. In short, we will explore key aspects of RDS CALs and their significance in relation to remote access, to answer the question What are RDS CALs.
That done you will have a chance to discover what RDS-Tools can do for the RDS environment and specifically your company's IT infrastructure.
A Client Access License, CAL for short, grants the right for devices or users to access a server and use its services. The license attached to the operating system allows the OS on the server to be run. These are Windows Server licenses. What I am going to call usage CALs combine with OS licensing to enable the access to and use of the server as well as its running. Microsoft offers two types of CALs - Device CAL and User CAL and these apply to either local and remote use situations. Read on, for their description.
Remote Desktop Services (RDS) provide the ability to access a server's desktop remotely. RDS CALs are specifically required for remote access scenarios. Each user or device that intends to access the server remotely needs to be properly licensed with RDS CALs to ensure compliance with Microsoft's licensing laws. These are additional to ordinary CALs and also attached to either User or Device.
As you will have gathered, in addition to RDS CALs, businesses also need to remember Windows Server CALs. The latter CALs are essential so that each user or device accesses a licensed Windows Server. This applies regardless of the purposes of their access, except one: administration.
It is worth noting that one small exception to the CAL rules. Up to a maximum of two users or devices may access the server and software without extra CALs but the OS license, but on the following condition. They can access it for server administration purposes alone. This is the only case requiring neither RDS CAL nor standard CAL. No other “users” are allowed under the Windows Server CAL.
Should your company infrastructure comprise a Remote Desktop Session Host (RDSH) server, bear in mind the following server behaviour. When a user initiates a connection with a RDSH server, the server will seek to contact a RD Licensing server to find out whether their incoming request is associated with a valid User CAL.
The RD Licensing Server has the job of checking its Collection and responding accordingly to the CALs it contains. Depending on if the user have an allocated CAL or not, the RD licensing server will respond positively or negatively to the RDSH server. The latter will accept the connection on the condition the response is positive. If the user has no CAL or there is no RD Licensing Server to respond to the query, it will refuse the user access. So, here again, it is important to have the appropriate licensing for your infrastructure.
Each Per Device CAL is assigned to a specific device, so that multiple users can access the server from that unique device. In contrast, each Per User CAL is assigned to an individual user, enabling every one of those users to access the server from any device they like. Deciding between Per User or Per Device CALs will depend on the organisation's remote access requirements.
Because Per Device CALs tie the license to a specific device, it is better suited to a situation where multiple users need to access the server via only sole device. On the other hand, given the fact Per User CALs associate each license with a particular user, it will grant them access from whichever of the devices they may need to use. It is these use cases which will prompt you in your choice of the type of CALs your company may choose to purchase.
We have seen the main description of CALs and where RDS CALs fit in. Whether you will need both depends on whether your company only works within LAN or not. They work together when your users and clients need remote access and therefore require additional RDS licensing to complement the standard licenses.
Bearing in mind the following differences apply to local and RDS CALs, the main differences between Per User and Per Device CALs include:
Per Device CALs are physically allocated to devices, while Per User CALs are assigned within Active Directory.
RDS CALs can be tracked with Per Device, whereas it's not feasible within a workgroup for Per User.
Per Device allows for revoking up to 20% of RDS CALs, which is not possible with Per User.
Per Device offers temporary CALs or RDS CALs for a limited duration, but Per User does not issue temporary CALs.
Per Device does not permit over-allocating RDS CALs, whereas Per User may result in over allocation.
RDS brings several advantages, such as cost-effective thin-client architecture and centralised control. However, it also poses some challenges. Security and monitoring are two main issues, besides the added cost of RDS CALs. Anyhow, when planning and purchasing hardware, software, CALs or anything else, be they first or second hand, it is remain important to ensure they are genuine. This plays a part in ensuring compliance and security.
If the RDS protocol (RDP) is exposed to the internet for remote access the server is left vulnerable to cyber-attacks. Be they brute-force, malware or other, it is essential to prevent them. With cyber-crime continually on the rise, it is paramount businesses and individuals grow better prepared against threats to data security. Indeed, it is sad to say that no server or computer is exempt from potentially becoming a target.
Yet, gladly, most admins and IT professional are aware of this and work hard to maintain the integrity of IT infrastructures. Beyond the all-important strong passwords and highly recommended two-factor authentication, measures can involve savvy infrastructure setup, RD gateway servers, maybe a DMZ as well as one or more firewalls, session time-outs, remote desktop role creation and management...
This is where RDS-Tools Advanced Security comes in with it all-round comprehensive protection. Our security software affords you, your colleagues and your clients the best cyber protection available, all that without breaking the bank.
Implementing RDS also requires well planned and carefully defined deployment and configuration for users, groups, apps, and more. Added to that, is the necessary continuous monitoring, surveillance of servers and their performance and usage, and the consequent need for alerts and updates being sent to the right people. This could all further add to the administrative burden. Hence why we developed RDS-Tools Server Monitoring . Our software aims to take the burden of this every instant watchfulness off from your shoulders and do it for you in all simplicity.
RDS CALs are a crucial element of remote access to Microsoft products via Remote Desktop Services. These licenses ensure compliance with Microsoft's licensing laws and facilitate regulated remote desktop access. By choosing the appropriate type of CALs and RDS CALs - Per User or Per Device - businesses can optimise their licensing costs and efficiently manage their remote desktop services. With the advantages and challenges presented by RDS and RDS CALs, IT teams of any kind need to keep atop a wide range of tasks.
Our hope is that with the above summary, IT professionals can better weigh up their requirements and effectively organise their company’s remote workspace experience. Precise management of RDS CALs, calculating license requirements accurately and implementing RDS licensing effectively will ensure a compliant and productive remote access environment. Come what may, our tools for RDS make up the Swiss army knife of IT and you are welcome to try them out and contact us about them any day. To finish, remember, staying informed about the licensing requirements, security and other software evolutions is key for a smoothly functioning IT infrastructure.
Your RDS Tools Team
Simple, Robust and Affordable Remote Access Solutions for IT professionals.
The Ultimate Toolbox to better Serve your Microsoft RDS Clients.
Get in touch
Related Posts
)
Looking for advanced monitoring tools? Ready to dive into effective Windows application performance monitoring? Learn more on the subject before we emphasize the power of RDS-Tools Server Monitoring as the go-to solution for IT professionals managing RDS environments.
)
RDS-Tools is excited to announce the latest release of RDS-Remote Support, now equipped with full Freshdesk Integration.
)
Learning how to restart Remote Desktop efficiently is crucial for maintaining productive, stable remote environments. This guide provides actionable steps and explores how RDS-Tools’ powerful solutions enhance the restart experience, ensuring seamless session management with robust security and monitoring features.
)
A guide on how to set up unattended access in TeamViewer, followed by information on RDS-Remote Support as a powerful alternative for IT administrators.
