Microsoft

RDS User CAL oder Device CAL: Welche Option passt zu Ihrem Team?

IT-Administrator prüft in einem Büro eine Lizenzierungs-Checkliste für Remote Desktop Services

Choosing between an RDS User CAL and an RDS Device CAL is mainly a question of what stays stable in your environment: the person connecting, or the workstation being used. A remote employee who works from an office desktop, laptop and approved mobile device will usually be easier to license by user. A production terminal shared by several shifts may be better licensed by device.

This guide explains RDS User CAL vs Device CAL in practical terms. It covers what an RDS CAL is for, how each model works, which scenarios suit each option, and what to check before buying Windows Server RDS licensing.

What an RDS CAL is for

Remote Desktop Services (RDS) is a Windows Server role used to provide remote access to centrally managed Windows desktops, applications and server-hosted resources. Organisations may use it so employees can work with applications or a hosted desktop without installing the complete environment on every endpoint.

An RDS CAL is the access licence associated with that Remote Desktop Services use. It is separate from the underlying Windows Server licence and from the ordinary Windows Server CAL requirement. The Windows Server 2025 Standard + 10 RDS CALs product, for example, combines Windows Server Standard 2025 with 10 Windows Server 2025 RDS CALs. Each user or device also needs a standard Windows Server CAL.

The RDS CALs in that bundle can be supplied as User CALs or Device CALs. User CALs are supplied by default, so organisations that need Device CALs should select that option when ordering or confirm the required type before purchase. Always match the CAL type to the way your organisation actually uses RDS.

RDS User CAL explained

A Windows Server 2025 RDS User CAL authorises one named user to access RDS hosted through a Windows Server 2025 environment. The entitlement follows the person rather than one particular computer.

This is useful when the same employee connects from several work devices. For example, an engineer might use a desktop at the office, a company laptop while travelling between sites and an approved mobile device when checking information away from the desk. A User CAL is designed for that person’s access across the devices they use during the working day, rather than requiring a separate RDS access right for every endpoint used by that individual.

User licensing is also a natural fit for teams where each employee has a defined account and device use changes regularly. It supports consistent access to centrally managed desktops, published applications and server-hosted resources while allowing the organisation to organise access around named staff members.

When a User CAL is usually a good fit

  • Employees connect from both office and home devices.
  • One person uses a desktop, laptop and other approved endpoints.
  • Staff travel between locations or work remotely.
  • Users have individual accounts and are easy to identify.
  • The number of people using RDS is lower than the number of possible connection devices.

A User CAL is not the same as a licence for unlimited people. It is assigned to a user, so the organisation needs to plan which people are licensed and keep its records clear when staff join, leave or change roles.

RDS Device CAL explained

A Windows Server 2025 RDS Device CAL is associated with one device that connects to Remote Desktop Services. It is intended for environments where several people use the same workstation or terminal.

Consider a production-floor PC used by different operators across shifts. Licensing the device can be more straightforward than licensing every operator who might sign in. The same logic can apply to reception desks, training-room computers, call-centre workstations and fixed terminals where the hardware remains in place but the users change.

Device licensing focuses on the access point. It can therefore suit an organisation where there are many occasional users but a relatively small number of shared computers. The device is the stable part of the working pattern, while the people connecting to it vary.

When a Device CAL is usually a good fit

  • Several employees use the same workstation across shifts.
  • Reception, warehouse, production or service terminals are shared.
  • Training rooms contain fixed PCs used by different groups.
  • Call-centre workstations are used by changing agents or shifts.
  • The number of shared devices is lower than the number of people who may use them.

A Device CAL does not automatically cover every computer a person may use. If an employee connects from a second laptop or home computer, that separate device must be considered under the organisation’s licensing plan.

RDS User CAL vs Device CAL: comparison

Point of comparison RDS User CAL RDS Device CAL
Assigned to Eine bestimmte Person Ein Gerät
Best for Individual employees using several devices Shared workstations used by multiple people
Remote workers Usually the more natural fit when a person connects from office and home devices Useful when remote access is limited to specified shared devices
Shift-based work May require licensing each person who uses RDS Can suit fixed terminals used by different shifts
Device changes The user can work from different approved devices Each additional connecting device must be considered
User changes Changes in staff require user records to be reviewed Several users can use the licensed device
Typical example An architect using an office PC and laptop A factory terminal shared by operators

Which licence fits common scenarios?

Scenario 1: A remote employee with several devices

A project manager works from an office desktop, a company laptop and a home workstation. The person, rather than one fixed endpoint, is the consistent part of the access pattern. An RDS User CAL is usually the clearer choice because it is designed to give one named user access across their work devices.

This model also helps when the user changes location during the week. The organisation can plan around the licensed employee instead of tracking every possible device used by that employee.

Scenario 2: A shared production workstation

A manufacturing terminal is used by operators on several shifts. Employees may change from day to day, but the PC remains in the same location. An RDS Device CAL is usually more suitable because the access requirement is centred on the shared workstation.

Before choosing this option, identify all devices that connect to RDS. A Device CAL for one terminal does not cover another terminal elsewhere on the production floor.

Scenario 3: A training room

A college, company or internal training team has fixed computers used by different participants for separate courses. A Device CAL can fit this pattern because the PCs are shared and the user population changes. Count the devices that need RDS access, not every person who may attend a session.

Scenario 4: A small office with one device per employee

If each employee has one regular workstation and rarely connects from another device, either model may appear workable. Compare the number of users with the number of devices and consider likely changes. User licensing may be simpler if staff work from home or use laptops later. Device licensing may be practical when several people rotate through a limited set of PCs.

Scenario 5: A mixed environment

Some organisations have both personal and shared access patterns. For example, office staff may use User CALs while warehouse terminals use Device CALs. A mixed plan may reflect the real environment better than forcing every connection into one model. Keep a clear record of which users and devices are covered, and confirm that the selected licensing approach is appropriate for the deployment.

How to choose RDS CALs

  1. Map the access pattern. List who connects, which devices they use and whether those devices are personal, assigned or shared.
  2. Count the stable element. If people stay the same while devices change, start by evaluating User CALs. If devices stay the same while users change, evaluate Device CALs.
  3. Separate remote and shared access. Remote workers often use several endpoints, while shift teams often share fixed terminals. Do not assume one pattern applies to the whole organisation.
  4. Check the Windows Server edition and version. The product facts described here apply to Windows Server 2025 RDS licensing. Confirm that the CAL version matches the Windows Server environment you plan to use.
  5. Include the standard Windows Server CAL requirement. An RDS CAL is not a replacement for the standard Windows Server CAL requirement. The Windows Server 2025 Standard + 10 RDS CALs bundle includes both the server software and 10 RDS CALs, but each user or device also needs a standard Windows Server CAL.
  6. Plan for change. Account for new employees, home working, replacement laptops, additional terminals and seasonal or shift-based staff.
  7. Keep evidence of assignments. Record named users for User CALs and the relevant workstations for Device CALs. Good records make reviews and future purchases easier.

For a small team, a simple spreadsheet may be enough. Larger environments should align the record with their identity, endpoint and IT asset-management processes. If the deployment is complex, ask Microsoft or a qualified licensing specialist to verify the planned configuration before purchase.

Windows Server 2025 options

The Windows Server 2025 Remote Desktop Services User CAL is designed for organisations that need to provide consistent access for individual employees across more than one work device. It is a practical option for office staff, mobile professionals and remote workers with defined user accounts.

The Windows Server 2025 Remote Desktop Services Device CAL is designed for shared access points. It fits fixed terminals, shift-based PCs, reception desks, training-room computers, call-centre workstations and production-floor devices where multiple people may connect.

For organisations setting up a new Windows Server environment, Windows Server 2025 Standard + 10 RDS CALs combines Windows Server Standard 2025 with 10 Windows Server 2025 RDS CALs. The RDS CALs can be User or Device CALs. Check the current product page and select the CAL type that matches your plan.

Häufig gestellte Fragen

What is the difference between an RDS User CAL and a Device CAL?

A User CAL is assigned to one named user and supports that person connecting from their work devices. A Device CAL is assigned to one device and supports access by different users of that device.

Is an RDS CAL enough to access Windows Server?

No. An RDS CAL covers the Remote Desktop Services access requirement. The user or device also needs a standard Windows Server CAL, as reflected in the Windows Server 2025 Standard + 10 RDS CALs product description.

Which RDS CAL is better for remote workers?

A User CAL is often the clearer fit when one employee connects from an office PC, laptop and other approved devices. If remote access is tied to a particular shared device, evaluate a Device CAL instead.

Which RDS CAL is better for shared workstations?

A Device CAL is usually the more natural fit when several employees or shifts use the same fixed workstation. Count every device that requires RDS access.

Can I use both User CALs and Device CALs?

A mixed environment may use User CALs for individual staff and Device CALs for shared terminals. Review the complete deployment and keep clear records of the users and devices covered.

Genuine Windows Server 2025 RDS User CALs, Device CALs and the Windows Server 2025 Standard + 10 RDS CALs bundle are available from KEYFORREST with instant electronic delivery. See the current product page for the available option and select User or Device CALs according to your licensing plan.

author-avatar

Über Marios Chaidousis

Marios Chaidousis ist ein Spezialist für Software und Lizenzen und betreut Autodesk (AutoCAD, Revit, Inventor), Microsoft (Office, Microsoft 365, Windows, Windows Server, SQL Server), Adobe sowie Sicherheitssoftware. Er unterstützt Ingenieure, Fachleute und Unternehmen dabei, die passende Lizenz auszuwählen und das Beste aus ihrer Software herauszuholen.LinkedIn · Facebook · Instagram