Blog
Windows Server CALs and RDS CALs: An SMB Guide
Windows Server licensing is easy to underestimate. A company may have one server, a small Windows 11 Pro fleet and a few remote workers, yet several different people and devices can access the server during a normal week. The operating system licence is only part of the calculation: access to Windows Server services is covered separately by Client Access Licences, or CALs.
This matters when your server provides file shares, identity services, business applications or other centrally managed workloads. It also matters when employees connect to a Windows Server desktop or application through Remote Desktop Services. In that case, a standard Windows Server CAL is not the complete requirement. An additional RDS CAL is needed for each user or device using the Remote Desktop Services access method.
This guide is written for small and medium-sized businesses that want a plain-English checklist for Windows Server CALs and RDS CALs for small business environments. It does not replace the Microsoft licensing terms for your deployment, but it gives you a practical way to identify what must be counted before you buy.
What a Windows Server CAL is for
A Windows Server 2025 CAL authorises access to Windows Server 2025 services. The basic rule supplied with the product is straightforward: every user or device that accesses Windows Server 2025 needs a CAL.
The CAL is separate from Windows Server 2025 Standard itself. Windows Server 2025 Standard provides the server operating system platform for infrastructure services, identity services, file workloads, business applications and other network-connected workloads. It does not mean that every employee or endpoint automatically has permission to access those services without a CAL.
Start by listing what the server actually does for your organisation:
- Stores shared documents or departmental files.
- Provides identity or centrally managed network services.
- Hosts an internal business application.
- Supports a controlled Windows environment for business workloads.
- Provides Remote Desktop Services sessions for users or devices.
Then identify the people and devices that connect to those services. An employee who opens a file share from a laptop is part of the count. A workstation used by several employees may be part of the count instead, if you choose device-based licensing. A remote connection to a server desktop can create an additional RDS licensing requirement, discussed below.
Microsoft 365, Office, Windows 11 Pro and a Windows Server licence should not be treated as interchangeable products. An Office or Microsoft 365 subscription may cover productivity applications and cloud services, but it does not automatically remove the requirement for a Windows Server CAL when a user or device accesses your Windows Server environment. Similarly, Windows 11 Pro on a company laptop does not by itself act as a Windows Server CAL.
User CAL or Device CAL: which model fits?
Windows Server 2025 CALs are available as User CALs or Device CALs. The two models authorise access in different ways:
| Licence type | What it covers | Often suitable when | Important counting point |
|---|---|---|---|
| User CAL | One specific user, using any number of devices | Employees work from an office desktop, laptop, tablet or other devices | Count the authorised people who access Windows Server |
| Device CAL | One device, used by any number of users | Several people share fixed workstations or terminals | Count the devices that access Windows Server |
A User CAL is usually easier to manage when access follows the person. For example, one employee may use a desktop in the office, a laptop while travelling and a tablet for occasional work. A single User CAL is designed to support that named user across multiple work devices under the User CAL model.
A Device CAL can be practical when many employees use the same equipment. Consider a reception computer, a warehouse terminal or a shift-based workstation. If different staff members use the same device to access Windows Server services, device-based licensing may avoid counting every individual user. The right choice depends on the actual working pattern, not simply on the number of employees on the payroll.
Do not mix the models casually. Make a clear decision for the relevant Windows Server access and keep a record of whether your organisation is counting users or devices. The product facts state that User and Device CALs have the same price per CAL; however, the total quantity required can be very different.
When do Remote Desktop Services CALs enter the picture?
Remote Desktop Services, commonly called RDS, allows users or devices to connect to Remote Desktop Services on Windows Server 2025. This may be used for a hosted Windows desktop, a remote application workflow or a controlled session on the server.
Every user or device that connects to Remote Desktop Services needs an RDS CAL. Crucially, an RDS CAL is in addition to the standard Windows Server 2025 CAL. The same person or device therefore needs both types of access licence when using RDS:
- A Windows Server 2025 CAL for access to Windows Server services.
- A Windows Server 2025 RDS CAL for the Remote Desktop Services connection.
For example, if eight employees use RDS to run a business application hosted on the server, the business must account for their ordinary Windows Server access and their RDS access. Buying eight RDS CALs does not replace the ordinary Windows Server CAL requirement.
RDS CALs also come as User or Device CALs. A User RDS CAL covers one person using any number of devices. A Device RDS CAL covers one device used by any number of users. The model should normally match the model chosen for the relevant access pattern, but you should document the decision and confirm the licensing terms for your particular deployment.
Not every remote activity is automatically an RDS scenario. A user may access a file share through a normal network connection, while another user opens a full server-hosted desktop through Remote Desktop Services. These are different access methods. Do not assume that a VPN, Microsoft 365 account or remote support tool is the same thing as an RDS session. Map the actual connection to the service being used and check the Microsoft terms where the situation is unusual.

Map licences to staff, devices and access methods
The most reliable SMB checklist starts with an access map rather than a headcount. A company with 25 employees may need fewer than 25 device-based CALs if everyone shares fixed terminals, or it may need user-based CALs for employees who use several devices. RDS adds another layer.
Step 1: List the Windows Server workloads
Record each Windows Server 2025 instance and its role in the business. Include file services, identity services, applications and other network-connected workloads. If one server is used for several purposes, record those purposes together. The goal is to understand who or what connects to the server, not merely how many servers exist.
Step 2: List human users
Include employees, contractors and other named users who are authorised to access Windows Server services. Pay attention to people who work across locations or use both a desktop and a laptop. A user-based approach can be easier to maintain when people change devices, but departures and role changes still need to be reflected in the inventory.
Step 3: List shared and dedicated devices
Record office PCs, laptops, warehouse terminals, reception systems and other devices that access the server. Note which devices are shared and which belong primarily to one person. This exposes a common counting gap: an organisation may count employee accounts but forget a shared device used by several shifts, or count computers without noticing that staff also connect from laptops.
Step 4: Mark RDS access separately
For each user and device, mark whether the connection uses Remote Desktop Services. Then select the relevant RDS CAL model and count the people or devices under that model. Keep the ordinary Windows Server CAL count separate from the RDS CAL count, even when the same names appear in both lists.
Step 5: Check indirect and technical access
Look beyond the obvious desktop users. Business applications, service accounts, automated processes and specialist devices may connect to server resources. Their licensing treatment can depend on how the service is configured and on the applicable Microsoft terms. Do not assume that an account called “service” or “admin” is outside the count. Flag uncertain cases for review rather than deleting them from the inventory.
Common counting gaps in small businesses
- Counting the server but not access. The Windows Server operating system licence does not by itself answer how many users or devices may access its services.
- Buying RDS CALs only. RDS CALs are additional to standard Windows Server CALs. They do not replace them.
- Assuming Windows 11 Pro covers server access. The endpoint operating system and the server access licence serve different purposes.
- Assuming Microsoft 365 replaces a CAL. Cloud productivity licensing and access to an organisation’s Windows Server services are separate questions.
- Counting employees without checking devices. A device-based model requires a device count, including shared terminals and equipment used by different shifts.
- Ignoring laptops and home working. A person who works remotely may access the same server from a different device or through RDS.
- Forgetting business changes. New employees, acquired teams, replacement devices and a move from file shares to hosted applications can change the required quantity.
Build a Windows Server licensing inventory
A small spreadsheet is often enough to make the position visible. Keep one section for standard Windows Server access and another for RDS. Useful columns include:
- Server name or workload.
- Service used, such as file access, identity or an internal application.
- User or device accessing the service.
- User CAL or Device CAL classification.
- RDS access: yes or no.
- User RDS CAL or Device RDS CAL classification.
- Department, location and responsible manager.
- Date last reviewed and reason for any change.
Review the inventory when a new server workload is introduced, when staff numbers change, when remote working expands, when shared terminals are added or when the organisation changes its application delivery method. A quarterly review may be useful for a growing business, while smaller organisations can align the check with regular IT asset reviews.
Keep purchase records and licence details with the inventory. The aim is not to create unnecessary administration; it is to make the access model explainable. If an auditor, IT supplier or new administrator asks why the business purchased a certain quantity, the answer should be visible from the user, device and RDS lists.
Choosing the right licence quantity
Choose a User CAL when access follows named people who use several devices. Choose a Device CAL when access follows shared equipment used by different people. Apply the same practical thinking to RDS CALs, then add the RDS requirement to the ordinary Windows Server requirement.
Examples:
- Small office with individual laptops: User CALs may be simpler because each employee can use an office computer and a laptop without counting every device separately.
- Warehouse with shared terminals: Device CALs may fit better where different shifts use the same fixed equipment.
- Remote application for selected staff: Identify the users or devices using RDS, provide the corresponding RDS CALs, and also account for their standard Windows Server CALs.
- Mixed working patterns: Map each access pattern carefully. Do not select a model only because it appears cheaper for the current headcount; future device changes and staff turnover also affect administration.
Windows Server 2025 CALs, User CALs, Device CALs and Windows Server 2025 RDS CALs are separate purchasing decisions. At KEYFORREST, genuine licences are available with instant electronic delivery. Select the product and licence type that match your documented access model, and see the current price on the product page.
Frequently asked questions
Does every employee need a Windows Server CAL?
Every user or device that accesses Windows Server 2025 needs a CAL. Whether you count employees or devices depends on whether you choose the User CAL or Device CAL model and how the server is used.
Is an RDS CAL a replacement for a Windows Server CAL?
No. A Windows Server 2025 RDS CAL is additional to the standard Windows Server 2025 CAL when a user or device connects through Remote Desktop Services.
Should a small business choose User CALs or Device CALs?
Choose User CALs when named people use multiple devices. Choose Device CALs when several people share fixed devices. Compare your actual working pattern, including remote access and shift work.
Does Microsoft 365 include Windows Server CAL rights?
Do not assume so. Microsoft 365, Office and Windows Server CALs cover different products and access scenarios. Check the specific terms for your licensing arrangement.
How often should we review our licence inventory?
Review it whenever users, devices, server workloads or remote access methods change. A regular IT asset review also helps identify forgotten shared terminals, new RDS users and access by technical accounts.