Per device or per user RDS license

Fraser Scott 21 Reputation points
2026-11-20T17:32:09.2+00:00

We are currently in discussions with a company to provide a hosting environment for our hospitality software and we need some clarification on a licensing issue which isn't clear.

 

An issue has arisen in terms of calculating the number of RDP users for our system as a whole. We supply a bar or restaurant solution, the POS terminal logs into the system and then throughout the day, and within the our POS software, the waiters or servers swipe their cards to order and post an item or items to a bill. 

Each waiter does not login to Windows (or the Server running the POS application under RDP).

The POS application is all that the terminal runs.

There is no Office 365 required for the waiters using the POS workstation.  

 

Imagine a site that has 10 Windows based POS terminals, in a variey of bars and restaurants

There might be 100 waiters/servers that could work on these terminals throught the day - maybe morning shift, afternoon shift and evening shift.  

Each day might be a different number of waiting/server staff working that day. It might be 80 one day, 105 the next, 60 the next.

 We would suggest it is 10 RDP users licences – Bar1, Bar2, Restaurant1, Restaurant2 and so on, NOT 100 users. However, it is being suggested that we will require RDS user CALS for each server, or device CALS.

 

Is 1 RDS User CAL per terminal compliant, or do we definitely require Per device RDS CALS

TIA,

Fraser

Windows for business | Windows Server | Devices and deployment | Licensing and activation
0 comments No comments

1 answer

Sort by: Newest
  1. HLBui 15,990 Reputation points Independent Advisor
    2026-11-20T18:18:08.8566667+00:00

    Hi Fraser Scott

    Based on the scenario you've described, I would not view the 100 waiters/servers as 100 individual RDS users, since they are not authenticating to Windows or establishing their own Remote Desktop sessions. The key point is that the POS terminals are the devices connecting to the Remote Desktop environment, while the waiter card swipes are simply application-level actions inside your hospitality solution.

    From a Microsoft licensing perspective, the decision generally comes down to whether you license RDS User CALs or RDS Device CALs. In an environment where a relatively small number of POS terminals are shared by a much larger pool of staff across multiple shifts, RDS Device CALs are typically the more appropriate and cost-effective licensing model. In your example, if there are 10 POS terminals accessing the RDS environment, you would normally look at licensing those 10 devices rather than every waiter who may use the application during the day.

    That said, a single RDS User CAL per terminal would not normally be the correct interpretation, because User CALs are assigned to named users, not shared devices. If the terminals are the connection point and are shared by many employees, RDS Device CALs are generally the compliant approach. Each device that connects to the RDS server requires its own Device CAL, regardless of how many staff members use that device.

    My recommendation would be to size the licensing based on the number of POS terminals connecting to the RDS environment and validate the final design with your licensing provider or Microsoft licensing specialist, especially if the hosting company is operating under a Service Provider Licensing Agreement (SPLA), as the licensing rules can differ in hosted environments.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.