A Windows VPS can provide a convenient way to host applications, websites, business software, remote desktops, and other Windows-based workloads without maintaining physical server hardware. However, when multiple people connect to a Windows VPS through Remote Desktop Services (RDS), licensing becomes an important consideration. One of the most frequently misunderstood areas is the relationship between a Windows VPS, Windows Server licensing, and RDS Client Access Licenses (CALs). Understanding these requirements can help businesses avoid unexpected compliance problems and choose an appropriate hosting arrangement.
What Is an RDS CAL?
An RDS CAL is a license that permits a user or device to access Remote Desktop Services on a Windows Server. Microsoft provides two primary RDS CAL models: Per User and Per Device. A Per User CAL is assigned to an individual user, while a Per Device CAL is assigned to a particular device.
This distinction is important because an RDS CAL is not simply another name for a Windows Server license. Windows Server licensing and RDS licensing address different requirements. A server can be running legitimately under its applicable Windows Server license while still requiring additional RDS CALs for users or devices accessing RDS functionality.
Does Every Windows VPS Need an RDS CAL?
Not necessarily. The answer depends on how the Windows VPS is being used. If the VPS is hosting ordinary server workloads and users are not using Remote Desktop Services beyond permitted administrative access, the licensing situation can differ from an environment designed to provide remote desktops or applications to users.
When Remote Desktop Services is used as a session-hosting platform, Microsoft states that each user or device connecting to an RDS session host needs an appropriate RDS CAL.
Therefore, simply purchasing or renting a Windows VPS should not automatically be interpreted as purchasing unlimited RDS access. The VPS provider’s included licensing and the customer’s intended use should be checked carefully.
What Is the Difference Between Per User and Per Device CALs?
The two main RDS CAL options are designed for different working patterns.
A Per User RDS CAL is associated with a user. This can make sense when employees have multiple devices, such as a desktop computer, laptop, and tablet, and need to access the same remote environment. Microsoft describes the Per User model as particularly suitable when individual users connect from their own devices.
A Per Device RDS CAL is associated with a device rather than a particular person. This can be useful when several employees share the same workstation, such as in shift-based operations. The same licensed device can therefore be used by different workers.
Choosing between these models should be based on the actual way users and devices access the Windows VPS rather than simply selecting whichever option appears cheaper.
Does a Windows VPS Provider Include RDS CALs?
This varies between providers and hosting plans. Some providers may offer Windows VPS packages with certain Microsoft licensing arrangements included, while others may require customers to supply or obtain additional licensing.
The important point is to read the provider’s licensing terms instead of assuming that a Windows VPS subscription automatically covers every type of remote access. Ask specifically whether RDS access is licensed, which RDS CAL model applies, and whether the provider operates under a licensing arrangement designed for service providers.
For organizations using a hosted Windows environment, this clarification should happen before deploying production workloads or adding multiple users.
Can You Use an Older RDS CAL With a Newer Windows Server?
Version compatibility is another common licensing question. Microsoft states that an RDS CAL for an earlier Windows Server version cannot be used to access a newer Windows Server session host. However, newer RDS CALs can generally provide access to earlier supported Windows Server versions.
For example, Microsoft’s current compatibility guidance states that Windows Server 2022 RDS CALs cannot be used to access a Windows Server 2025 session host, while Windows Server 2025 RDS CALs can be used with Windows Server 2022 and earlier supported versions.
This makes version checking especially important when upgrading a VPS operating system.
Is the RDS CAL the Same as a Windows Server CAL?
No. They serve different purposes. A Windows Server CAL generally covers access to Windows Server functionality under the applicable licensing model, while an RDS CAL provides the additional licensing required for Remote Desktop Services functionality.
Microsoft describes RDS CALs as additive licenses. In other words, organizations may need the applicable Windows Server licensing and the appropriate RDS licensing rather than treating an RDS CAL as a replacement for the underlying server licensing.
This distinction is one of the most important concepts to understand when evaluating a Windows VPS RDS CAL requirement.
How Are RDS CALs Installed and Managed?
In a traditional RDS deployment, a Remote Desktop Licensing server is used to install, issue, and track RDS CALs. Microsoft explains that the license server provides CALs to users or devices when they connect to an RDS session host.
Administrators can install the Remote Desktop Licensing role, activate the license server, and install the appropriate CALs. The session-host environment must then be configured to use the licensing server.
For a VPS customer, however, the provider may manage some or all of this infrastructure. That is why it is important to establish who is responsible for licensing, activation, tracking, and compliance before configuring RDS.
Is There a Grace Period?
Yes. Microsoft documents a 120-day licensing grace period for RDS deployments. During this period, an RDS license server is not required. Once the grace period expires, clients need valid RDS CALs issued by a license server to continue signing in to the session host.
The grace period should not be interpreted as a permanent free-use period. It is intended to provide time for administrators to configure the licensing infrastructure. Organizations planning long-term Windows VPS deployments should arrange licensing before relying on RDS for ongoing operations.
Can RDS CALs Be Shared Between Users?
The answer depends on the CAL model. A Per User CAL is assigned to a specific user, while a Per Device CAL is assigned to a specific device. Microsoft allows organizations to use a combination of user and device CALs when appropriate.
Organizations should therefore avoid treating a pool of CALs as unrestricted licenses that anyone can use without tracking. In particular, Microsoft notes that Per User licensing is not enforced in the same way as Per Device licensing, making it the administrator’s responsibility to maintain sufficient licensing and remain compliant.
What Should You Ask a VPS Provider?
Before purchasing a Windows VPS for RDS purposes, ask several direct questions. First, determine which Windows Server edition and version is included. Second, ask whether RDS CALs are included or separately required. Third, determine whether licensing is Per User, Per Device, or another authorized service-provider model. Fourth, ask who manages the Remote Desktop Licensing server. Finally, confirm whether the proposed arrangement permits your intended number and type of remote users.
These questions can prevent a situation where a technically functional VPS is later discovered to have an unsuitable licensing arrangement.
How Can Businesses Avoid Common Licensing Mistakes?
The safest approach is to separate technical requirements from licensing assumptions. Start by identifying how many people will connect, how many devices they will use, whether users share devices, which Windows Server version will run on the VPS, and whether the VPS provider is supplying Microsoft licensing.
Next, verify the requirements against Microsoft’s current licensing documentation. Microsoft provides specific guidance for RDS CAL assignment, version compatibility, licensing servers, and deployment configuration.
Businesses should also maintain records of assigned licenses and periodically review their environment, particularly after adding employees, changing devices, upgrading Windows Server, or moving to another VPS provider.
Final Thoughts
A Windows VPS RDS CAL requirement can appear complicated at first, but the basic principle is straightforward: Windows Server licensing and Remote Desktop Services licensing are separate considerations. When a Windows VPS is used to provide RDS-based access to users, the organization needs to determine the appropriate CAL model, confirm version compatibility, and establish who is responsible for licensing.
The best Windows VPS arrangement is not necessarily the one with the lowest advertised monthly price. Licensing coverage, technical configuration, security, scalability, and provider transparency are equally important. By asking the right questions before deployment and checking current Microsoft licensing guidance, businesses can build a Windows VPS environment that is both practical and appropriately licensed.